Skip to Content

Platform architecture

Each tenant runs as its own deployment with its own database and application instances: what stays shared, and what higher tiers dedicate.

Most of this documentation describes what you can configure. This page describes what runs underneath it: how your tenant is separated from every other tenant, what that separation guarantees, and what it does not. It matters mainly for two conversations (a security review and a capacity question), and the answers to both follow from one design decision.

Single-tenant by deployment, not by query

Many identity services are built as one large shared system: every customer's users, sessions, and logs live in the same data model, kept apart by a tenant identifier that each query has to carry. Isolation there is a property of the application code, and it holds as long as every query gets that filter right.

This platform is built the other way around. Each tenant is its own deployment. It has:

  • its own database, with its own credentials, and
  • its own application instances, which serve only that tenant.

No record is stored in a collection shared with another tenant, and no query needs a tenant filter to stay separated, because a tenant's processes have no route to another tenant's data in the first place. The isolation is a property of the deployment, so it does not depend on application code being correct.

For a security review, this rules out a whole class of findings by construction: a missing filter, an object reference that is not checked, or a cache key collision cannot expose another customer's records, because those records are not reachable from the process handling your request.

What is dedicated, what is shared

Separation is not the same as running on private hardware. In the standard deployment:

LayerDedicated to your tenantShared
DataYour database, with its own credentialsThe database environment hosting it
ApplicationYour application instancesThe cluster the instances run in
Configuration, keys, logsAll of it–

Signing keys, encryption keys, session state, audit logs, and configuration are always yours alone. There is no shared key material and no shared configuration store.

The two shared layers are what the higher tiers let you remove:

  • Private database cluster (optional on Advanced, included on Pro): a database environment dedicated to your tenant, with compute and storage not shared with any other customer. Without it, your database is still yours alone; only the environment hosting it is shared.
  • Private deployment (Pro): infrastructure dedicated to your tenant, separate from the cluster other deployments run in.

Both are commercial and operational upgrades to an isolation model that already exists. Neither changes how your data is separated.

The same architecture in every plan

The Free plan runs on the same architecture as the Pro plan. It is not a sandbox, a shared demo environment, or a different code path. It is a full deployment with a smaller license. Two practical consequences:

  • What you validate on Free or during a Trial behaves the same way in production. Protocol behaviour, token contents, and the admin console are identical.
  • Upgrading a subscription raises limits and unlocks features. It does not migrate your tenant to a different stack, and it does not require a re-import, a new issuer, or a new set of client credentials.

Entitlements are evaluated live against your license, so a tier change takes effect without a restart. See Plans & add-ons.

Availability and updates

Every deployment runs multiple application instances rather than a single process, so the loss of one instance does not take the tenant offline. Because the instances serve only your tenant, load from another customer cannot slow your sign-ins down, and a problem in another tenant's deployment cannot affect yours.

Running your own instances also means your tenant has its own version state and its own maintenance window. Two things follow from that:

  • Updates are rolled out per deployment rather than to all customers at once.
  • From Essential upwards you can opt into the preview deployment to receive new versions early, on your tenant only, before they become the general release.

Data location

The platform is operated in a data center in Germany and processes data in line with EU data protection requirements. This applies to every plan, including Free. Signing keys, encryption keys, and the audit log stay within your own deployment; nothing about a sign-in is processed by a third-party identity service.

Reference

PropertyTrialFreeEssentialAdvancedPro
Dedicated database per tenant✓✓✓✓✓
Dedicated application instances✓✓✓✓✓
Multiple instances per deployment✓✓✓✓✓
Data center in Germany✓✓✓✓✓
Preview deployment (early access)––✓✓✓
Private database cluster–––Optional✓
Private deployment––––✓

See also

  • Plans & add-ons, for the feature and sizing limits of each tier.
  • Rate limits, for the request throughput a single client may use.
  • Audit logs, for the tamper-evident log kept inside your deployment.
  • Signing keys, for the key material issued to your tenant alone.

On this page