Skip to main content
The same Helm charts deploy three profiles: standard in-tenant, sovereign (in-region, data-residency pinned, KSA profile available), and fully air-gapped — no internet egress at install time or runtime. What the air-gapped profile covers: container images mirrored to your local registry with digests preserved, offline Helm repository, offline schema and dashboard import, offline license activation, and an update path that never requires a connection.
Sovereignty here is architectural, not contractual: because inference, data, and state all run inside your perimeter, there is no traffic to police.
The complete air-gapped procedure ships in the release package (install/), and every release bundle is self-contained by design — that is what the package verification chain exists for.