GAIA vs Orbits

GAIA

GAIA's source is public, so its approval gate, memory store and token handling can be read. Three approval modes and per-tool overrides exist, but the default mode in the source runs every action unasked, which the privacy policy and release notes do not say. Pro costs $30 a month and self-hosting is limited to noncommercial use.

Orbits

Orbits is a family household app whose assistant, Bit, runs shared calendars, lists and meals, reads household email and places restaurant calls after approval, with iOS releases every week or two. No outside agent can call it, prices appear only as App Store in-app purchases, and no status page, security contact or named subprocessors were found.

GAIA

1. Set Settings > Approvals to Always ask or Auto before connecting mail. The default in the source runs every action, including send and delete, without asking.
2. Expect no public API on the hosted service. The backend turns off its OpenAPI document in production, so reach GAIA through its apps, bots or CLI.
3. Check the plan before relying on the hosted service. The README and docs describe a Free plan, and the pricing page says GAIA is a paid product.
4. For self-hosting, prepare Docker, Node.js 20, a WorkOS account and a model key first, and confirm the use is noncommercial under the licence.
5. Add outside tools as MCP servers by URL on the Integrations page. GAIA asks before adding a server in every approval mode.

Orbits

1. Don't plan to call Orbits from another agent. llms.txt says no public agent API is offered.
2. Tell the owner the assistant needs an Orbits subscription bought in the app, and that any trial appears only at purchase.