Hetzner vs AWS: Cloud Cost and Features Compared
Hetzner is often the better value for predictable virtual machines, dedicated servers, storage, and network workloads that a team can operate itself. AWS is the better fit when managed databases, event-driven services, global regions, deep IAM, compliance programmes, or rapid elasticity remove enough engineering work to justify their cost. Compare a complete workload, not nominal vCPU and RAM prices.
Match services by responsibility, not by name
A Hetzner Cloud server and an Amazon EC2 instance both provide compute, but CPU allocation, storage, network limits, availability constructs, images, and support differ. Hetzner also offers dedicated servers; AWS provides a much larger catalogue of managed services. Replacing RDS, SQS, Lambda, EKS, or CloudFront with software on virtual machines transfers patching, backups, scaling, and on-call ownership to the customer.
Create an architecture inventory showing each managed AWS capability and the Hetzner replacement, owner, recovery target, and staff time. For Kubernetes, compare self-management with Amazon EKS, including control-plane charges and the operational work EKS still leaves to the customer. “Both run Kubernetes” does not make their responsibility models equivalent.
Build a date-stamped total-cost model
Use each provider's current catalogue, including AWS EC2 pricing, for the exact location, architecture, operating system, and purchase model. Include block-storage performance and snapshots, load balancers, public IPv4, NAT, inter-zone and internet traffic, DNS, monitoring, support, backups, reserved commitments, taxes, and currency. Then add engineering and expected incident cost.
Benchmark the real application for CPU steal or contention, storage latency and throughput, network throughput, cold provisioning, and failure recovery. A “four vCPU” label is not a cross-provider performance unit. Keep the workload steady, publish the configuration and date, and repeat after changing instance family or region.
Location does not settle compliance
Hetzner's location list includes Germany, Finland, the United States, and Singapore. AWS also lets customers select regions, but a region choice alone does not establish GDPR compliance or immunity from government access. Assess the contracting entity, data-processing agreement, subprocessors, support access, transfer mechanism, telemetry, backups, retention, and who controls encryption keys. AWS's GDPR centre describes its shared-responsibility material; legal counsel should map it to the workload.
Choose Hetzner for a bounded architecture with a team capable of operating it and an exit plan based on standard images, databases, and object formats. Choose AWS when specific managed services or global capabilities produce measurable delivery or reliability gains. Pilot a backup restore, loss of one location, account compromise, and provider migration before declaring either platform cheaper or safer.
Published · Updated