Common Framework

Sovereign Supplier Consortium

How non-US cloud providers from Europe, UK, Canada, and Australia can work together to offer a viable alternative to US hyperscalers—and how governments can leverage this combined capability.


1. The Challenge: No Single Non-US Provider Matches Hyperscale

No single European, UK, Canadian, or Australian cloud provider currently matches the breadth and scale of AWS, Azure, GCP, or OCI. However, a consortium of providers working together can match or exceed hyperscale capability.

Capability US Hyperscaler Single Non-US Provider Consortium Approach
Global presence 30+ regions worldwide 5-10 regions typically Combined: 50+ datacenters across 4 jurisdictions
Service breadth 200+ managed services 20-50 services typically Combined: Full coverage via specialisation
Capacity Effectively unlimited Constrained Combined: Sufficient for government workloads
Enterprise support 24/7 global Regional coverage Combined: Full coverage across time zones

Key insight: The consortium model doesn't require building a new hyperscaler. It requires coordinating existing providers to offer interoperable services under a common framework.


2. Consortium Model: How It Works

Structure

Sovereign Cloud Supplier Consortium

GOVERNMENT BUYERS

UK | EU | Canada | Australia

COMMON PROCUREMENT FRAMEWORK

Shared qualification criteria | Standard contracts | SLAs

▼ ▼ ▼

EU Providers

  • OVHcloud
  • Hetzner
  • Scaleway
  • IONOS
  • T-Systems

UK Providers

  • Crown Hosting
  • EU providers
  • with UK DCs

CA/AU Providers

  • Canadian telcos
  • AUCloud
  • Regional hosts

INTEROPERABILITY LAYER

Standard APIs | Data portability | Identity federation

How Providers Participate

Participation Level Requirements Benefits
Tier 1: Full Consortium Member
  • Full compliance with consortium standards
  • Interoperability certification
  • Cross-provider SLA participation
  • Contribution to common tooling
  • Listed on all jurisdiction frameworks
  • Direct award eligibility
  • Joint marketing/positioning
  • Referrals from other members
Tier 2: Associated Provider
  • Sovereignty criteria compliance
  • Standard API implementation
  • Security certification
  • Listed on national frameworks
  • Competitive tender eligibility
  • Pathway to Tier 1
Tier 3: Specialist Provider
  • Sovereignty criteria compliance
  • Specialised capability (e.g., HPC, AI, storage)
  • Subcontract opportunities
  • Specialist lot eligibility

3. Current Sovereign Provider Landscape

European Providers (Available Now)

Provider HQ Datacenters Key Capabilities Gov Accreditation
OVHcloud France 33 DCs: FR, DE, UK, CA, AU, SG Full IaaS, Managed K8s, Databases, Object Storage SecNumCloud (FR), G-Cloud (UK), HDS (Health)
Hetzner Germany DE, FI VMs, Dedicated, Cloud, Object Storage ISO 27001, SOC 2
Scaleway France FR, NL, PL VMs, K8s, Serverless, Object Storage, AI ISO 27001, HDS
IONOS Germany DE, UK, ES, US* VMs, K8s, Databases, S3 Storage ISO 27001, G-Cloud (UK), BSI C5
T-Systems Germany DE, EU-wide Sovereign Cloud, Managed Services BSI C5, ISO 27001
Exoscale Switzerland CH, DE, AT, BG VMs, K8s, Object Storage ISO 27001, FINMA compliant
Infomaniak Switzerland CH Public Cloud, Managed K8s, Swiss Mail ISO 27001, Swiss FDPIC

* IONOS US operations are legally separate; use EU-only infrastructure for sovereign workloads.

UK Providers

Provider Type Capabilities Accreditation
Crown Hosting Data Centres Government partnership Colocation, managed hosting OFFICIAL-SENSITIVE, SECRET
UKCloud (administration) UK-based Multi-cloud, sovereign options G-Cloud, IL2-IL4
European providers with UK DCs EU-owned Full IaaS/PaaS in UK datacenters G-Cloud

