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.
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. Full minimums: requirements.json and Sizing and requirements.
- Skill calls, including skills served over MCP, agent workspaces and agent turns (Claude Code, Codex or OpenCode, on the executor fleet) run in your cluster. Model calls go through the always-on LLM Gateway.
- Install: one installer covers both editions, and 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.