Why Chapman AI

Six reasons that drove the architecture, not slogans bolted on at marketing time.

01

Deployment flexibility is a first-class feature

Most AI platforms force a choice: their hosted product or build your own. Chapman AI gives you three options that share the same codebase. Start on our shared multi-tenant platform to evaluate, move to a per-tenant subdomain for production, and graduate to your own custom domain when end users should never see our brand. The same platform underneath — no migration when your needs change.

02

Tenant isolation enforced by the database, not just the code

Every tenant-scoped table has a tenant_id column with a Postgres row-level security policy. The database itself rejects cross-tenant reads even if application code forgets a WHERE clause. That defence-in-depth model is hard to retrofit later. Chapman AI was built with it from the start.

03

Enterprise auth without the enterprise build

Email magic-link or password by default. SAML, OIDC, Google Workspace, Azure AD, and SCIM provisioning available per tenant via WorkOS. You don't write SAML, your enterprise customer doesn't get blocked at procurement.

04

White-label means white-label

Chapman AI branding is invisible by default in custom-domain deployments. Your logo, your colours, your product knowledge, your domain. End users see your brand. We are infrastructure they don't see.

05

UK ownership, EU data residency

Hosted on Google Cloud in London (europe-west2). Owned by Chapman AI Ltd, registered in the UK. Data stays in-region by default. GDPR-aligned by architecture, not by retrofit.

06

You can change AI providers

The platform fronts Azure OpenAI, Anthropic, and provider-of-your-choice through one consistent interface. Per-tenant model and prompt configuration. If a provider becomes more expensive, less capable, or geopolitically inconvenient, you switch without rebuilding.

Ready to see it on your domain?

Tell us about your use case and we’ll spin up a tenant for you to evaluate.