Hourly cloud lifecycle vs recurring VPS bundle
Hetzner vs Contabo: Which Billing Model Fits?
Hetzner Cloud and Contabo VPS can both run a self-managed Linux workload, but they are not the same purchase. Hetzner emphasizes an hourly cloud lifecycle with modular resources. Contabo emphasizes recurring VPS plans with large nominal resource allocations. The better fit depends on how long the server lives, what extras it needs, and how you will migrate or recover it.
Provider documentation checked on October 25, 2026.
Short answer
Choose the operating model, not a synthetic score
Start with Hetzner when
You want hourly provisioning, a monthly cap on server compute, API-driven create and delete workflows, modular public networking, or a choice between shared and dedicated vCPU plans.
Start with Contabo when
You want a long-running recurring VPS and the selected plan's nominal memory, storage, port, snapshot, and traffic allocation fits without frequent resizing or cross-family migration.
There is no universal winner. A fair decision needs the exact region, server family, resource model, public IP, backup policy, traffic behavior, expected lifetime, scale path, and recovery plan.
These are commercial links. VPSchart may receive compensation if you use them, without changing your price. The comparison uses the cited provider documentation, not commission size. Product eligibility and referral terms can vary, so verify them on the destination page.
Hetzner vs Contabo at a glance
| Decision point | Hetzner Cloud | Contabo VPS |
|---|---|---|
| Billing model | Hourly billing with a monthly server-price cap. Billing continues while the server exists, even when powered off. | Recurring VPS plan. Check the live order flow for the available billing period, setup charge, renewal amount, region, and options. |
| Compute model | Shared-resource plans and dedicated-vCPU plans are documented as distinct choices. | VPS resources are virtualized and shared at the hypervisor layer. Contabo also lists separate VDS products. |
| Public networking | Primary IPv4 is optional and separately billed. IPv6 is available without that IPv4 charge. | Verify the address allocation shown for the selected plan and region in the live order flow. |
| Backup and snapshots | Optional backups use seven rolling slots. Snapshots remain until deletion and are billed by compressed size. Attached Volumes are not included. | Snapshot counts and Auto Backup availability depend on the VPS family. Storage VPS has different feature limits. |
| Traffic | Plans include traffic. Additional outbound traffic beyond the allowance is billed according to location. | Plans advertise high or unlimited traffic subject to the provider's fair-use and disruption controls. Check the exact plan and location. |
| Resize path | Plan changes are supported within documented limits. A location cannot be changed in place. | Upgrade within the same family where supported. Downgrade or cross-family moves require a new server and migration. |
| Natural fit | Short-lived or automated cloud servers, modular infrastructure, and workloads that benefit from explicit lifecycle control. | Long-running self-managed servers where the selected recurring bundle closely matches the expected steady-state resources. |
Compare the complete cost basket
A starting price is not a complete bill. Hetzner separates several resources from server compute. Contabo packages plans differently and varies features by family. Price the same workload and recovery standard on both sides.
Hetzner cost basket
- Cloud server family, size, location, and actual lifetime
- Optional Primary IPv4 and any retained addresses
- Backups, snapshots, Volumes, and external recovery copies
- Outbound traffic beyond the included allowance
- Load balancers or other separately selected resources
Contabo cost basket
- VPS family, size, region, billing period, and renewal
- Any setup charge shown in the live order flow
- Snapshot, Auto Backup, storage, or support options
- Migration work when changing family, region, or size
- The operator time needed for security and recovery
Cost-control difference: deleting a Hetzner Cloud server stops its server charge, while simply powering it off does not. A recurring Contabo service stays active through its billing period and renews until cancelled under the account terms. Neither model eliminates charges for separately retained resources.
Server lifetime changes the answer
Hetzner's model is useful when automation creates a server for a job and deletes it afterward. The hourly charge is capped at the monthly server price, but a powered-off server continues to incur charges because the allocation remains reserved. Optional cost alerts are informational and do not stop spending.
Contabo is easier to model as a recurring service for a server that stays online. It is less naturally suited to rapid create-and-destroy cycles because cancellation follows the billing relationship rather than an hourly cloud lifecycle. Confirm the billing period and renewal details shown at checkout before treating any displayed monthly amount as the complete commitment.
Nominal resources do not prove performance
Contabo plans can present large memory, storage, and transfer allocations. Hetzner offers both shared-resource and dedicated-vCPU cloud plans. Those facts describe capacity and resource isolation choices, not application performance.
CPU generation, sustained allocation, noisy-neighbor exposure, storage latency, network path, region, and workload shape can all change a result. VPSchart did not run a controlled Hetzner versus Contabo benchmark for this update, so it does not publish a performance winner or provider score.
A useful first-party test
- Choose the exact candidate plans in the regions your users need.
- Deploy the same image, kernel settings, data, and application version.
- Warm both systems and run the same workload at the same local time.
- Measure application latency, throughput, disk tail latency, error rate, recovery time, and total bill.
- Repeat across several days before making a revenue-sensitive decision.
Backup labels hide important differences
Hetzner Cloud backups are created automatically when enabled and use seven rolling slots. They are bound to the server and are deleted with it. Snapshots are retained until you delete them, but are billed separately. Hetzner also states that attached Volumes are not part of a server backup or snapshot.
Contabo documents snapshots and Auto Backup for selected Core and Performance VPS families. Storage VPS has no snapshots or Auto Backup. Plan-level snapshot counts can differ, so check the current product page for the chosen family rather than assuming a portfolio-wide feature.
Recovery boundary: take an application-consistent backup outside the provider account. For databases, use the database's supported export or replication process. Test a full restore before production depends on it.
Traffic wording needs a workload check
Hetzner documents an included traffic allowance and location-dependent charges for additional outbound traffic. Contabo markets high or unlimited traffic, but its pricing terms allow action when use is exceptionally high or disrupts the network. Neither phrase alone predicts the result for a sustained high-bandwidth workload.
Estimate monthly outbound data, sustained port use, geographic routes, and peak behavior. If traffic is material to revenue, ask the provider to confirm the applicable policy for the exact plan and region before purchase.
Scaling and migration boundaries
Hetzner does not move an existing cloud server to another location in place. Its documentation points to creating a new server from a snapshot or backup. Contabo documents region migration options, but both IPv4 and IPv6 addresses change. A Contabo downgrade also requires a new server and manual migration.
Within Contabo, upgrading inside the same VPS family can retain the service and IP where supported. Moving between families is a different operation, and some SSD-to-NVMe paths require reinstalling or moving data. Treat every family or region change as a migration until the provider confirms otherwise for the exact service.
- Record the source. Save the operating system, disk layout, IP dependencies, firewall rules, scheduled jobs, secrets, DNS, and current bill.
- Create an independent backup. Keep it outside the source provider and verify that it can be read.
- Build the target. Recreate the application, network controls, monitoring, mail settings, and backups.
- Test before cutover. Validate data integrity, TLS, authentication, performance, alerts, and a restore.
- Switch with rollback. Lower DNS TTL in advance, perform the final sync, and keep the old service until production checks pass.
- Remove resources deliberately. Cancel or delete the old service and separately retained resources only after the rollback window closes.
Make the decision in seven questions
- Is the server short-lived, automated, or permanently online?
- Do you need shared compute, dedicated vCPU, or a separate VDS product?
- Which public IP, backup, snapshot, storage, and traffic costs apply?
- Will the selected region and family remain suitable for the next year?
- Can the workload tolerate a new IP or manual migration when it changes?
- What first-party test will validate application performance and recovery?
- What is the complete cost through renewal, including operator time?
Choose Hetzner when an hourly cloud lifecycle and modular infrastructure remove operational friction. Choose Contabo when a recurring VPS bundle matches a stable workload without relying on a future downgrade or cross-family move. Verify the live configuration and terms immediately before purchase.
Frequently Asked Questions
Is Hetzner or Contabo cheaper?
There is no reliable provider-wide answer. Compare the exact server family, region, CPU model, memory, storage, public IPv4, backup, traffic policy, billing period, and expected lifetime. Hetzner bills cloud servers hourly with a monthly cap, while Contabo presents recurring VPS plans. A low headline price can describe a different cost basket.
Does a powered-off Hetzner Cloud server still cost money?
Yes. Hetzner says server resources remain reserved while the server exists, so charges continue when it is powered off. Delete the server to stop server charges, but first account for separately billed Primary IPv4 addresses, snapshots, backups, and Volumes that you retain.
Do Hetzner and Contabo include backups?
Do not assume the same backup model. Hetzner Cloud backups are an optional service with seven server-bound slots, and snapshots are billed separately by stored data. Contabo documents snapshot availability and an Auto Backup add-on for selected VPS families, while Storage VPS has different limits. Neither replaces an independent off-provider backup and a tested restore procedure.
Can I resize or downgrade a Contabo VPS?
Contabo documents in-place upgrades within the same VPS family. A downgrade requires a new smaller server, manual data migration, and cancellation of the old server. Direct conversion between plan families is not generally available, and some storage moves or reinstalls can erase data.
Should I choose Hetzner or Contabo for self-hosting?
Choose Hetzner when hourly lifecycle control, API-driven provisioning, modular networking, and a choice between shared and dedicated vCPU plans matter. Choose Contabo when a recurring VPS bundle with larger nominal resource allocations fits a long-running workload. Test the actual application because nominal resources alone do not establish performance.
Official sources
Checked October 25, 2026. Plans, prices, limits, availability, and provider terms can change after this date.
- Hetzner Cloud billing FAQ: hourly billing, monthly cap, powered-off servers, traffic, backups, snapshots, IPv4, and cost alerts.
- Hetzner Cloud server overview: shared-resource and dedicated-vCPU plans plus Primary IP boundaries.
- Hetzner Cloud server FAQ: location changes, public networking, resource models, and port restrictions.
- Hetzner backup and snapshot FAQ: retention, server binding, Volume exclusions, and consistency guidance.
- Contabo VPS documentation: plan families, shared virtualization, snapshots, Auto Backup, upgrade, downgrade, region migration, and family-conversion boundaries.
- Contabo pricing: current plan families, resource allocations, traffic wording, and current displayed prices.
- Contabo Performance VPS: family-level snapshot, Auto Backup, and traffic features.
- Contabo add or remove service guide: service activity through the billing period.
- Contabo renewal guide: automatic renewal and cancellation boundary.
- Contabo cancellation guide: cancellation process and backup or snapshot deletion risk.