Where do you stand? › Route 3 · Vendors & stack
I know which systems I need — who supplies them?
Pick the components you have to put in place. For each one you get the build-vs-buy reading and the market layer that supplies it, with the same scored recommendations and confidence the full analysis uses. Nothing is stored; the selection lives in the URL.
Target market(s)European UnionUnited States (federal)change
Legally-driven components are flagged when their requiring regulation sits outside your selected markets.
density
Step 1 of 2 — pick your components1 selected
Multi-Region Failover & Resilience Testing
Step 2 of 2 — the vendor & stack view
1 of 1 selected components are covered by 1 market layer.
Named vendors are community-maintained, disputable examples — not an endorsement. The stable object is the market layer. Compare with the reference stack for your regulatory profile →
Build or buy, per component (1)
Multi-Region Failover & Resilience Testing buy (products exist) EU
A Sovereign Infrastructure product can carry this; the buyer's duties stay with you.
Required by: DORA in force
Sovereign Infrastructure — covers 1 of your components
Covers: Multi-Region Failover & Resilience Testing. This layer supplies 3 components in the graph.
Confidence: moderate (68/100)
Community-maintained examples
OVHcloud · Scaleway · STACKIT · AWS European Sovereign Cloud · Microsoft Azure EU Data Boundary · Google Cloud Sovereign Controls · Groq · CoreWeave · Lambda Labs · Together AI · Fireworks AI · Baseten · Modal · Replicate · Anyscale
Filters to self-hostable, customer-VPC and open-source options when personal or confidential data cannot leave the EU.
| Example | Sub-category | What it does | Hosting | Claimed alignments |
|---|---|---|---|---|
| OVHcloud | native EU | French provider with EU-only jurisdiction and a narrower managed-AI catalog than the hyperscalers. Typical: EU-resident inference, regulated workload hosting. | not checked | ISO 27001 (claimed)SecNumCloud-positionedGDPR-positioned |
| Scaleway | native EU | EU-operated cloud with GPU instances and managed inference under French corporate control. Typical: EU-resident inference, fine-tuning. | not checked | ISO 27001 (claimed)GDPR-positioned |
| STACKIT | native EU | German provider (Schwarz Group) positioned for data residency in Germany. Typical: public sector, retail data platforms. | not checked | C5-positionedGDPR-positioned |
| AWS European Sovereign Cloud | sovereign hyperscaler | Separately operated EU region set with EU-resident personnel and keys; full hyperscaler catalog. Typical: large-scale enterprise AI, regulated hosting. | not checked | ISO 27001 (claimed)SOC 2 (claimed)EU data-boundary positioning |
| Microsoft Azure EU Data Boundary | sovereign hyperscaler | EU processing and storage boundary across Azure and Copilot services with confidential-compute options. Typical: enterprise copilots, regulated hosting. | not checked | ISO 27001 (claimed)SOC 2 (claimed)EU data-boundary positioning |
| Google Cloud Sovereign Controls | sovereign hyperscaler | Partner-operated and data-boundary variants with external key management. Typical: regulated analytics, EU-resident inference. | not checked | ISO 27001 (claimed)SOC 2 (claimed)EU data-boundary positioning |
| Groq | specialized GPU / accelerator | LPU inference hardware marketed on deterministic low latency rather than training throughput. Typical: low-latency agents, real-time decisioning. | not checked | SOC 2 (claimed) |
| CoreWeave | specialized GPU / accelerator | GPU-dense cloud for training and high-throughput inference with dedicated capacity contracts. Typical: model training, batch inference. | not checked | SOC 2 (claimed)ISO 27001 (claimed) |
| Lambda Labs | specialized GPU / accelerator | GPU cloud and on-prem clusters aimed at research and fine-tuning workloads. Typical: fine-tuning, research clusters. | not checked | SOC 2 (claimed) |
| Together AI | inference platform | Hosted open-weight model inference and fine-tuning with per-token pricing. Typical: open-weight inference, fine-tuning. | not checked | SOC 2 (claimed)open-weight sovereignty positioning |
| Fireworks AI | inference platform | Optimised serving of open-weight models with function-calling and structured output support. Typical: agent tool-calling, high-QPS inference. | not checked | SOC 2 (claimed)HIPAA-eligible (claimed) |
| Baseten | inference platform | Model deployment platform with autoscaling endpoints and VPC deployment options. Typical: custom model serving, VPC-isolated inference. | not checked | SOC 2 (claimed)HIPAA-eligible (claimed) |
| Modal | serverless compute | Serverless GPU execution for jobs, batch pipelines and sandboxed agent tasks. Typical: batch pipelines, sandboxed execution. | not checked | SOC 2 (claimed) |
| Replicate | serverless compute | API-first hosting of community and custom models, priced per run. Typical: prototyping, multimodal inference. | not checked | vendor-stated security posture |
| Anyscale | serverless compute | Managed Ray for distributed training, serving and multi-step agent workloads. Typical: distributed training, agent fan-out. | not checked | SOC 2 (claimed) |
Community-maintained, disputable examples — not an endorsement and not a ranking. Alignments are as claimed by vendors or the source compilation, not verified by RAIN; a certification is shown as a certification only where a certificate or registry reference is recorded.
Disclosure: RAI·N·avigator operates in this category too, so we have a commercial interest in any comparison here. That is why this layer maps product classes to control objectives and lists named products as community-maintained examples — we publish no rankings, no quadrants and no coverage assertions about any vendor, including ourselves.
Select on
jurisdiction of the control plane (not only the data plane), operator nationality and support-access paths, key custody, C5 / C3A / SecNumCloud attestation scope, managed-AI service depth vs. isolation trade-off, exit and repatriation terms
Why this confidence
- 1 in-scope component of this use case is supplied by this layer (Multi-Region Failover & Resilience Testing) — a direct supplied_by path in the graph.
- The catalog use-case match is strong, so the component set this layer was derived from is reliable.
- High-risk tier: this layer carries mandatory Chapter III duties, so some tooling in it is non-optional.
- 15 community-maintained example vendors recorded on the layer node.
- Selection metrics for this layer are documented, so the shortlist can be compared objectively.
- Only 1 of 3 components this layer supplies are in your scope — evaluate a narrow subset of its capabilities.