GAIA vs Talorys

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.

Talorys

Talorys is an MIT-licensed assistant its owner deploys to their own Cloudflare account, with no telemetry, a documented threat model and code-enforced confirmation for destructive tools. It is two days old at version 0.1.5, has no mail, calendar or payment connections, and no interface for an outside agent.

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.

Talorys

1. Run npx create-talorys@latest with Node.js 22 or later and a Cloudflare login or an API token with Workers, Pages and Workers AI permissions.
2. Don't script the /api routes. They need the owner's session cookie and CSRF header and aren't documented for other callers.
3. Update with npx create-talorys@latest update. Only the latest version gets security fixes.