Skip to content

Independent marketplace for verified cloud accounts

Hetzner vs OVH

Two large European providers that own their data centres but sell very different things. This compares product breadth, bare metal ranges and how each one treats data sovereignty.

Buy Hetzner Account
Germany, EU hardware value

Hetzner

Regions noted in source
Germany, Finland, United States, Singapore
Configurations listed
3
From$50 View account
Buy OVH Account
EU sovereignty, bare metal

OVHcloud

Regions noted in source
Europe and global
Configurations listed
2
From$30 View account

Hetzner and OVHcloud are the two names that come up whenever a European team decides it would rather not run on an American cloud. Both own and operate their own facilities. Both build a significant part of their own hardware. Both are large enough to be a credible long-term supplier rather than a reseller with a logo.

They are not interchangeable. OVHcloud is a broad infrastructure provider with a catalogue that reaches from shared web hosting up to private cloud and sovereign offerings for regulated buyers. Hetzner is a focused hosting company that sells servers extremely well and declines to sell much else. Choosing between them is mostly a question of how wide a supplier relationship you want.

Catalogue width and what that means in practice

OVHcloud’s product list is long. Public cloud instances, managed Kubernetes, object and block storage, managed databases, bare metal in several distinct ranges, hosted private cloud built on VMware, domains, email, web hosting, and dedicated offerings aimed at regulated sectors. For an organisation that wants one European vendor on the purchase order, that breadth is the point.

Hetzner’s list fits on one screen. Cloud instances, dedicated servers, storage boxes, load balancers, private networks, a few supporting pieces. There is no managed Kubernetes service, no managed relational database in the usual sense, and no private cloud product.

Width cuts both ways. A broad catalogue means fewer vendors and more things you can adopt without a new procurement cycle. It also means a larger console, more concepts, more documentation to read and more ways to configure something incorrectly. Narrow catalogues are easier to reason about, and for teams that already run everything through an infrastructure as code provider model, the missing managed services matter less than they look like they should.

Bare metal, where both companies are strongest

This is the part of the comparison that rewards attention, because both providers are serious about physical servers in a way most clouds are not.

OVHcloud segments its bare metal into distinct ranges with different intentions: entry-level machines for general hosting, performance-oriented lines for production workloads, and higher-end ranges aimed at storage-heavy, virtualisation and demanding enterprise use. The ranges differ in network specification, redundancy and the kind of support wrapped around them, not just in CPU model. If you need a specific hardware profile, the catalogue usually has a line designed for it.

Hetzner approaches the same market from the other side. Its dedicated server business includes a server auction, where previously provisioned machines are offered as they free up. That is an unusual and genuinely useful mechanism: if you are flexible about exact configuration, you can get substantial hardware for noticeably less than a new build. The trade is availability. What is in the auction today is not guaranteed to be there next month, which makes it excellent for capacity you can plan around and awkward for a fleet you need to scale on demand.

Both are far better value than renting equivalent capacity as virtual machines from a hyperscaler, and both carry the same operational obligation. A physical server is yours to run. Bare metal versus virtualized compute goes through what changes in your operations when you stop being able to rebuild a host in ninety seconds.

How each handles sovereignty

Sovereignty has become a procurement word rather than a technical one, and the two companies answer it differently.

OVHcloud has built an explicit position around it. The company is French, it is vocal about European digital independence, and it offers tiers of isolation for customers whose requirements go beyond data residency into questions of operator access and legal jurisdiction. If your buyer is a public body, a hospital group or a regulated financial firm, OVHcloud has usually already had the conversation your legal team is about to start.

Hetzner’s answer is simpler and quieter: it is a German company, operating German and Finnish facilities, selling under German contract law. That is a strong sovereignty position in substance, and it comes with much less paperwork around it. For most commercial customers it is entirely sufficient. For a formal procurement process that wants documented assurances about who can touch what, Hetzner gives you less to hand to the compliance reviewer.

The distinction matters because residency and sovereignty are not the same thing. A region in Frankfurt operated by a United States company is residency. A European company operating European facilities under European law is a different legal exposure, and European cloud providers and data sovereignty sets out where the line actually falls.

