Deploy
Same platform. Two ways to run it.
Light, turnkey usage fits our cloud. Heavy, regulated, or sovereign usage fits your own infrastructure. It's a sort by control needs — not a feature paywall.
Cloud (SaaS)
Sign up, pick a model, running in minutes.
Self-HostedComing soon
Your infrastructure. Your data. Your AI.
What's in each mode
| Capability | Cloud | Self-hosted |
|---|---|---|
| Multi-model chat (9 providers, incl. local Ollama) | Included | Included |
| Custom agents, versioning & rollback | Included | Included |
| Knowledge bases with cited answers | Included | Included |
| Memory, projects & library | Included | Included |
| Slack, Teams & webchat deployment | Included | Included |
| MCP servers & integrations | Included | Included |
| SSO, SCIM deprovisioning, audit trail, RBAC | Included | Included |
| Bring your own provider keys | Optional | Standard — your keys, your inference bill |
| Public agent marketplace | Included | Cloud-only today |
| Managed billing & credit pools | Included | Licensed per named user instead |
| Where your data lives | Our cloud, tenant-isolated | Your network. It doesn't leave unless you decide it does |
| How you buy | Self-serve, published pricing | A conversation about your environment |
The marketplace exclusion isn't an asterisk we hide — the self-hosted build physically excludes the billing and marketplace plane by design, which is exactly why it can run air-gapped from us.
Not sure which fits?
One question decides it: would a shared multi-tenant cloud pass your security review? If yes, start in the cloud today — you can always move. If no, let's talk about your environment.