Prepaid VPS package vs hourly cloud resources
Hostinger vs Hetzner: Which Operating Model Fits?
Hostinger and Hetzner can both run a typical Linux workload, but they package the purchase differently. Hostinger favors a prepaid VPS term with a bundled resource allowance. Hetzner Cloud favors hourly infrastructure where networking, backups, and server lifetime must be priced together.
Provider documentation checked on October 24, 2026.
Short answer
Choose the billing and operations model first
Start with Hostinger when
You expect to keep one VPS for the selected prepaid term and want the advertised plan to bundle its listed CPU, RAM, NVMe storage, bandwidth, public addressing, and backup policy. Confirm the renewal amount before comparing the monthly equivalent.
Start with Hetzner when
You want to create and delete cloud servers by the hour, choose shared or dedicated resources, and configure public networking and backups separately. This model is useful for temporary environments and infrastructure that changes often.
There is no universal winner. A low displayed compute price is incomplete until the term, server lifetime, region, public IPv4, backup retention, storage, traffic, taxes, and recovery plan are included.
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.
Hostinger vs Hetzner at a glance
| Decision point | Hostinger VPS | Hetzner Cloud |
|---|---|---|
| Purchase model | Prepaid for the selected term. The displayed monthly amount is the term total divided by its length. | Hourly billing up to the documented monthly cap for applicable servers. |
| Entry resource example | KVM 1 currently lists 1 vCPU, 4 GB RAM, 50 GB NVMe storage, and 4 TB bandwidth. | Choose among shared and dedicated resource families. Exact configurations and availability vary. |
| CPU contract | Hostinger documents CPU credits. The VPS can use its allocated vCPU capacity while credits remain, then capacity is reduced after depletion. | Shared plans share processor resources. Dedicated plans reserve the assigned vCPU resources. |
| Public network | KVM plans list one IPv4 and one IPv6 address. | IPv6 is available without an extra charge. Public IPv4 is a separately billed option. Private-only configurations are possible. |
| Automatic backup | Weekly by default, with an optional daily frequency. Hostinger also documents one manual snapshot with a one-day expiry. | Optional add-on at 20 percent of server price, with seven rotating daily slots. Attached Volumes are excluded. |
| Operational shape | One self-managed VPS package for a selected prepaid period. | Composable cloud resources that remain billed until deleted. |
| Natural fit | A stable, long-running server where the prepaid term and renewal are acceptable. | Temporary environments, automation, or infrastructure that benefits from hourly creation and deletion. |
Compare the complete cost basket
Do not compare a Hostinger promotional monthly equivalent with a bare Hetzner server price. They describe different purchase contracts. Build one basket for the period you actually expect to run the service.
Hostinger cost basket
- Total prepaid amount for the selected initial term
- Renewal amount for the following term
- Required daily backup option or other add-ons
- Taxes and any resource upgrade needed during the term
- Unused prepaid time if the project ends early
Hetzner cost basket
- Selected server and region for its actual lifetime
- Public IPv4 if required by the application
- Optional Cloud backups and separately billed storage
- Traffic or other resource charges outside the included allowance
- Resources left allocated after a server is powered off
Deletion is the Hetzner billing boundary. Hetzner states that a server continues to incur charges while it exists, even when it is powered off. Export required data and confirm the rollback plan before deleting it.
The CPU labels do not mean the same thing
Hostinger publishes a CPU credit model for its VPS plans. A server can use its allocated vCPU capacity while credits remain, but Hostinger reduces available CPU capacity when those credits are depleted. This matters for sustained compilation, encoding, busy application workers, and other long-running processor loads.
Hetzner separates shared and dedicated resource families. Shared resources are the economical choice for bursty services that can tolerate contention. Dedicated resources are the clearer contract for sustained or latency-sensitive work. The label alone does not prove real application performance.
Evidence boundary: VPSchart did not run a controlled Hostinger versus Hetzner benchmark for this update. Test the actual application in the required region if performance affects revenue, latency, or job completion time.
Backup retention and scope differ
Hostinger documents a weekly VPS backup by default and an optional daily frequency. Its current help material describes up to four retained backup copies when daily backups are enabled. It also supports one manual snapshot, which expires after one day.
Hetzner Cloud backups are optional and cost 20 percent of the server price. The service uses seven rotating daily backup slots and binds the backups to the server. Attached Volumes are not included.
Neither arrangement replaces an independent recovery copy. Use application-aware database exports where required, store at least one copy outside the provider account, and test a restore before relying on the schedule.
Which provider fits your workload?
Stable website or self-hosted application
Hostinger can be the simpler commercial choice when the server will stay online for the full prepaid term and the included resource bundle fits. Compare the complete initial payment and renewal, not only the displayed monthly equivalent.
Temporary development or test environment
Hetzner's hourly model can fit an environment that is created for a task and deleted afterward. Merely powering the server off does not stop charges, so deletion needs to be part of the automation and operating checklist.
Sustained CPU work
Do not infer sustained performance from vCPU count alone. Hostinger's CPU credit policy and Hetzner's shared or dedicated distinction create different limits. Run the real workload and record completion time, error rate, throttling, and total cost.
Private service or IPv6-first workload
Hetzner lets you choose private-only networking, IPv6, IPv4, or both, subject to the current server and network rules. That can avoid an unnecessary public IPv4 charge, but only if every dependency can reach the chosen address setup.
Migration checklist between Hostinger and Hetzner
- Inventory the service. Record ports, DNS, certificates, databases, scheduled jobs, persistent storage, mail delivery, firewall rules, and external allow lists.
- Choose the target contract. Confirm region, CPU model, memory, disk, address family, backup retention, billing term, and expected lifetime.
- Create an independent backup. Export databases with an application-aware method and keep a copy outside both provider accounts.
- Build and test the target. Restore data, validate the application, TLS, background jobs, monitoring, mail, and the recovery procedure before changing traffic.
- Cut over with rollback. Lower DNS TTL in advance, perform a final sync, change traffic, and keep the old server until production checks pass.
- Remove old resources deliberately. Delete servers and separately billed resources only after the rollback window and billing review are complete.
Make the decision in five questions
- Will the server remain online for a full prepaid term, or must it be billed by the hour?
- Does the workload tolerate shared or credit-based CPU behavior, or does it need dedicated resources?
- Is public IPv4 required, or can the service use IPv6 or private networking?
- What backup retention, database consistency, and off-provider recovery copy are required?
- What is the total cost through renewal, including addresses, backups, storage, traffic, and unused time?
Choose Hostinger when a stable prepaid VPS bundle fits the full operating period. Choose Hetzner when hourly infrastructure and separately configurable resources fit the deployment. In both cases, test the workload and recovery path before moving production.
Frequently Asked Questions
Is Hostinger or Hetzner cheaper?
There is no provider-wide answer. Hostinger sells prepaid VPS terms and shows a monthly equivalent based on the selected term. Hetzner Cloud charges by the hour up to a monthly cap for many server types, then adds separately billed items such as public IPv4 and optional backups. Compare the complete basket for the exact term, region, IP setup, backup policy, and expected lifetime.
Does Hostinger or Hetzner offer hourly billing?
Hetzner Cloud documents hourly billing up to a monthly cap for applicable servers. Billing continues while the server exists, even when it is powered off. Hostinger VPS plans are paid in advance for the chosen term, so the displayed monthly figure is not an hourly rate.
Are Hostinger VPS and Hetzner Cloud managed services?
Treat both as self-managed infrastructure for this comparison. You are responsible for the operating system, security updates, application deployment, monitoring, and recovery unless you buy a separate management service. Hostinger support explicitly describes its VPS product as self-managed.
How do Hostinger and Hetzner backups differ?
Hostinger documents a weekly VPS backup by default, with an optional daily frequency, plus one manual snapshot that expires after one day. Hetzner Cloud backups are an optional add-on priced at 20 percent of the server price and use seven rotating daily slots. Hetzner backups do not include attached Volumes. Keep an independent backup and test restores with either provider.
Can I migrate between Hostinger and Hetzner?
Yes, but do not assume provider snapshots are portable. Create the target server, export databases with an application-aware method, copy persistent files, test services and backups, switch DNS, and keep a rollback window before deleting the old server.
Official sources
Checked October 24, 2026. Plans, prices, limits, and provider terms can change after this date.
- Hostinger VPS plans: current term presentation and listed KVM plan resources.
- Hostinger VPS parameters and limits: CPU credits and plan limits.
- Hostinger managed hosting guide: self-managed VPS boundary.
- Hostinger VPS backup and restore guide: schedules, retained copies, snapshots, and restore workflow.
- Hetzner Cloud server overview: shared and dedicated resources and public network choices.
- Hetzner Cloud billing FAQ: hourly billing, monthly caps, powered-off servers, and deletion.
- Hetzner backups and snapshots FAQ: pricing, retention slots, server binding, and Volume exclusions.
- Hetzner Cloud servers FAQ: IPv4 and IPv6 configuration and charges.