Two plans, no surprises. Or self-host the open-source core at no cost.
For personal use — one account, all features, no limits.
Share agents with your team or household.
Starting at $5/month — 20x less than alternatives that only support one agent. See how we compare →
The entire stack is open source under the Apache 2.0 license. Run it on a home server, a Raspberry Pi, or wherever you want — no limits and no cost.
Side-by-side comparison of Cloud tiers and self-hosted.
| Feature | Single User | Team | Self-Hosted |
|---|---|---|---|
| Users | 1 | Unlimited | Unlimited |
| Runtime connections | Unlimited | Unlimited | Unlimited |
| Concurrent sessions | Unlimited | Unlimited | Unlimited |
| Sessions per user | Unlimited | Unlimited | Unlimited |
| Message retention | 30 days | 365 days | Unlimited |
| Database | Managed Postgres | Managed Postgres | SQLite or Postgres |
| Authentication | Clerk SSO | All SSO providers | Builtin or Clerk |
| TLS / CORS | Managed | Managed | Self-configured |
| Support | Priority | Community | |
| Audit log export | — | ✓ | ✓ |
| Source access | Apache 2.0 | Apache 2.0 | Apache 2.0 |
With Cloud, we host the hub (the central server) for you — you just install the runtime on your machine and connect. Self-hosted means you run everything yourself, including the hub. Either way, your agents always run on your own machines.
Yes. You just point your runtime at a different hub address. Your agent setup stays the same — only the hub changes.
No. The self-hosted version has the same features with no artificial limits. Cloud just saves you from running and maintaining the hub yourself.
Agent output passes through the hub so you can see it in the chat UI. On Cloud, that means it goes through our servers. If you'd rather keep everything local, self-host the hub on your own machine.
We use Stripe — all major credit and debit cards work.
