Features
What is included, and what you can add
High availability control plane
Switch a running cluster from one control plane node to three, with automatic failover and a 99.95% uptime SLA, for €40/month per cluster.
Upgrades from the UI
Move to a newer Kubernetes version from the UI. We support the three latest minor releases.
Starter Kit
An optional small welcome page, wired to ingress, so you can see the cluster answer from the start.
Load balancer included
A public endpoint with HTTPS on every cluster. Add your domain, point a CNAME at it, done.
Plain kubectl
It's upstream Kubernetes. Use your existing manifests, Helm charts, GitOps tooling and CI.
Credentials on demand
Create cluster credentials per person or pipeline and download a ready-to-use kubeconfig.
REST API
Automate clusters, node pools, domains and kubeconfigs from scripts and CI, with access keys scoped to exactly what each job needs.
MCP server for AI agents
Give your AI assistant a key of its own. It can check on clusters, read the activity log and resize pools, within the permissions you set.
Load balancer included
HTTPS is part of the cluster
Every cluster has a public endpoint behind our load balancer, and we issue and renew the TLS certificates. Add your domain, point a CNAME at the cluster, and it is reachable over HTTPS.
; the only record you need
shop.example.com.CNAMEk3v9q2xr7m1p4tza.hyperkub.net.
visitor
https://shop.example.com
hyperkub load balancer
TLS · public IP
your cluster
Ingress → Service
01
Add your domain
In the control plane, next to the cluster it should reach.
02
Point a CNAME at the cluster
Each cluster has its own endpoint on hyperkub.net to point it at.
03
Traffic arrives over HTTPS
Our load balancer handles the TLS certificate. Inside the cluster, a standard Ingress routes the traffic to your services.
What you would otherwise set up yourself
On many managed Kubernetes services, exposing an app over HTTPS means:
- Provision a cloud load balancer, billed every month
- Reserve a public IP address and attach it
- Install and run an ingress controller
- Set up cert-manager and a Let's Encrypt issuer
- Keep all of it patched and renewing
On Hyperkub it is one CNAME record, and the load balancer is part of the price.
Start with one small cluster
Create one in the EU, and run kubectl apply a few minutes later.