Cost calculator

Your traffic

Choose a workload. We’ll estimate traffic and requests for you.

Estimated monthly costs

USD per month, before tax. Load balancing and unpriced extras are excluded.

What’s included?

Estimates cover cacheable content. Origin and optional services are added only when you enter their rates. Plans differ in features and coverage; check their terms before buying.

Advanced settings
Split traffic between regions

Percentages must total 100%. The same split applies to bytes and requests. CloudFront charges by serving edge location; this is an approximation. Shared free allowances are allocated proportionally.

Origin and optional services

Paid tiers start with this workload; estimates do not include other account traffic. Enter your own effective rates after origin allowances. Reads use request misses; egress uses byte fill. Functions assume one invocation per viewer request. Zero leaves an extra out of the estimate; it does not mean your origin is free.

Compare a quote you received

This is your quote, not a published provider price. Use an effective rate for the selected traffic mix; tiers, included usage and commitments need to be reflected in your inputs. Sharing a scenario includes your quote details.

Presets are starting assumptions, not measured traffic. Video assumes one rendition and segment GETs; playlists, retries and extra audio tracks add requests. Fill is a byte ratio, not a request cache-hit rate. GB = 1 billion bytes; Google bills GiB = 1,073,741,824 bytes; CloudFront estimates use binary GB as a billing assumption.

Overview

Hetzner provides cloud servers, dedicated servers, DNS, load balancers, and object storage. It does not advertise a native content delivery network. Hetzner’s Object Storage FAQ recommends placing a third-party CDN in front of a bucket when globally distributed caching is required.

Network

Cloud origin regions

Hetzner Cloud lists Falkenstein and Nuremberg in Germany, Helsinki in Finland, Ashburn in Virginia, Hillsboro in Oregon, and Singapore. Product availability and traffic prices vary by network zone.

Object Storage

Buckets are available in Falkenstein, Nuremberg and Helsinki. A bucket stays in its selected location; cross-location replication requires a separate setup. These are origin regions, not CDN cache locations.

Cloud origin regions

Approximate city centers for matched cloud origin regions. Object Storage is available only in Falkenstein, Nuremberg and Helsinki. These are not CDN cache PoPs.

NurembergHelsinkiSingapore
Cities

Nuremberg, Helsinki, Singapore

Listed without a marker: Falkenstein, Germany, Ashburn, Virginia, United States, Hillsboro, Oregon, United States.

Features

Origin services

  • Cloud and dedicated servers, DNS and load balancers can host applications behind a CDN.
  • Object Storage uses an S3-compatible API and supports public object URLs, versioning, presigned URLs and optional server-side encryption.
  • The storage API supports TLS 1.3; this is an origin capability.

Delivery controls

Choose a separate CDN for distributed caching, cache purge, viewer security and image processing. Object Storage is designed for storage and retrieval rather than direct high-volume delivery to end users.

Pricing

Object Storage origin bill

  • The account base is EUR 0.0104 per active hour, capped at EUR 6.49 per month, excluding VAT. It applies across buckets, projects and locations.
  • Included storage and outgoing-traffic quotas accrue hourly; unused quota expires monthly. A continuously active account accrues 1 TB of storage capacity and just over 1 TB of monthly traffic, depending on month length.
  • Extra storage costs EUR 0.0087 per TB-hour; extra outgoing traffic costs EUR 1 per TB. Objects smaller than 64 kB are billed as 64 kB.
  • S3 operations, ingress and internal eu-central traffic are free. Free GET operations do not make their outgoing traffic free.

Add delivery costs

The CDN has its own delivery and optional-service bill. The calculator accepts USD rates only. Use your account’s USD tariff or convert EUR to USD before entering effective per-GB origin egress. Add storage and account charges under other monthly services. These storage rates are not a native CDN tariff.

Developer tools

Connect an origin

Use the bucket hostname as the CDN origin, preserve the required Host header and TLS settings, and test cache policy, range requests and purge behavior. Limit origin access where the chosen setup permits it.

Manage storage

Use S3-compatible tools such as AWS CLI, SDKs or rclone. Hetzner Console creates credentials; bucket and object operations use the S3 API. Monitor cache misses against the documented 750 requests per second limits per bucket and source IP.

When it fits

  • A project already uses Hetzner compute or Object Storage as its origin.
  • The team is prepared to select, configure, and pay for a separate CDN.
  • Origin location coverage is sufficient for cache misses and uncacheable traffic.

Before you choose

  • A project requires one vendor to supply origin hosting and a native global CDN.
  • A storage workload needs thousands of small-object operations per second or consistently very low origin latency.
  • The architecture cannot separately budget or monitor CDN-to-origin traffic.

History

Hetzner began in 1997 and is based in Gunzenhausen, Germany. Hetzner Online GmbH provides hosting, cloud and storage infrastructure.

Its data center parks are in Nuremberg, Falkenstein and the Helsinki area; United States and Singapore cloud regions use colocation space.

Sources