Docs / AEP / Self-Managed
Coming Q4 2026Helm install, Super User token activation, and HA configuration for running AEP in your own cluster.
Self-Managed AEP deploys into your own Kubernetes cluster or VPC, under an org-wide license rather than a per-machine key. This guide previews the setup flow ahead of the Q4 2026 launch — see the Self-Managed product page for pricing and to talk to sales about planning your deployment.
AEP ships as a Helm chart. A typical install targets its own namespace:
Your deployment needs network reachability to Licensing to reserve seats and activate — the first-run setup calls out to Licensing with a Super User token (generated when your org's Self-Managed license is provisioned) to bind the cluster to your org's seat pool. Fully offline / air-gapped activation is planned but not yet supported; talk to sales if that's a hard requirement for your environment.
The Business and Enterprise tiers support multi-replica, HA deployment — the Helm chart's ha.enabled=true value adds a second control-plane replica and a shared session store, so a single pod restart doesn't interrupt in-flight skill runs.