Canadian & Australian Providers

Region Providers Notes
Canada Bell, Telus, Rogers (enterprise), SSC infrastructure, OVHcloud Canada, regional providers Limited hyperscale; European partners with Canadian DCs offer best near-term option
Australia AUCloud, Vault Cloud, Sliced Tech, NEXTDC, Macquarie Data Centres Strong sovereign provider ecosystem; PROTECTED certified options available

4. Practical Collaboration Mechanisms

Cross-Border Service Delivery

European providers can serve UK, Canadian, and Australian governments through:

Model A: Local Datacenter Expansion

How it works: European provider builds or leases datacenter capacity in UK, Canada, or Australia.

Example: OVHcloud already has datacenters in UK, Canada, Australia, and Singapore.

Data residency: Government data never leaves national jurisdiction.

Legal: Local subsidiary subject to local law; parent company non-US.

Model B: Joint Venture with Local Partner

How it works: European provider partners with local telco or datacenter operator.

Example: European cloud platform deployed on Canadian telco infrastructure.

Data residency: Data in locally-owned datacenter.

Legal: JV incorporated locally; European partner provides technology.

Model C: Technology Licensing

How it works: European provider licenses platform technology to local operator.

Example: Canadian Crown corporation licenses European cloud platform for sovereign deployment.

Data residency: Entirely local.

Legal: Fully local operation with European technology underpinning.

Interoperability Standards

Consortium members commit to implementing these interoperability standards:

Service Type Standard API Portability
Object Storage S3-compatible API Change endpoint URL; same code works
Container Orchestration Standard Kubernetes API Export manifests; deploy anywhere
Virtual Machines OpenStack or standard VM images Export images in standard format
Databases PostgreSQL, MySQL standard pg_dump / standard backup/restore
Identity OIDC / SAML 2.0 Standard federation protocols
Infrastructure as Code OpenTofu providers Change provider; similar config

Shared Services & Tools

Consortium members contribute to shared open-source tools:


5. Procurement Coordination

Mutual Recognition

Jurisdictions agree to recognise each other's sovereign provider certifications:

Jurisdiction Certification Recognised By
France SecNumCloud EU, UK (accelerated review), CA, AU
Germany BSI C5 EU, UK (accelerated review), CA, AU
UK NCSC Cloud Security Principles EU (review), CA, AU
Australia ASD ISM / PROTECTED UK, CA, NZ (automatic)

Framework Agreements

Consortium providers listed on multiple government frameworks:

Benefit: Once a provider is consortium-qualified, they can compete for government work across all four jurisdictions without separate certification processes in each country.


6. Economic Model for Providers

Why Providers Should Join

Benefit Description
Market access Access to combined government cloud market across 4 jurisdictions [1]
Long-term contracts Government contracts typically 3-7 years with renewal options
Anchor customers Government adoption signals quality to enterprise market
Reduced competition US providers excluded; smaller competitive field
Shared investment Consortium R&D reduces individual provider costs

Government Demand Signal

Combined government demand across consortia members:

€129B European cloud market 2024[1]
24 mo Target migration timeline
4 Markets accessible via consortium
0 US providers competing

7. Next Steps for Establishing Consortium

  1. Government working group establishment
    Representatives from UK CDDO, EU DIGIT, Canadian TBS/SSC, Australian DTA
  2. Provider engagement
    Invite leading non-US providers to participate in consortium definition
  3. Standards agreement
    Agree interoperability standards and certification mutual recognition
  4. Procurement framework updates
    Each jurisdiction updates frameworks to include "Sovereign Consortium" lot
  5. Pilot projects
    Initial cross-border projects using consortium providers

Stronger Together

No single provider matches hyperscale.
A consortium of sovereign providers can.

References

  1. European cloud market size: Statista, "Cloud computing in Europe - statistics & facts" (2024). European cloud computing market valued at €129 billion in 2024. Source. Additional: Synergy Research Group estimates European market at $86.6B (€74B) for public cloud services specifically, growing 24% YoY in 2025. Source.