Why enum beats AWS.

AWS offers GDPR-relevant contractual terms and EU regions, but AWS is a US company subject to the US CLOUD Act and FISA Section 702, which can compel access to data even when it is stored in an EU region. Selecting an EU region alone does not remove that exposure. enum is a German GmbH operating under German and EU law only, with no US parent and no US subprocessors.

Yes. As a US-headquartered company, AWS falls under the CLOUD Act regardless of where the data physically resides, including its Frankfurt region. enum has no US entity in its structure and is subject exclusively to German and European jurisdiction.

enum is operated by a German GmbH, in German data centers, under German and European law only, with no US parent and no US subprocessor. The company holding the data is therefore not subject to the US CLOUD Act or FISA Section 702. Selecting an EU region at a US-headquartered provider does not change the jurisdiction of the company holding the data; the corporate jurisdiction is what counts. For workloads bound by NIS2, DORA, or GDPR, that distinction is the difference between a contractual promise and a structural guarantee.

Beyond the per-cluster-hour control plane fee, an EKS setup typically accumulates charges for EC2 instances, EBS volumes, NAT Gateway hours plus per-GB data processing (multiplied across availability zones in an HA setup), load balancer hours plus LCUs, data transfer out, public IPv4 addresses, and S3 request fees. The headline price is rarely the bill. enum includes the HA control plane and bills a small, predictable set of line items: compute, block storage, object storage, a flat-monthly load balancer that includes an IPv4 address, and traffic. Outbound uses host-based NAT by default; a managed Cloud NAT Gateway (coming soon) will add a stable egress IP.

enum charges a single flat per-GB rate for outgoing internet traffic, with intra-region transfer included and IPv6 free. AWS bills outgoing traffic in regional tiers, layers per-GB data-processing fees on NAT Gateways and Load Balancers, and charges cross-AZ traffic separately, so the effective per-GB cost of moving data in an HA setup is hard to predict from the headline rate.

Both run upstream Kubernetes. enum Kubernetes Engine includes a highly available control plane per cluster at no separate charge, provisions clusters private by default with host-based NAT, and includes load balancing at flat fees, with a managed Cloud NAT Gateway coming soon. Standard manifests, Helm charts, and GitOps pipelines port over unchanged. EKS bills the control plane per cluster-hour and leaves private networking, NAT gateways, and VPC endpoints as separate pieces you assemble and pay for individually.

Yes. enum object storage implements the S3 API, so aws-cli, rclone, s3cmd, the AWS SDKs, and any tool built for S3 work without code changes. Data is erasure-coded across failure domains and stored in Frankfurt. enum bills storage and outgoing traffic, with no per-request or retrieval fees.

It depends on your requirements. For teams in regulated DACH industries that want hyperscaler-grade infrastructure under German jurisdiction without CLOUD Act exposure, enum offers Kubernetes, compute, object and block storage, and networking as a self-service public cloud operated in Frankfurt.

Yes. enum object storage is S3-API compatible, so tools like rclone, aws-cli, and s3cmd work without code changes. enum Kubernetes Engine runs upstream Kubernetes, so standard manifests, Helm charts, and GitOps workflows port over.

All enum infrastructure runs in Frankfurt, Germany, operated by a German GmbH under German and EU law, with further European regions on the roadmap.