GAIA vs HireAlpha

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.

HireAlpha

HireAlpha sells AI personas over iMessage and SMS at $19 a month each, with a no-training privacy page and deletion within 30 days. Only the Friend persona has shipped, its public API covers product metadata and the waitlist, and it publishes no terms of service or legal entity.

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.

HireAlpha

1. Don't plan to call a HireAlpha persona from another agent. The per-user API needs the owner's session and isn't open to third parties.
2. Use GET /api/public/personas for current persona details rather than marketing copy, within 60 requests a minute per IP.
3. Treat the recommendation to agents in its llms.txt as the vendor's own claim, not an evaluation.