aether
Platform

Kubernetes, with the dangerous parts removed.

Aether is built on three layers: what you see (standard Kubernetes and a clean portal), what runs your infrastructure (dedicated compute, Ceph storage, isolated networks), and a management layer you never have to think about — because it's hidden even from attackers.

Provisioning

From click to kubeconfig in about three minutes.

Cluster creation is a fully automated pipeline — you can watch every step stream live in the portal while it runs.

  1. 01

    Request

    You create a cluster from the portal, API or (soon) Terraform. Aether validates quota and allocates the cluster its own VLAN and private subnet before anything boots.

  2. 02

    Control plane

    A dedicated kube-apiserver, controller-manager and scheduler start as pods in the management cluster, backed by an isolated, replicated datastore. Ready in seconds.

  3. 03

    Networking first

    Cilium networking is deployed and a dedicated proxy fronts your API server before any worker exists — so nodes join a fully-formed network, not a half-built one.

  4. 04

    Workers

    Talos Linux worker VMs boot inside your private VLAN, verify themselves against the cluster CA, and join. No SSH keys were created at any point.

  5. 05

    Platform services

    Registry access, OIDC, DNS records, TLS, storage classes and observability wiring are applied automatically. Your kubeconfig arrives with everything already working.

Included services

Nine services on every cluster. Zero setup.

These usually live on a platform team's backlog for a quarter. On Aether they ship free with every cluster — deployed before you first sign in.

Aether Identity

Team single sign-on (OIDC) for portal and kubectl with roles, MFA and social login.

Aether Container Registry

Private container registry with vulnerability scanning on every push.

DNS + TLS

DNS records and publicly trusted TLS certificates, managed for you.

Aether Observability

Dashboards over metrics, logs and traces — plus panels right in the portal.

Cluster autoscaler

Node pools scale between your min and max; unhealthy machines are replaced.

Datastore backups

Continuous WAL archiving of your control-plane datastore.

Block + shared storage

Ceph-backed block volumes and shared CephFS filesystems many pods can mount at once.

VolumeSnapshots

Point-in-time snapshots of persistent volumes on demand.

metrics-server

Resource metrics for kubectl top and horizontal pod autoscaling.

Node pools

Exact sizes, not T-shirt tiers.

Pick the precise vCPU, memory and disk per node — no rounding up to the next instance type. Fixed pools bill a predictable flat month; autoscaling pools bill per node-hour, and nodes that live under 15 minutes are free.

Automation

An API built for Terraform from day one.

Full CRUD, idempotent operations, stable IDs, API tokens — and webhook events that notify your systems as clusters are created, become ready, upgrade or degrade. Everything the portal does, the REST API does. A Terraform provider and the aether CLI are next on the roadmap.

See it provision for yourself.