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 & Architecture

Hetzner infrastructure can act as a CDN origin. Its documented cloud locations are in Europe, North America, and Singapore. Those locations are data-centre regions, not a CDN edge footprint. A separate CDN can fetch objects or web responses from Hetzner and cache them closer to users.

Pricing

Hetzner publishes usage and quota information for its infrastructure products. CDN egress, requests, security, and other edge charges come from the third-party CDN and must be priced separately. No CDN rate is listed here because Hetzner does not offer a native CDN product.

Integrations & DevEx

Use a Hetzner service as the origin and configure the chosen CDN to fetch it. For Object Storage, preserve the bucket hostname and TLS requirements, restrict origin access where possible, define cache keys and TTLs, and test purge and range-request behaviour before production use.

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.

When it doesn’t

  • The requirement is a single vendor for origin hosting and a native global CDN.
  • The workload needs CDN-specific controls without integrating a third party.
  • The architecture cannot restrict or monitor traffic between the CDN and the Hetzner origin.