GAIA vs Haven

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.

Haven

Haven answers by phone call, text, email and app, is free in beta with no card, and publishes a status page with dated incidents. No public page read says which actions need approval, which accounts it connects or how their tokens are kept, and it names no model provider or sub-processor.

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.

Haven

1. Haven has no documented API or MCP server. An outside agent can reach it only through the owner's channels (call, SMS, email, app).
2. Do not assume an approval step before Haven sends mail, texts or calls. None is documented on the public pages.
3. Email Haven sends to other people names Hello Haven as sender and says it was sent on the user's behalf, per the terms.
4. Chat messages, history, profile context and uploaded files go to third-party AI model providers that the vendor does not name.
5. Check status.hellohaven.ai before relying on phone or voice. All four published incidents affected those channels.