The same engine. Built for one, a team, or the whole org.
CTXone's open core is complete and self-hosted — every MCP tool, the full memory graph, plans, branches, taint, and provenance. Team and Enterprise don't unlock features; they run that same engine for many people, with the identity, sharing, and governance that a group needs.
One hub your whole team points at.
Everyone runs against a single shared Hub, so context is shared by default — not copied, primed, or re-explained per person. What one engineer teaches CTXone, the whole team's agents already know.
What you get
- A shared team Hub. One daemon, one graph, every tool and teammate connected to it by URL. No per-laptop database drifting out of sync.
- Per-user identity. Commits, blame, and
why-did-weattribute to real people — so a decision traces back to who actually made it, not an anonymous agent. - Branch workflows across contributors. Sandbox speculative context on a branch, review the diff, and merge it into the shared graph the same way you'd merge code.
- Shared plans. Plans live on the team hub and survive across people and sessions, so work-in-flight is visible to everyone instead of trapped in one person's chat history.
- Priority support. A direct line for setup, upgrades, and the occasional "why is recall ranking this?" question.
Who it's for
Teams already using AI coding tools daily who are tired of each member's agent starting from zero. If you've ever settled an architectural decision in Slack only to watch a teammate's model re-litigate it a month later, Team is the fix.
Agent context, governed at org scale.
Everything in Team, plus the multi-tenancy, access control, and auditability required to run CTXone across many teams in a regulated environment — without giving up the self-hosted, data-stays-put posture of the open core.
What Enterprise adds
- Multi-tenancy. Isolate graphs by team, project, or business unit within one deployment, with clear boundaries between who can see and write what.
- RBAC. Role-based access control over paths and operations — read, write, branch, merge, administer — mapped to your org's roles.
- SSO / SAML. Authenticate through your existing identity provider. No separate CTXone accounts to provision or offboard.
- Audit bundles. Exportable, tamper-evident records of who wrote, changed, or removed context and when — provenance you can hand to a compliance reviewer.
- Policy governance. Codify verification gates (taint / quarantine) as org policy, so sensitive paths require review or are blocked from automated writes.
- Data residency & compliance support. Deploy where your data is required to live, with support for HIPAA, SOC 2, and GDPR-aligned operating requirements.
- Direct founder access & roadmap influence. A working relationship with the people building CTXone, and real input into what ships next.
Who it's for
Organizations in compliance-forward industries — healthcare, financial services, regulated public sector, large SaaS — deploying AI agents internally at scale, who need governance and auditability as a precondition, not an afterthought.
Talk to us
Tell us what you're building and which edition fits. We'll walk you through deployment, identity, and governance for your environment.
Just getting started or evaluating solo? The open-source edition is the same engine — install it and run it today, no account.