SurrealDB runs on Amazon EKS, Google GKE and Azure AKS. This page covers the three deployment models available on them - managed Scale, a self-hosted Enterprise cluster, and a single node - and which one fits.
Production multi-node SurrealDB uses shared distributed storage with replication across nodes. For managed HA, use the Scale plan. Self-hosted multi-node clusters on Kubernetes run SurrealDS, the distributed storage engine in SurrealDB Enterprise, with the SurrealDB operator.
For a single-node deployment on Kubernetes - including a cluster you create with EKS, GKE, or AKS - start with Deploy on Kubernetes. For how the multi-node model works in general, see Run a multi-node cluster.
The managed control planes
Each of the three major clouds offers a managed Kubernetes control plane. The control plane is the only part they manage for you; how SurrealDB storage is provided is still your choice - a single node with SurrealKV on a persistent volume, or a multi-node cluster on distributed storage (Scale or Enterprise).
| Provider | Service |
|---|---|
| AWS | Amazon Elastic Kubernetes Service (EKS) |
| Google Cloud | Google Kubernetes Engine (GKE), including Autopilot |
| Microsoft Azure | Azure Kubernetes Service (AKS) |
Choose a path
| Goal | Path |
|---|---|
| Managed multi-node HA (recommended for most teams) | A managed Scale cluster, with the storage layer operated for you |
| Self-hosted multi-node HA on EKS, GKE, or AKS | SurrealDS with the SurrealDB operator, a node in each availability zone, and an S3-compatible bucket that supports conditional writes or an Azure Blob Storage container |
| Single SurrealDB pod, SurrealKV on a volume | Deploy on Kubernetes on a cluster you manage |
Next steps
Deployment models - single-node vs multi-node vs managed
Instances - the managed option
Scale - pricing for managed multi-node clusters
Observability once an instance is running