Skip to content

Platform model

Aether is built around a clean split: you own and run your tenant clusters; we run the control plane. Understanding that split makes everything else fall into place.

A tenant cluster is a Kubernetes cluster that belongs to your organization. It’s where your workloads run. You create as many as you need, on the regions you choose, and you have full kubectl-level control over what runs inside them: Deployments, Services, ingress, network policies, persistent volumes, and so on.

Every cluster has a Kubernetes control plane — the API server and the components that schedule and reconcile your workloads. On Aether, the control plane is fully managed. Aether provisions it, operates it, keeps it healthy, and backs it with a fully managed datastore.

You never:

  • Manage, patch, or upgrade the control plane’s machines.
  • SSH into control-plane nodes.
  • Size, scale, or babysit the control-plane database.

You only ever interact with the control plane through its Kubernetes API — the same way any Kubernetes client does.

Each tenant cluster is isolated from every other tenant. Your clusters get their own private network for workloads and nodes, their own control plane, and their own datastore. One organization’s clusters can’t see or reach another’s.

Aether handlesYou handle
Provisioning and operating the control planeYour workloads and manifests
Control-plane health, datastore, and backupsYour application data and PVCs
Installing the Cilium CNIYour NetworkPolicy rules and ingress
Bringing up and tearing down worker nodesChoosing node-pool sizes and counts
Managed load balancers, block storage, registryUsing them from your workloads