enum vs Hetzner.
Kubernetes you don't have to run.

Hetzner gives you great servers. On enum, the Kubernetes on top is operated for you: control plane, upgrades and networking.

Side by side.
Who runs what.

enumKubernetes on Hetzner
Kubernetes control planeOperated by enum, highly available, includedInstalled and operated by your team
UpgradesRolled out node by node by enumPlanned and executed by your team
Private networkingPrivate clusters by default, NAT includedNetworks, firewalls and routing set up by you
Load balancerFlat monthly price, IPv4 includedHetzner Load Balancer, billed per hour, connected by you
Object storageS3-compatible, no request feesSeparate product or your own setup
LocationFrankfurt, German companyGerman company, data centers in Germany and abroad

Why teams switch.

Stop running the control plane

etcd, certificates, upgrades and failover are our job. Your team works on the product.

Private by default

Clusters start private, with NAT included. No firewall puzzle to get right first.

Help when it matters

Engineers who know the platform, and Enterprise Support or DevOps as a Service if you want more.

→We plan and run the move with you.How migration works

Questions.
About switching from Hetzner.

Why pay for managed Kubernetes instead of servers?

Because running Kubernetes yourself costs engineering time: control plane, upgrades, certificates, networking and on-call. On enum the highly available control plane is included and operated for you.

Do I lose control with managed Kubernetes?

No. You get upstream Kubernetes with full API access. enum operates the control plane and the nodes underneath; your workloads and configuration stay yours.

How does pricing compare?

Raw servers are cheaper per CPU than a managed platform. On enum the control plane, NAT, 100 GB of disk per node and the load balancer's IPv4 are included, and you skip the time to run it all. The calculator shows your setup.

Can I migrate from Hetzner to enum?

Yes. enum runs upstream Kubernetes, so manifests, Helm charts and GitOps pipelines move over unchanged, and S3 tools work against enum Object Storage as they are. Our engineers plan and run the move with you.

How do we get Kubernetes clusters?

Kubernetes clusters are set up on request today; self-service creation launches in Q4 2026.

Tired of running Kubernetes yourself?
Let us run it.

Tell us about your cluster today. We plan the move with you.