Network posture

OVHcloud operates its own global backbone and has long included DDoS mitigation as standard across its products rather than as a paid add-on. For anyone hosting a target, a game service, a forum, a public API, a political or media site, that is a meaningful line item that does not appear on the invoice.

Hetzner also provides attack mitigation and runs a well-connected European network, with strong peering into the regions it serves. Within Europe the practical difference for normal traffic is small. Outside Europe, OVHcloud’s larger international presence gives it more reach, including locations in North America and Asia Pacific.

Console, API and day-to-day friction

Here Hetzner is the more pleasant product and it is not particularly close. The cloud console is fast, uncluttered and does what you expect. The API is clean. People who use it tend to stop thinking about it, which is the highest compliment an interface gets.

OVHcloud’s control panel carries the weight of its catalogue. There is more to navigate, the terminology varies between product lines because they grew separately, and account structure takes longer to understand. It is workable and it has improved, but expect a learning curve rather than an afternoon.

The managed services gap

If your plan involves someone else running your database, your Kubernetes control plane or your object store, OVHcloud has products for that and Hetzner does not. This is the single largest functional difference between the two and it decides a lot of shortlists on its own.

The temptation is to score it as a straight win for OVHcloud. Resist that for a moment. A managed service is worth paying for when it removes work you would otherwise do badly or inconsistently. It is worth less when your team already runs that component well, has it described in code, and has tested its restore path. Plenty of competent operators look at a managed Postgres offering and correctly decide that their existing automation is better suited to their workload than a generic service would be.

The question to ask is not which provider has more services, it is which services you would actually enable in the first ninety days. If the answer is none, catalogue width is a cost you are paying in console complexity for no return. If the answer is three, Hetzner means three more systems your team owns forever, and that arithmetic usually favours OVHcloud.

Which one fits your situation

Requirement Better fit Why
Cheapest competent European compute Hetzner Lower cost per core and per gigabyte of RAM
One European vendor across many product types OVHcloud Broad catalogue under a single contract
Formal sovereignty requirements in procurement OVHcloud Dedicated offerings and documented positioning
Opportunistic bare metal at low cost Hetzner Server auction for flexible configurations
Specific bare metal hardware profile OVHcloud Distinct ranges built for different workloads
Simple console and clean API Hetzner Narrow product set, less to navigate

Accounts, credits and getting moving

Both providers verify new customers, and OVHcloud’s process in particular reflects a company that sells to businesses as well as developers. Billing country, payment method and intended use all affect what a new account is allowed to do immediately.

If you need working capacity without waiting on that, the listings for Buy Hetzner Account and Buy OVH Account describe what each one includes. TrustCloudHub is an independent marketplace and has no affiliation with either company. Any credit attached to an account remains under the provider’s control: it expires, it is restricted to certain services, and you should confirm the balance inside the provider’s own console after transfer instead of trusting a description. Whatever you buy, run the post-handover security checklist before you put real workloads on it.

If you want the same European question framed against a cheaper German competitor, Hetzner vs Contabo covers what the discount tier actually costs you.

Other comparisons to consider

Hetzner vs Vultr
vs

Hetzner vs Vultr

This comparison comes down to one trade: Vultr puts compute in many more places around the world, while Hetzner delivers…

Google Cloud vs Hetzner
vs

Google Cloud vs Hetzner

Hetzner sells compute by the unit at a low price. Google Cloud sells a platform. The comparison is really about…

Azure vs Hetzner
vs

Azure vs Hetzner

Hetzner sells capacity at a price Azure does not try to match. This comparison covers what the gap actually buys…

OVH vs Contabo
vs

OVH vs Contabo

Contabo sells generous specifications at low prices; OVHcloud sells a full infrastructure catalogue with enterprise options. The comparison is really…

Background reading

Reading Cloud Storage Performance Specifications
Infrastructure 7 min read

Reading Cloud Storage Performance Specifications

IOPS, throughput and latency are three promises, not one. How to read a storage spec sheet so the performance you get matches…

Decided which platform fits?

Both accounts are documented in the catalog, with configurations, credit balances and service limits listed before you buy.

Telegram