hetzner calculator

Why a Hetzner Calculator Matters

Hetzner is popular for one simple reason: excellent performance-per-euro. But low base prices can still lead to messy invoices if you scale quickly, forget to account for backups, or underestimate traffic overages. A good calculator helps you plan before deployment, not after the surprise bill.

This calculator is designed for practical budgeting. Instead of giving you a single vague number, it breaks costs down by compute, storage, bandwidth, networking, and tax. That makes it easier to answer questions like:

• How much will my staging and production environments cost together?
• At what point does overage traffic change my architecture decision?
• How much should I budget for backups and additional IPv4 addresses?

How This Hetzner Calculator Works

1) Compute cost (hourly with monthly cap)

Hetzner cloud servers are generally billed hourly, with a monthly maximum. That means your per-instance compute cost is calculated as: minimum(hourly rate × hours, monthly cap). If your workload runs all month, the cap usually applies.

2) Volume storage

If you attach block volumes, they are billed by GB per month. In this calculator, storage is estimated at €0.044 per GB/month. This is useful for databases, persistent app data, and file uploads.

3) Backup estimate

Backups are often forgotten in early cost planning. To keep planning simple, this tool applies a percentage of compute spend (default 20%) as an estimated backup cost. You can set this to zero or tune it for your own policy.

4) Network extras and traffic overage

Additional IPv4 addresses and excess outbound traffic can become meaningful at scale. You can configure:

• How many extra IPv4 addresses you need
• Your monthly outbound traffic
• Included traffic allowance per server

Overage is billed only when outbound traffic exceeds included allowance across all servers.

Sample Use Cases

Lean side project

• 1× CX22
• 730 hours/month
• No extra IPv4, no storage volume
• Low traffic

This setup is ideal for personal apps, portfolio APIs, or lightweight SaaS MVPs. You can keep costs very low while still getting dependable uptime.

Growing SaaS stack

• 3× CX32 app nodes
• 1× database node with attached volume
• Backups enabled
• Moderate outbound traffic

In this stage, your budget starts shifting from pure compute into storage resilience and data transfer. The calculator helps you spot when it is time to optimize architecture rather than just adding more instances.

Production workload with strict reliability

• Dedicated vCPU plans (CCX family)
• Higher backup allocation
• Multiple extra IPs
• Traffic planning with headroom

For critical workloads, reliability and predictable performance usually matter more than minimizing every cent. A detailed monthly estimate helps finance and engineering stay aligned on what “production-ready” actually costs.

Cost Optimization Tips

• Right-size first: avoid overprovisioning CPUs and RAM “just in case.” Monitor for one month and adjust.
• Use autoscaling patterns: horizontal scaling during peaks can be cheaper than oversized always-on instances.
• Track traffic direction: outbound traffic often matters more than inbound in cloud billing models.
• Audit old volumes: unattached or oversized volumes can quietly raise monthly spend.
• Make backup strategy explicit: define retention and frequency, then price it on purpose.

Common Budgeting Mistakes

• Calculating only base server cost and ignoring storage growth.
• Assuming test environments are “small” but leaving them running 24/7.
• Ignoring tax/VAT effects in client proposals.
• Skipping exchange-rate risk when invoicing in USD but paying in EUR.
• Not reevaluating costs after architecture changes.

FAQ

Is this an official Hetzner calculator?

No. This is an independent planning tool for budgeting and rough forecasting.

Can I use this for dedicated servers too?

The calculator is primarily tuned for cloud-style monthly estimation. You can still use it conceptually for dedicated setups, but fixed server pricing and options should be entered manually where needed.

How accurate is the estimate?

It is intended for decision support, not accounting. Final invoices may differ due to region-specific pricing, promotions, exact traffic definitions, and any provider-side updates.