Context
Wombat's multi-provider Terraform coverage includes OVHcloud alongside AWS, Azure, GCP, STACKIT and Hetzner Cloud (framework v1.1.0).
OVHcloud
Assess OVHcloud workloads with the same provider-neutral controls you use on hyperscalers — with a stronger focus on residency and exit.
- European cloud, same control model
- Framework control coverage
- 72 controls with provider-specific checks
- 4 relevant pillars
- 4 starting points
What Wombat adds to the provider view.
OVHcloud is a European provider with framework control coverage in the current control pack. Use the neutral baseline to compare it with the hyperscalers and to make residency, key custody and exit explicit.
The current framework control pack includes 72 controls with OVHcloud-specific checks.
Context
Use the sovereignty hub to connect provider choice to residency, key ownership, exit and supplier risk.
Context
The same control model lets you compare OVHcloud with the hyperscalers without maintaining a separate assessment.
OVHcloud quickstart
Use the OVH provider with the EU endpoint, then score the workload against the same baseline.
main.tf
terraform {
required_version = ">= 1.6.0"
required_providers {
ovh = {
source = "ovh/ovh"
version = "~> 1.0"
}
}
}
provider "ovh" {
endpoint = "ovh-eu"
}
terminal
wombat check . --output jsonUse the standard OVH_* environment variables. The EU endpoint is the default for European workloads.
Known regions in the dashboard map.
Approximate locations only. The dashboard maps 85 region codes for this provider; below are the distinct locations in that map.
Approximate region locations from the dashboard map. Not a datacenter map.
Gradignan, France
Beauharnois, Canada
Roubaix, France
Bishops Stortford, UK
Falkenstein, Germany
Miami, USA
Las Vegas, USA
Chicago, USA
Phoenix, USA
Seattle, USA
Quebec City, Canada
Gravelines, France
Bahia, Brazil
Robopolis, Brazil
London, UK
Warsaw, Poland
Data and verification
Data status. The region labels for OVHcloud are compiled from the WOMBATpass dashboard region map. The current extract is dated 31 Oct 2026. The page currently lists 85 region codes from that map.
Verification. The data has not been cross-validated with the provider. It may be incomplete, approximate or outdated.
Intended use. The information is provided for general orientation only. It is not a guarantee of service availability, a representation of exact datacenter locations, or a statement of provider certification.
Corrections. Providers and other parties may submit corrections — including the provider name, the affected region code or control count, and a public source — to page@wombat-gov.dev or open a correction issue ↗.
Trademarks. Provider names and trademarks are the property of their respective owners. Wombat is not affiliated with, endorsed by or sponsored by these providers; the names are used solely for identification.
License. The provider data on this page is published under CC BY 4.0. It is a derived compilation from the WOMBATpass dashboard and the Wombat framework control pack. Attribution: Wombat Community. The data is provided without warranty. Data license.
Methodology. Read the data methodology →
Pillars that matter on OVHcloud.
The same control model applies across providers, so the comparison stays consistent when the estate does not.
WAF-SOV
Sovereign
The primary lens: residency, jurisdiction, key custody, exit and provider concentration.
Read the Sovereign pillar →WAF-SEC
Security
Identity, network isolation and encryption still determine the security baseline.
Read the Security pillar →WAF-REL
Reliability
Portability and recovery only help if the workload can actually run elsewhere.
Read the Reliability pillar →WAF-OPS
Operational Excellence
Supplier oversight, incidents and evidence collection need an operating model.
Read the Operational Excellence pillar →Control coverage by pillar.
Unique controls with provider-specific checks in the current framework control pack. A control may have multiple checks.
Snapshot of the current framework control pack; counts are not a certification. See the full coverage table →
Start here.
Use the provider-native guidance for depth, and the Wombat baseline for the cross-provider score, comparison and evidence.
Make the European provider choice evidence-backed
Score the OVHcloud workload against the same neutral baseline, then use the sovereignty hub to turn residency and exit into controls.