OVHcloud vs Hetzner

OVHcloud and Hetzner are the usual shortlist when European infrastructure is a requirement rather than a preference. Both offer solid resource pricing, so the choice comes down to configuration detail.

Configurations and prices in the catalogue

Both tables read from the live product records, so they match the product pages exactly.

What actually differs

• Outbound mail. Some OVHcloud configurations in this catalogue are listed with port 25 open, which decides the question for anyone sending mail directly from a server.
• Configuration shape. The OVHcloud listings here are oriented around vCPU counts, while the Hetzner listings are oriented around resource pricing.
• Product surface. OVHcloud carries a wider set of adjacent services; Hetzner keeps a tighter product list.

Where each one tends to fit

OVHcloud suits

• Workloads that need outbound mail from the server itself.
• Teams sizing by vCPU count for a known workload.
• Projects that may need adjacent services from the same provider.

Hetzner suits

• Long-running servers where cost per core and per gigabyte decides it.
• Teams happy to assemble their own supporting services.
• Projects with a clear European user base.

What to check before you buy

• The exact configuration above that covers your workload rather than the cheapest line.
• Whether port 25 access is part of your requirements.
• Which region the configuration is provisioned in and how far that is from your users.
• How you will document ownership and rotate credentials on handover.

More written guidance is in the Networking and Storage topic of the Cloud Library.

Questions