Skip to main content
Pick by where your data must stay and how much of xpander you want to run yourself.

​
Hybrid or Air-Gapped

Choose Hybrid for data residency: runtime data, credentials and model keys stay in your VPC, while xpander cloud manages agent definitions, identity and the skills catalog. It is the smaller footprint and the default. Choose Air-Gapped for zero dependency on xpander cloud: sealed or classified networks, strict egress policies, or full operational ownership. “Air-gapped” means air-gapped from xpander’s cloud. Internet-backed skills can stay enabled or be sealed off. The full requirements are published at charts.xpander.ai/requirements.json. The installer shows the same numbers before it changes anything.

​
On both self-hosted deployments

  • Kubernetes: the reference installs run on Amazon EKS, and the guides are written for AWS. Any Kubernetes 1.28 or later with a CNI, cluster DNS and a CSI driver with a default RWO StorageClass meets the chart’s requirements. No other distribution has a step-by-step guide yet.
  • Skill calls, including skills served over MCP, and the agents’ workspaces run in your cluster.
  • Agent turns (Claude Code, Codex or OpenCode) run on the executor fleet, a warm pool the chart always renders. See Sizing and requirements.
  • Model calls go through the LLM Gateway, always on in your cluster. See LLM Gateway on a self-hosted install.

​
Install

Run the installer from a terminal with kubectl access to the target cluster. The same installer covers both editions: its first question is which one.
xpander Chat generates a personalized one-liner with everything filled in.

​
Next steps

Install Hybrid

The full Hybrid guide.

Install Air-Gapped

The full Air-Gapped guide.

Set up an EKS cluster

VPC, IAM, nodes and add-ons.

Size your cluster

Footprint, workspaces and the executor fleet.

Set up the AWS Operator

IAM roles for AWS skills.

Apply least-privilege IAM

Three-tier IAM roles.