Evidence comparison
OVHcloud and Hetzner Cloud: what the public record shows about each
Both products turn up on cloud and sovereign cloud shortlists, so this page puts their two evidence records next to each other: 15 items on OVHcloud and 20 on Hetzner Cloud, each one linked to the source it came from. It does not name a winner, and the section below explains why the numbers cannot be subtracted from one another.
Read the counts correctly
More advisories does not mean less secure. A vulnerability register records what researchers found and what the vendor disclosed. A product deployed in thousands of organisations with a mature disclosure process accumulates far more entries than a product nobody audits. A low count can mean a small install base, a young product or a vendor that publishes little, and a high count often marks the opposite.
The two counts are not measured with equal precision. An advisory is only listed against a vendor when the register ties it to one of its products by name, and vendors differ enormously in how consistently their products are named. Here that gap is 0 unattributable entries for OVHcloud against 0 for Hetzner Cloud, which moves the advisory row far more than the products do. Both numbers are in the table so the difference is visible rather than hidden.
Treat this page as two records shown together, never as one score minus another.
The two records side by side
| Measure | OVHcloud | Hetzner Cloud |
|---|---|---|
| Evidence items in the recordSize of the record, not a quality signal. | 15 | 20 |
| Kinds of source | 2 | 2 |
| Advisories attributed to the vendor's productsCounts scrutiny and deployment breadth. See the caution above. | 0 | 0 |
| Register entries that could not be attributedEntries naming the vendor that could not be tied to one of its products, so they are excluded from the row above. Read the two rows together: where this number is high, the registers describe that vendor's products less consistently, and the advisory count above says more about naming than about the product. | 0 | 0 |
| Of those, in the CISA known-exploited catalogueExploitation observed in the wild. The one count worth reading closely. | 0 | 0 |
| Share from government registers | 0% | 0% |
| Share the vendor cannot edit | 100% | 100% |
| Public practitioner threadsReflects community size as much as product behaviour. | 6 | 9 |
| Most recent entry | Jul 17, 2026 | Jul 03, 2026 |
| Sources last re-queried | Jul 17, 2026 | Jul 17, 2026 |
Where each record comes from
The registers and platforms behind each column, with the body that operates each one. A record resting on government registers carries different weight from one resting on the vendor's own documentation, which is why this is shown per vendor rather than merged.
OVHcloud
| Source | Operated by | Classification | Items | Latest |
|---|---|---|---|---|
| Engineering discussions | Hacker News, public threads | Independent | 10 | Dec 01, 2025 |
| Analyst, review and reference sources | Recognised analysts, review marketplaces and technology press | Independent | 5 | Jul 17, 2026 |
Hetzner Cloud
| Source | Operated by | Classification | Items | Latest |
|---|---|---|---|---|
| Engineering discussions | Hacker News, public threads | Independent | 16 | Jun 15, 2026 |
| Analyst, review and reference sources | Recognised analysts, review marketplaces and technology press | Independent | 4 | Jul 03, 2026 |
Documented vulnerabilities
Only entries tied to a product of the named vendor by a structural signal are listed: an advisory reference on the vendor's own domain, the vendor as the assigning authority, or the affected product list naming it. Entries that merely mention a vendor in passing are excluded from both columns.
OVHcloud
Hetzner Cloud
What practitioners report
Public threads naming each product in their own title. Not curated for sentiment, and not counted as a verdict: a loud thread is one team's experience, not a measurement.
OVHcloud
- Hacker NewsDec 01, 2025Independent
Canadian Court: OVHcloud from France must hand over user data
- Hacker NewsNov 28, 2025Independent
GrapheneOS bails on OVHcloud over France's privacy stance
- Hacker NewsAug 29, 2025Independent
Microsoft can't guarantee data sovereignty – OVHcloud says 'We told you so'
- Hacker NewsAug 27, 2025Independent
Microsoft can't guarantee data sovereignty – OVHcloud says 'We told you so'
- Hacker NewsJun 20, 2025Independent
EU Eyes Ditching Microsoft Azure for France's OVHcloud
Hetzner Cloud
- Hacker NewsJun 15, 2026Independent
Hetzner Cloud prices are up 120%
- Hacker NewsMay 30, 2026Independent
Provisioning a Private Talos Kubernetes Cluster on Hetzner Cloud
- Hacker NewsNov 30, 2025Independent
Why I Built My Own Kubernetes Cluster on Hetzner Cloud
- Hacker NewsAug 15, 2025Independent
Deploy Production-Ready Kubernetes on Hetzner Cloud
- Hacker NewsOct 26, 2024Independent
Tell HN: Switched from Lightsail to Hetzner Cloud, 2 blogs for $4 a month
What neither record can tell you
The two lists below are the honest holes in each record. Everything a choice between these two actually turns on sits outside both of them.
OVHcloud
- No advisory indexed under the name OVHcloud was found in NVD, the European Vulnerability Database, the CISA catalogue of known exploited vulnerabilities or CERT-Bund. That is not a clean bill of health. Products are frequently registered under a parent brand or a component name.
- No authoritative source contributes to this record. Everything rests on independent coverage and on OVHcloud's own material.
- Pricing, contract terms, notice periods and support commitments are not part of any public register. They come from the vendor and belong in a negotiation record.
- Certification status such as ISO 27001, SOC 2 or BSI C5 has to be checked against the current certificate and its stated scope. A valid certificate can still exclude the product being bought.
Hetzner Cloud
- No advisory indexed under the name Hetzner Cloud was found in NVD, the European Vulnerability Database, the CISA catalogue of known exploited vulnerabilities or CERT-Bund. That is not a clean bill of health. Products are frequently registered under a parent brand or a component name.
- No authoritative source contributes to this record. Everything rests on independent coverage and on Hetzner Cloud's own material.
- Pricing, contract terms, notice periods and support commitments are not part of any public register. They come from the vendor and belong in a negotiation record.
- Certification status such as ISO 27001, SOC 2 or BSI C5 has to be checked against the current certificate and its stated scope. A valid certificate can still exclude the product being bought.
Whether OVHcloud is the right choice is not on this page
A record of what is true about a vendor is one half of a decision. The other half is your context: which criteria matter, how heavily each one weighs, what is a hard no, and who has to sign the result off. No public page can know that, and any page that claims to rank vendors for you is guessing at it.
Typical criteria for this category
Needs your case- Data Sovereignty & Residencyweight
- Certifications (BSI C5, ISO 27001, SOC 2)weight
- Scalability & Performanceweight
- Migration Complexityweight
- Vendor Lock-in Riskweight
Criteria shown as examples for cloud and sovereign cloud. Weighting and fit are properties of your decision, not of the vendor, so they are not published here.
What DecisionOS adds on top of this record
- The vendor scored against your criteria with your weighting, not against a generic ranking
- A dealbreaker check against your hard constraints: data residency, contract terms, existing stack
- A side-by-side view of the alternatives on your shortlist, built from this same evidence pool
- This evidence mapped onto your compliance scope: NIS2, DORA, ISO 27001, SOC 2
- A decision memo your board can read, with the trade-offs and the reasoning on the record
Questions this page answers
Which is better, OVHcloud or Hetzner Cloud?
This page does not answer that, and no public page can. Better exists only relative to a decision: which criteria matter, how heavily each weighs, what counts as a dealbreaker and which systems the product has to live next to. What this page gives you is the evidence on both, 15 items on OVHcloud and 20 on Hetzner Cloud, each with its source, so the judgement rests on the record rather than on marketing.
Does OVHcloud or Hetzner Cloud have more vulnerabilities?
Both records currently hold 0 attributed advisories. That comparison is easy to misread. A vulnerability register records what researchers found and what the vendor disclosed, so a widely deployed product with an active disclosure process accumulates more entries than one nobody audits. A low count can equally mean a small install base or a vendor that publishes little. The two figures are also not measured with equal precision: an advisory only counts here when a register ties it to a named product, and 0 entries naming OVHcloud and 0 naming Hetzner Cloud could not be tied to one. The count worth reading closely is how many entries appear in the CISA catalogue of known exploited vulnerabilities, which is 0 for OVHcloud and 0 for Hetzner Cloud.
How independent is the evidence on OVHcloud and Hetzner Cloud?
100 percent of the OVHcloud record and 100 percent of the Hetzner Cloud record come from sources the vendor does not control: government vulnerability registers, public practitioner threads and a fixed list of recognised analysts and technology press. Material either vendor publishes about itself stays in the record and is labelled as a claim.
What does this comparison of OVHcloud and Hetzner Cloud leave out?
Pricing, contract terms, notice periods, support commitments and the current scope of any certificate. None of those appear in a public register; they come from the vendor and belong in a negotiation record. Fit with your existing stack and your compliance scope is also absent, because it is a property of your organisation rather than of a cloud and sovereign cloud product.
Why does nexalign publish this instead of ranking OVHcloud and Hetzner Cloud?
Because a ranking would have to invent the buyer. Every quadrant and score sheet silently assumes a weighting that belongs to someone else's decision. nexalign publishes the record and keeps the weighting where it belongs, in DecisionOS, where it is set by the people who have to defend the outcome.
The full records
OVHcloud: the full evidence record
15 items from 2 kinds of source
Hetzner Cloud: the full evidence record
20 items from 2 kinds of source
Two records do not make a decision
Choosing between OVHcloud and Hetzner Cloud depends on which criteria matter to you, how heavily each one weighs, what your hard constraints are and who has to sign the result off. DecisionOS takes this same evidence pool, scores it against the criteria of your actual decision and produces a memo that holds up in front of a board and an auditor.