Skip to content
Deployment

One platform. Your perimeter.

Start shared for a pilot, graduate to a dedicated deployment, or run fully air-gapped. It's one codebase the whole way — a dedicated install is just a multi-tenant platform with a population of one.

Shared

Spin up in minutes on an isolated slice of a shared cluster.

  • Isolated org slice
  • Fastest time to pilot
  • Upgrade any time
topology

shared cluster

tenant
you
tenant
Graduation

From a shared pilot to your own perimeter.

The same platform follows you. Graduating is a migration, not a rewrite.

01

Pilot on shared

Spin up in minutes on an isolated slice of a shared cluster.

02

Graduate to dedicated

Export the org slice, provision a single-tenant stack, switch over.

03

Go air-gapped

Package for offline licensing and run with no egress — paired with models self-hosted inside your perimeter.

No rewrite, ever

The platform doesn't change — only where it lives.

One codebase

No `if (singleTenant)` forks. Dedicated = population of one.

Offline licensing

Signed licenses drive what runs — no call home to activate or renew.

Models set the boundary

Self-host models inside your perimeter and nothing leaves it. Hosted frontier models need outbound access to the provider.

Bring one database. Leave with a pipeline.

A pilot runs on one real source of yours, on an isolated slice or air-gapped if you need it. You keep everything that gets built.