Provider frameworks are excellent at provider depth. Wombat adds the neutral baseline: the same controls, score and evidence when a workload touches more than one cloud.
The list is grouped by the depth of Wombat support, so the score is never presented as more than it is.
The current framework control pack includes checks for these providers.
Use AWS Well-Architected as the provider-native lens, then add the cross-provider sovereignty, evidence and cost controls that a multi-cloud estate needs.
Keep the Azure Cloud Adoption Framework and Well-Architected guidance, then add a provider-neutral control model for the workloads that do not live in one cloud.
Assess STACKIT workloads with the same provider-neutral controls you use on hyperscalers — and make residency, exit and supplier concentration explicit.
Use the Google Cloud Architecture Framework as the provider-native lens, then add the cross-provider sovereignty, evidence and cost controls that a multi-cloud estate needs.
Assess OVHcloud workloads with the same provider-neutral controls you use on hyperscalers — with a stronger focus on residency and exit.
Assess Hetzner Cloud workloads with the same provider-neutral controls, with a focus on cost efficiency, reliability and European residency.
These providers are available in the dashboard's provider selector. Framework control coverage is expanding; treat the score as partial until the relevant control pack covers the resource types.
Track Alibaba Cloud projects in the WOMBATpass dashboard and apply the neutral control model where the current control pack covers the resource types.
Track Yandex Cloud projects in the dashboard and use the sovereignty lens to make jurisdiction, residency and exit explicit.
Track OCI projects in the dashboard and apply the neutral control model where the current control pack covers the resource types.
The dashboard's region map recognises these providers for region detection. They do not have a dedicated framework control pack yet; the pages are discovery baselines for jurisdiction, residency and provider concentration.
A German cloud provider recognised in the dashboard region map; use the sovereignty lens for residency and jurisdiction.
A Swiss provider recognised in the dashboard region map; useful when Swiss jurisdiction and residency are part of the decision.
A Dutch provider recognised in the region map; pair the efficiency view with the sovereignty and reliability questions.
Deutsche Telekom's Open Telekom Cloud is recognised in the dashboard region map; use the sovereignty lens for jurisdiction and residency.
An Italian cloud provider recognised in the region map; evaluate residency and supplier concentration with the sovereignty lens.
A European provider recognised in the region map; use the neutral baseline where the control pack covers the resource types.
A Dutch provider recognised in the region map; use the sovereignty view for jurisdiction and provider concentration.
A French sovereign cloud provider recognised in the region map; residency, jurisdiction and exit are the natural starting points.
A German provider recognised in the region map; use the sovereignty and evidence views for German procurement questions.
A European provider recognised in the region map; use the dashboard for visibility and verify control coverage before scoring.
A French cloud provider recognised in the region map; use the sovereignty lens for jurisdiction and exit.
A European hosting and cloud provider recognised in the region map; use cost, reliability and residency together.
A French cloud provider recognised in the region map; use the neutral baseline to compare cost, reliability and sovereignty.
A German cloud provider recognised in the region map; evaluate residency, reliability and cost in the same baseline.
A Finnish cloud provider recognised in the region map; use cost, reliability and European residency together.
A Swedish cloud provider recognised in the region map; use the sovereignty view for jurisdiction and provider concentration.
See all providers on one map →
All providers from the dashboard's provider selector and region map are listed above. The framework control pack currently covers AWS, Azure, GCP, STACKIT, OVHcloud and Hetzner Cloud. Alibaba Cloud, Yandex Cloud and OCI are dashboard-tracked. The European region-map group is recognised for region detection; those pages are discovery baselines until a dedicated control pack exists. Multi-cloud and “other” are metadata modes, not providers.
Data status. The region labels on the provider pages are compiled from the WOMBATpass dashboard region map. The current extract is dated 31 Oct 2026.
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 →
