enum vs Google Cloud.
Kubernetes without US jurisdiction.
Run the same upstream Kubernetes you run on GKE, from a German company, billed in euros.
Side by side.
What's included, what's extra.
Why teams switch.
No CLOUD Act
Google is a US company; an EU region does not change that. enum GmbH has no US entity in its structure.
Euros, not surprises
Published prices in euros, a highly available control plane included, no fees for storage operations.
Same Kubernetes
Upstream Kubernetes. Manifests, Helm charts and GitOps pipelines move over unchanged.
Questions.
About switching from GKE.
Is Google Cloud subject to the US CLOUD Act?
Yes. Google is part of Alphabet, a US company, so the CLOUD Act applies regardless of the region. enum has no US entity in its structure.
What does GKE cost compared to enum?
GKE adds a cluster management fee, Cloud NAT per hour and per GB, load balancer forwarding rules and data processing, and charges for storage operations. enum includes the control plane, NAT and the load balancer's IPv4, and bills compute, storage, load balancers and traffic in euros.
How is enum different from GKE Autopilot?
Autopilot bills per pod resource and manages nodes for you. On enum you choose node sizes and pay per node hour, with optional commitments; if you want us to run the platform for you, there is DevOps as a Service.
Can I migrate from GKE 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.
Curious what you'd pay?
Build your setup in the calculator.
Or talk to an engineer about your current Google Cloud bill.