enum vs AWS.
Same standards, shorter bill.
Upstream Kubernetes and S3, like you know them, from a German company with no US parent and an invoice you can read.
Side by side.
What's included, what's extra.
Why teams switch.
No CLOUD Act
AWS is a US company; an EU region does not change that. enum GmbH has no US entity in its structure.
A bill you can predict
Five line items in euros instead of per-hour, per-GB and per-request charges stacked on each other.
Nothing to relearn
Upstream Kubernetes and the S3 API. Your manifests, charts and tools keep working.
Questions.
About switching from AWS.
Is AWS subject to the US CLOUD Act?
Yes. As a US-headquartered company, AWS falls under the CLOUD Act regardless of where the data is stored, including its Frankfurt region. enum has no US entity in its structure.
What does AWS EKS really cost?
Beyond the control plane fee per cluster-hour, an EKS setup typically adds instances, volumes, NAT Gateways per availability zone, load balancer hours and capacity units, data transfer, public IPv4 addresses and S3 request fees. enum includes the control plane, NAT and the load balancer's IPv4, and bills compute, storage, load balancers and traffic.
Is enum Object Storage S3-compatible?
Yes. aws-cli, rclone, s3cmd and the AWS SDKs work without code changes. Storage and outgoing traffic are billed; requests are free.
Can I migrate from AWS 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 AWS bill.