Hetzner Cloud review

Hetzner Cloud is a hosted infrastructure service for provisioning cloud servers. It sits below your application stack: you choose a server size, then run your operating system, application and supporting services on that compute. It is not an application framework or a database, and the homepage positions it alongside Hetzner’s dedicated root servers, managed servers and custom solutions.

The entry point is the CX23, listed at €5.99 per month excluding VAT. It has 2 shared vCPUs, 4 GB RAM, 40 GB NVMe SSD and 20 TB traffic. Larger listed plans move up to 8 shared vCPUs and 16 GB RAM on CX43; CX53 is also listed, but its resource limits are not published. Hetzner describes the service as flexible cloud servers with high-end hardware. That describes the category, not the operational contract: confirm regions, service guarantees, networking and storage behavior against the requirements of your workload.

The vendor does not publish API, SDK, language, CLI or integration details on its homepage. That leaves a key implementation question open: whether your provisioning workflow can call a supported API, use an official SDK in your language, or needs another control-plane workflow. Confirm those details in Hetzner’s technical documentation before choosing it for infrastructure as code or automated deployments.

Architecturally, a cloud server gives your application a compute host; your team still needs to decide how to provision it, configure the operating system and deploy software. If Docker, a particular Linux distribution, or a specific automation tool is a requirement, verify current support and setup instructions in the vendor’s docs rather than assuming compatibility from the cloud-server label. The homepage also does not publish rate limits or API versioning details. For production automation, check those alongside authentication, server lifecycle operations and support escalation paths.

The listed starting price is €5.99 per month excluding VAT for CX23: 2 shared vCPUs, 4 GB RAM, 40 GB NVMe SSD and 20 TB traffic. CX33 costs €8.99/month and includes 4 shared vCPUs, 8 GB RAM, 80 GB NVMe SSD and 20 TB traffic. CX43 is €16.49/month for 8 shared vCPUs, 16 GB RAM, 160 GB NVMe SSD and 20 TB traffic. CX53 is €29.99/month, but confirm its capacity before sizing a workload.

Instances are billed hourly up to a monthly cap; annual billing is not published. There is no free plan or free trial listed. Primary IPv4 costs €0.50/month, and IPv6-only prices are €0.50/month lower. The listed traffic allowance applies to CX23, CX33 and CX43; check the terms for your selected server and ask about charges beyond included traffic before production. The pricing page lists prices excluding VAT, so include applicable taxes in your budget. For a fuller plan comparison, see our separate Hetzner Cloud pricing page.

Hetzner Cloud is a hosted service, not an open-source server you can install in your own environment. The vendor does not publish a software licence for the cloud service on its homepage. If self-hosting or source-code access is a procurement requirement, ask Hetzner directly before adopting it.

Your application may be portable at the operating-system and software layers, but that does not guarantee a one-step migration. Plan how to export databases and files, recreate networking and rebuild deployment automation on another provider. The homepage does not publish data-export tooling or a migration path. Keep backups in a format and location you control, and test recovery independently of the cloud account. The more your deployment relies on provider-specific APIs or services, the more migration work you should budget for; confirm those dependencies during design.

The available plan details establish shared-vCPU capacity, NVMe storage and included traffic for CX23 through CX43, but they are not a production readiness checklist. Verify availability commitments, maintenance behavior, backup and snapshot options, regional availability, security controls and compliance terms with Hetzner before putting critical services on the platform. Confirm what happens when traffic exceeds the plan allowance and how support handles an incident.

Reddit discussions show mixed, anecdotal experience. One post says rising cloud prices made dedicated servers attractive, while another user describes a weekend outage on a Singapore cloud node and a move back to Germany. A separate post refers to snapshots, backups and easy scaling as cloud conveniences. These reports are not service-wide reliability data, but they point to practical checks: choose a region deliberately, maintain independent backups, and define a recovery path that does not depend on one server or support response.