Skip to main content
xpander installs from a Helm chart into your own Kubernetes cluster. On AWS that cluster is EKS, for the Hybrid deployment (execution in your VPC, control plane in xpander’s cloud) and the Air-gapped deployment (everything in your cluster, no connection to xpander).

​
Before the install

​
Install

The installer asks which edition you are installing and walks through the rest; run it from a terminal with kubectl access to the cluster. Hybrid identifies itself with the organization id, environment id and deployment-manager key from the install card in Xpander Chat. Air-Gapped uses the two signed license files instead.
  • Hybrid deployment: one-liner install, external access and DNS, LLM keys, upgrades.
  • Air-gapped deployment: mirroring, sealed installs, local LLM inference, data tier, domains and DNS, egress table.

​
After the install

Expect one Running, 1/1 pod per application service: agent-controller, agent-worker, api, aws-operator, chat, code-runner and mcp. Expect also the executor fleet, a StatefulSet whose pods run agent sessions on Claude Code, Codex or OpenCode. In Xpander Chat, Settings > Locations shows the cluster with a heartbeat status per component. On Hybrid, one component reaches xpander’s cloud: the Agent Controller, the service that mediates every model and skill call. On Air-Gapped, none does.