The open core, with the guarantees an enterprise needs.
Everything the family gives you, plus what security, procurement and scale ask for: dedicated infrastructure, single sign-on, audit trails, an SLA, and a contract that fits your organisation. The same code the open core runs: no fork, no separate product, no lock-in, and the assurances around it that a large deployment requires.
The same software, with the edges an org needs.
None of this changes the code you evaluate. It is the operating, the identity surface, the support and the paperwork around it.
Dedicated tenancy and infrastructure on QuxCloud, or run in your own cloud with our help. Data residency and network isolation where your policy requires it.
Single sign-on over SAML and OIDC, SCIM provisioning and de-provisioning, and audit logs of who did what and when: the parts a directory and a security team expect.
Priority support with a named engineer who knows your deployment, response times in writing, and an uptime SLA on the managed service.
A security review, a DPA, and terms that fit your process, including a commercial licence for the source-available kits, so your use is covered without a question mark.
Enterprise is a wrapper, not a different build.
- The same open core. You evaluate the real libraries, then get guarantees around them, never a proprietary fork you cannot inspect.
- No lock-in, at your scale too. The schema and the data stay yours; leaving remains a migration you control, not a contract you have to escape.
- Isolation the database enforces. Tenant separation is row-level security in Postgres, so a query that forgets whose data it reads returns nothing at all.
- One contact for the whole family. Billing, tenancy, identity, mail and the applications built on them, under one agreement and one support line.
Bring it to your organisation.
Tell us about your scale, your security requirements and your timeline, and we will take it from there.