Built on Confidential Compute

Managed Kubernetes without handing over the keys.

Managed Kubernetes (RKE2) with three masters on confidential VMs. The kubeconfig is sealed to a key made in your browser, and the masters refuse any node you didn't sign.

Memory encrypted by the processor (AMD SEV-SNP). The disk unlocks only after attestation.

Why Hippius Kubernetes

Our machines.
Your admin rights.

Control plane on confidential VMs

Three masters with embedded etcd, each on its own confidential VM. The processor encrypts their memory, and the disk unlocks only after attestation.

Admin access only you can open

The masters seal the kubeconfig to your cluster key, and it is decrypted in your browser. After launch, Hippius holds no readable kubeconfig, no certificate authority and no shell on the nodes.

Every node signed by you

Adding a node is signed in your browser with your key. The masters refuse any node you didn't sign, so Hippius can't add a machine of its own.

By design

What we can't do. On purpose.

Your cluster key is made in your browser, and only its public half ever reaches us. So a few things are simply not possible.

  • We can't open your kubeconfig.

    The masters seal it to your key. It is decrypted in your browser, and neither your key nor the kubeconfig is sent anywhere.

  • We can't slip a node into your cluster.

    Every node is signed with your key. The masters check the signature and refuse any node you didn't sign.

  • We can't recover your key file.

    Nobody, Hippius included, can reset it. Keep it backed up, for example in a password manager.

Use cases

For clusters nobody else should administer.

  • Sensitive workloads

    Services and jobs that handle data the servers they run on must not be able to read.

  • Internal services and batch jobs

    Workers talk over your private network and have no public IP. The API answers only the ranges you allow.

  • Clusters you can take with you

    Daily Velero backups, on unless you turn them off at creation, are encrypted inside the cluster before they reach your own Object Storage, and restore into any Kubernetes cluster, on Hippius or not.

FAQs

An RKE2 cluster (v1.34.3) with three masters running embedded etcd, each on its own confidential VM with a public IPv4 for the API. Nodes talk over your private network with the Canal network plugin. All three masters run in the country you choose.