Self-managed cloud infrastructure review
Hetzner can be a compelling infrastructure option when its network zone, processor architecture and self-management boundary fit the workload. The sensible comparison includes separate Internet Protocol (IP) addresses, backups, storage, traffic, tax and operator time, then tests recovery before migration.
Evidence checked 13 August 2026. Product availability, traffic allowances and prices can change. No lab benchmark, ticket test, uptime measurement, customer survey or paid ranking is claimed.
Decision first
A Hetzner Cloud server is infrastructure, not managed website hosting. Root access and an application image do not transfer responsibility for patching, monitoring, malware response, database repair or restore testing to the provider.
Geography
Hetzner documents six Cloud locations across four network zones. Products and transfer rules can vary by zone, so “Hetzner price” is not one globally interchangeable number.
| Network zone | Locations | Decision implication |
|---|---|---|
| eu-central | Falkenstein, Germany (fsn1); Nuremberg, Germany (nbg1); Helsinki, Finland (hel1) | Three European locations. Shared Ampere and Intel or AMD choices documented here; Object Storage is currently European only. |
| us-east | Ashburn, Virginia (ash) | Check the exact AMD plan, traffic allowance and price shown for this zone. |
| us-west | Hillsboro, Oregon (hil) | Validate audience latency and capacity independently before committing. |
| ap-southeast | Singapore (sin) | Compare zone-specific traffic and overage terms, not the European headline. |
Official location documentation says shared AMD and dedicated AMD are offered in all six locations, while shared Ampere and Intel or AMD products are limited to the European locations. Capacity can still be temporarily unavailable.
Compute choice
Shared-vCPU plans suit workloads with low to medium or variable processor demand. The product page distinguishes cost-optimized and regular-performance shared lines. Noisy-neighbor exposure and sustained-load needs should be tested on the exact plan.
Dedicated vCPUs are positioned for predictable, sustained processor demand and production applications. They reduce one resource-contention concern, but do not turn the server into a managed service.
CAX uses Arm64. Confirm the operating-system image, application packages, native extensions, monitoring agent and backup restore path support it. Hetzner does not permit cross-architecture restores, ISO use or rescaling.
Complete cost
The official price interface is dynamic and did not expose stable monetary values to our evidence crawler on 13 August 2026. This page therefore does not freeze a misleading “from” price. Use Hetzner's current selector, then record the configuration and date.
Do not compare this monthly ceiling directly with a managed host's headline price unless the support and responsibility boundaries are also equal.
Recovery
The optional feature is billed at 20% of the server price and provides seven daily slots. Hetzner chooses the backup time; the oldest backup rotates out when the next is created.
Server backups cover the server disk. Attached Volumes are not included. Application consistency, external dependencies and a working recovery runbook remain your responsibility.
Snapshots are manual, persist until deleted and are billed by compressed storage. They can be useful before a risky change, but are not a substitute for automated, independent application backups.
Responsibility map
| Layer | Primary owner | What to verify |
|---|---|---|
| Datacenter, host platform and documented cloud availability | Hetzner | The Service Level Agreement (SLA) covers individual cloud-server availability at 99.9% per calendar month, subject to exclusions and the claim process. |
| Cloud server operating system | Customer | Secure Shell access, firewall, package updates, least privilege, logs and intrusion response. |
| Web server, runtime, database and application | Customer | Configuration, updates, vulnerability response, performance, data integrity and email delivery. |
| Monitoring and incident response | Customer | Application-level probes, resource alerts, on-call ownership and a tested runbook. |
| Backup policy and restore proof | Customer | Volume coverage, independent copies, encryption, retention, restore tests and architecture compatibility. |
| Account verification and billing identity | Customer | Accurate information and a verifiable payment or identity path. Reviews can delay or reject account activation. |
Migration gate
Compare the DigitalOcean operational-fit dossier · Compare the Vultr operational-fit dossier · Compare the Akamai Cloud (Linode) duty-cycle dossier · Map the hosting support boundary
Evidence trail
Commercial claims were taken from current Hetzner product, documentation and legal pages. Prices are intentionally omitted because the rendered selector did not provide stable figures to the crawler.
Questions
No. Hetzner provides cloud infrastructure and platform controls, while the customer remains responsible for the operating system, application, monitoring, security updates and recovery process.
No. The server and allocated resources remain billable until the server is deleted, although partial hours are rounded up and each server type has a monthly price cap.
The optional backup feature provides seven rotating daily backup slots. Backups cover the server disk, but attached Volumes are excluded.
No. Processor families, Object Storage, traffic allowances and pricing can differ by network zone or location, and capacity can be temporarily unavailable.
No. Images, backups, snapshots and ISO images remain tied to the original processor architecture.
No verified Hetzner affiliate relationship was identified for this page. Links to Hetzner are direct, untracked official links.
