Hetzner Cloud pricing: hourly rate beside monthly cap
Scope: shared AMD Regular Performance only, EUR, the website's 0% VAT selection. Each row preserves the location behind the displayed minimum. The US generation has different CPU and disk allocations; it is not a regional replacement price for the European SKU.
| SKU | Quote location | vCPU | RAM GB | NVMe GB | EUR/month cap, IPv4 included | EUR/hour displayed |
|---|---|---|---|---|---|---|
| CPX02 | HEL1 | 1 | 1 | 20 | €5.49 | €0.0088 |
| CPX12 | HEL1 | 1 | 2 | 40 | €9.99 | €0.0160 |
| CPX22 | HEL1 | 2 | 4 | 80 | €16.99 | €0.0272 |
| CPX32 | HEL1 | 4 | 8 | 160 | €30.49 | €0.0489 |
| CPX42 | HEL1 | 8 | 16 | 320 | €59.49 | €0.0953 |
| CPX52 | HEL1 | 12 | 24 | 480 | €85.49 | €0.1370 |
| CPX62 | HEL1 | 16 | 32 | 640 | €110.99 | €0.1779 |
| CPX11 | ASH1 / HIL1 | 2 | 2 | 40 | €17.99 | €0.0288 |
| CPX21 | ASH1 / HIL1 | 3 | 4 | 80 | €32.49 | €0.0521 |
| CPX31 | ASH1 / HIL1 | 4 | 8 | 160 | €62.99 | €0.1009 |
| CPX41 | ASH1 / HIL1 | 8 | 16 | 240 | €120.99 | €0.1939 |
| CPX51 | ASH1 / HIL1 | 16 | 32 | 360 | €238.49 | €0.3822 |
Data from Hetzner official Regular Performance page → CPX rows: CPU, RAM, drive, from/month and /hour cells. Checked 2026-11-13 04:29 UTC. Footer on the matrix: “Price incl. IPv4”; VAT excluded. These are card observations, not a converted currency or a monthly price divided by assumed hours.
Same SKU, different location and traffic allowance
| SKU | Network zone | Location labels on card | Monthly quote incl. IPv4 | Included traffic | Difference from HEL1 |
|---|---|---|---|---|---|
| CPX02 | eu-central | HEL1 | €5.49 | 20 TB | €0.00 = €5.49 − €5.49 |
| CPX02 | eu-central | FSN1 / NBG1 | €6.49 | 20 TB | €1.00 = €6.49 − €5.49 |
| CPX02 | ap-southeast | SIN1 | €7.99 | 0.5 TB | €2.50 = €7.99 − €5.49 |
| CPX11 (different SKU) | us-east | ASH1 | €17.99 | 1 TB | Not a same-SKU comparison |
| CPX11 (different SKU) | us-west | HIL1 | €17.99 | 1 TB | Not a same-SKU comparison |
Data from Hetzner official Regular Performance page → expanded CPX02 and CPX11 location rows. Checked 2026-11-13 04:29 UTC. Difference cells are our subtraction of the linked monthly inputs. Labels above reproduce the public card's uppercase labels; the Console may use lower-case identifiers. Availability for a new order: Not obtained; a successful location-specific order check is needed. The official Locations → Which cloud products are available? warns that instances can be unavailable.
The allowance changes with the selected plan and location; it is not a global allowance quoted identically everywhere. A cross-server or cross-zone shared allowance pool was Not obtained; explicit pooling documentation is needed before offsetting one server's usage with another server's unused allowance. The Billing FAQ → How do you bill for traffic? distinguishes outgoing traffic from free incoming/internal traffic and counts public traffic between different network zones as outgoing.
Three location-sensitive checks before ordering
Our assumption: one CPX02 exists through twelve complete capped months, unchanged rates, no tax or optional services. Helsinki: 12 × €5.49 = €65.88. German location: 12 × €6.49 = €77.88. Singapore: 12 × €7.99 = €95.88. Location alone changes this model by €12.00 or €30.00 per year relative to Helsinki. This compares the same SKU, not the US CPX11.
Our assumption: a full-month server sends 0.6 TB of chargeable outgoing traffic. Using the CPX02 location allowances, Helsinki's excess = max(0, 0.6 − 20) = 0 TB; Singapore's excess = max(0, 0.6 − 0.5) = 0.1 TB. The current region-specific overage rate is Not obtained; a current official EUR/TB quote for each zone is needed to turn that excess into money. Do not copy a dedicated-server rate into a Cloud calculation.
The Traffic → Exceeding traffic section specifies 100 MB = 0.0001 TB billing blocks. With the Billing FAQ's upward-rounding rule, the formula is ceil(max(0, outgoing TB − allowance TB) / 0.0001) × 0.0001 × regional EUR/TB. In our Singapore scenario: ceil(0.1 / 0.0001) = 1,000 blocks. The missing rate remains a missing input, not zero.
IPv4, backups and retained resources
| Resource | Official rate / basis | Evidence location |
|---|---|---|
| Primary IPv4 | €0.50/month; separately billed | IP pricing → Cloud |
| Primary IPv6 | Free | IP pricing → Cloud |
| Floating IPv4 | €3.00/month | IP pricing → Cloud |
| Floating IPv6 | €1.00/month | IP pricing → Cloud |
| Server backups | 20% of server price; 7 slots | Billing FAQ → Snapshots and Backups |
| Snapshot stored data | €0.0143/GB-month | Regular Performance → Snapshots add-on |
| Volume storage | Not obtained: conflicting unit text and calculator; consistent quote needed | Block Storage → Volumes |
Data from Hetzner official pages: IP pricing → Cloud table, Billing FAQ → How do you bill for Snapshots and Backups?, Regular Performance → Snapshots and Block Storage → Volumes unit text and calculator. Checked 2026-11-13 04:29 UTC. The IPv4 fee is already included in the plan cards above; do not add it again. Primary IPv4 and Floating IPv4 are different resources.
Backup formula: B = P × 20%, where P is the chargeable server-price basis confirmed for the chosen order. Our assumption: P = €10.00, purely to illustrate the rule, not a published plan quote. B = €10.00 × 0.20 = €2.00/month. The percentage comes from Billing FAQ → Snapshots and Backups, second paragraph. The public page's backup starting widget does not resolve the separately billed IPv4 basis, so the exact CPX02 backup invoice amount is Not obtained; a selected-order backup quote is needed.
Our assumption: retain 20 GB of compressed snapshot data for a complete month, plus one unassigned Primary IPv4 and one Floating IPv4. Snapshot = 20 × €0.0143 = €0.286; IPs = €0.50 + €3.00 = €3.50; subtotal = €3.786 before invoice rounding and tax. Deleting the VM alone does not mean these retained resources disappear. Check their deletion separately. The Billing FAQ → Primary IPs expressly bills unassigned IPs; its snapshot section charges compressed stored size. Retaining an allocated volume adds an unquoted charge, and Volumes → Resources and attributes excludes attached volumes from server backups and snapshots.
Short runs and year-one versus year-two budgets
For the server resource, C = min(monthly cap, hourly rate × ceil(existence hours)). The Billing FAQ → How do you bill your servers? supplies the minimum and rounding rules. A lower bill requires fewer billable existence hours; stopping the OS does not shorten existence. A location-specific compute-only hourly and cap quote was Not obtained separately from the IPv4-inclusive public card, so we do not present the latter as a server-only invoice.
Our assumption: a server-only quote has an hourly rate h and cap M. A job retained for 24 hours and one minute has ceil(24 + 1/60) = 25 billed hours, so C = min(M, 25h). It stays below the cap exactly when 25h < M. The duration is our scenario; h and M must come from the same selected configuration. The symbols deliberately avoid inventing a missing quote.
No first-year discount is shown in the checked CPX cards. This describes the observed offer, not a promise about every account or future campaign. Our assumption of twelve full capped months at the unchanged Helsinki IPv4-inclusive card rate gives year one = 12 × €5.49 = €65.88; year two under the same assumption = €65.88; difference = €0.00. A guaranteed future renewal tariff is Not obtained; future official pricing is needed. Do not treat our unchanged-rate scenario as a renewal quote.
Who should use this Hetzner VPS pricing guide?
Use the CPX location table when a shared AMD instance fits your workload and you can choose where it runs. Check other families separately for dedicated CPU or ARM requirements. If you need an exact tax-inclusive checkout total, an assured in-stock order, a current overage invoice or volume budget, the missing inputs below must be resolved before ordering.
What was not obtained
- Live order availability: requires a successful selected-location stock check.
- Regional traffic overage unit prices and allowance-pooling rules: require current explicit Cloud billing terms for the selected zone.
- Consistent volume unit price: requires reconciliation of the official unit text and calculator. No volume amount is included in our totals.
- Exact CPX02 backup billing basis and compute-only hourly/cap quote: require the selected-order breakdown.
- Future renewal tariff and account-specific tax/credit total: require future rates and the account checkout.
Every item in this list is Not obtained, rather than N/A or an assumed zero. No third-party number fills these gaps.
Official sources and check date
Official public prices and documentation checked 2026-11-13 04:29 UTC. This is a dated editorial observation, not an automatically refreshed feed. Source sections are linked at each table and calculation. Arithmetic results are our calculations; hypothetical inputs are labelled our assumption.