What runs where
- In your environment: the web UI, control plane, a self-hosted Supabase stack (auth, storage, edge functions) and the data tier (PostgreSQL, Redis Stack, MongoDB), as one Helm release in one namespace. Agent skill calls (including MCP) and agent workspaces run there too. The Company Brain runs there as well, on by default (
brain-ingest, one pod). - Sent to xpander: nothing. No heartbeats, no catalog sync, no telemetry.
- Your choice: your LLM endpoint, cloud services such as Bedrock, S3 or SES, and the registry you mirror from at install time.
- MCP clients (Claude, ChatGPT, Cursor) reach Omni once you set
global.mcp.publicUrl. Until then, withui.env.VITE_OMNI_MCP_URLempty too, Platform > Agents > Channels shows Not offered on this install, and the License page’s Capabilities card shows the value to add. - Private mode needs
global.network.internetEgress: false. Withtrue, built-in skills that use public APIs (for example arXiv and HackerNews) call them from the cluster. Withfalse, those skills do not work.
Air-Gapped Security Architecture
Zero egress, the signed Ed25519 license, local sign-in, and the full install-time / run-time / never egress table.
Three things define an air-gapped install
- The license is the identity. Two sealed files (
install.jsonandactivation.json, formatxpander-license/v2) plus the organization id you pass with--org. No console IDs and no API key. Older single-filelicense.json(v1) installs carry the org id inside. The installer generates the environment id and the first install creates your organization in-cluster. Single-tenant: one license, one organization. - Images come from your own registry mirror. xpander delivers them through the gated
xpanderaihubDocker Hub org with a per-customer read token. The installer mirrors them, or you mirror them yourself on a sealed network. - Image tags are pinned per release. The chart refuses unpinned images, and an upgrade needs the new bundle mirrored first.
--edition airgap: a checklist, license validation, mirroring when needed, and a live watch over the install.
“Air-Gapped” means from xpander’s cloud, not necessarily from the internet. Internet-backed skills (web search, docs search, TTS) can stay on or be sealed off. Ask your xpander contact about the sealed hardening profile.
What talks to what
Nothing goes to xpander at run time. Every outbound connection is one you choose, and every inbound one lands on your ingress controller over your own path (internal DNS, VPN, private load balancer). Full table: Air-Gapped Security Architecture.Outbound connections
Outbound connections
Inbound connections
Inbound connections
The host names are the chart’s defaults and each can be renamed (Domains, Ingress & DNS):
Prerequisites
Published requirements: requirements.json.
The executor fleet and the always-on AI Gateway add to these numbers. Their requirements, including the XFS StorageClass the fleet needs, are below.
Executor fleet and AI Gateway requirements
Executor fleet and AI Gateway requirements
- The executor fleet (where Claude Code, Codex and OpenCode turns run) adds to these numbers and needs a namespace that admits PodSecurity
baseline, Landlock on its nodes (orglobal.fleet.landlock.enabled: false) and XFS withprjquota. No privileged container or node preparation. See Node prerequisites. - The AI Gateway is always on, and agents’ model calls go through it. It adds its pods (0.5 vCPU / 1 GiB requested each, up to 1 vCPU / 4 GiB) and the
llm-gwimage. See AI Gateway on a self-hosted install. - The fleet storage class. The fleet starts warm with one executor and needs a StorageClass that mounts XFS with
prjquotafor its 500 GiB per-executor volume. Without that class or driver, the chart renders the executor idle atreplicas: 0, annotatedxpander.ai/fleet-idle-reason, so an--atomicinstall never waits on a volume that cannot bind. Create the class and the next upgrade starts it. Sizing tiers: Sizing and requirements.
Next steps
Install Air-Gapped
The one-liner, mirroring and the license.
Review the install before you run it
--manual, --values-out and --dry-run..tgz) covers bring-your-own ingress, private CA and proxy, SMTP, internet posture, builtin-skills seeding and Bedrock region pinning.
