Stand it up inside
your own perimeter.
One Helm chart. Three deployment shapes. Your Postgres, your NATS, your KMS — bring the data plane you already operate.
This page is the operator handbook for SREs and platform teams standing up exAI inside their own VPC, their own data centre, or a sealed air-gapped site. No marketing — install command, sizing tiers, runtime requirements, upgrade flow, and the airgap mode that ships zero outbound bytes.
Same chart.
Three postures.
Pick the posture that matches your regulator, your network, and your team. Every mode boots from the same Helm chart, the same audit log schema, the same control plane API. No second-class installations, no feature drift between shapes.
Multi-tenant managed
Shared control plane operated by exAI on AWS · GCP · Azure. Per-tenant Firecracker pools, per-tenant KEKs, isolated NATS subjects. The fastest path to first useful run.
- Fully managed control plane
- Per-tenant data isolation guarantees
- 99.95% SLA · 24×7 SRE rotation
- SOC 2 Type II · ISO 27001 inherited
BYOC · your AWS / GCP / Azure
Single-tenant control plane provisioned into your own cloud account. exAI manages the workload, your CISO holds the keys. Network never leaves your VPC.
- Customer-owned VPC · subnets · KMS
- exAI-managed lifecycle · upgrades · pages
- Cross-account IAM · least-privilege role
- Audit log streamed to your CloudTrail / SIEM
Air-gapped on-prem
Full offline install onto your own metal or private cloud. Signed model artefact bundles delivered via physical media. Zero outbound egress required, ever, by design.
- Helm chart · 100% offline install
- Cosign-verified model bundles · USB · NAS
- Local-only telemetry · audit to your SIEM
- Quarterly air-gapped release channel
One chart.
Two values files.
The chart splits cleanly into a control plane and a data plane. The control plane is the workload exAI ships and upgrades. The data plane is yours — your Postgres, your NATS, your object storage — wired in via short, declarative values.
The chart structure is intentional: a top-level controlPlane block and a top-level dataPlane block. Control plane values cover replicas, ingress, image pull secrets, and signing keys. Data plane values point at the Postgres, NATS, and object storage you already operate.
exAI does not embed a Postgres, a NATS, or a MinIO. We refuse to operate the customer's persistent data. The chart accepts connection strings, KMS ARNs, and bucket references — that's it. Your DBA team owns durability, your platform team owns the message bus, and the audit log flushes to your S3 bucket under your KMS key.
Upgrades are a normal helm upgrade with a one-shot migration job. Rollbacks are first-class: every release ships with a tested down-migration and a signed manifest of what changed.
$ helm repo add exai https://charts.exai.dev$ helm install exai exai/exai-platform \$ --namespace exai-system \$ --create-namespace \$ --values values.production.yamlSized for your
seat count.
Three reference profiles — pilot, standard, strategic. The middle column is what most customers run. The numbers are list price for AWS BYOC; expect a 25–40% discount in your account with reserved capacity, and a different mix on GCP / Azure / on-prem.
No callback.
No telemetry. Sealed.
The hardest deployment shape we ship. Tested in classified-tier facilities, OT/ICS networks, sanctioned regions, and SCIFs. Designed against a single rule — zero outbound bytes, ever — and verified against it in CI.
Air-gapped mode is not a managed-cloud feature with the internet turned off. It is a separate release channel, built every quarter, signed end-to-end, and shipped to you as a single tarball with a manifest of every byte inside it.
Model artefacts are delivered the same way — on signed, encrypted physical media, hand-walked through the procurement chain into the secure facility. The bundle contains weights, tokenizer, and a cosign signature that your inbound process verifies before any byte touches the data plane.
At runtime there is no callback path. The audit log streams to your local SIEM only. There is no support tunnel that phones home, no diagnostic that uploads, no licence check that pings — every line of this is audited against an airgap-verifier in our own CI before a release tag is cut.
Your data plane. Yours.
Helm chart. Customer-managed Postgres, NATS, KMS. Three deployment shapes. One audit log schema. No second-class installation, no second-tier support. Bring it inside your perimeter — or run it sealed, offline, signed.