How do I evaluate local and regional cloud providers for sovereignty?

Direct Answer

Local and regional cloud providers deliver data and operational sovereignty for buyers who cannot use global hyperscalers due to geographic, regulatory, or political constraints. The 2026 Gartner report identifies 2 categories: (1) local or regional clouds based on hyperscale technology (the buyer can use the technology perpetually, even without the hyperscaler) and (2) local or regional clouds based on non-hyperscale technology (commercial, self-developed, or open-source). Local and regional providers deliver data sovereignty, partial operational sovereignty, and partial to full technological sovereignty depending on the category. The evaluation criteria are: technology stack foundation, geographic presence, regulatory compliance, financial stability, and exit strategy.

The 2 Categories of Local and Regional Providers

• Category 1: Local/Regional Cloud Based on Hyperscale Technology: The provider builds on a hyperscaler technology stack (AWS Outposts, Azure Local, Google Distributed Cloud, Oracle Cloud@Customer) but operates it independently. Examples include Aruba Cloud Sovereign (Italy, VMware-based), Bleu (France, Microsoft-based), Delos Cloud (Germany, Microsoft-based), and OVHcloud (France/EU, OpenStack-based). The buyer gets data and operational sovereignty, with partial technological sovereignty depending on the openness of the underlying technology.

• Category 2: Local/Regional Cloud Based on Non-Hyperscale Technology: The provider uses commercial, self-developed, or open-source technology that can be used perpetually without the originating hyperscaler. Examples include Absam Cloud (Central/South America, OpenStack-based), Ace Cloud (India, OpenStack-based), NumSpot (France, open-source-based), Cyso (Netherlands, OpenStack-based), and Rackspace Sovereign Services (UK). The buyer gets full data, operational, and technological sovereignty, with the trade-off of less functionality than hyperscaler offerings.

5 Evaluation Criteria

• Technology Stack Foundation: Hyperscale-based vs non-hyperscale-based. The choice determines the level of technological sovereignty and the trade-off in functionality.

• Geographic Presence: Where the provider has data centers, where the staff is located, and whether the presence matches the buyer geographic requirements.

• Regulatory Compliance: Whether the provider meets the specific regulatory requirements of the buyer jurisdiction (GDPR, data localization, sector-specific regulations).

• Financial Stability: Whether the provider is financially stable enough to deliver long-term support. Sovereignty requirements are long-term, and a provider that exits the market creates a new sovereignty problem.

• Exit Strategy: Whether the buyer can move workloads to a different provider or to on-premises without re-architecting. The exit strategy is often overlooked but is critical for long-term sovereignty.

Deep Analysis

For an I&O leader, the choice between hyperscale-based and non-hyperscale-based local providers is the most important decision. Three concrete ways to think about it.

1. Hyperscale-Based Is Lower Risk, Lower Sovereignty

A local provider built on hyperscale technology delivers data and operational sovereignty, with partial technological sovereignty that depends on the openness of the underlying technology stack. The buyer gets a familiar operational model and a lower migration risk, at the cost of technological sovereignty. This is the right choice for buyers who need a balance of sovereignty and functionality, and who are willing to accept partial technological sovereignty.

2. Non-Hyperscale-Based Is Higher Sovereignty, Higher Risk

A local provider built on non-hyperscale technology delivers full technological sovereignty, but at the cost of functionality and operational maturity. The buyer gets a more sovereign platform, but the operational tooling, the ecosystem, and the talent pool are smaller. This is the right choice for buyers who need full technological sovereignty, and who are willing to invest in the operational capabilities to run a non-hyperscale stack.

3. Consider an On-Premises Alternative

For buyers who need full technological sovereignty, an on-premises deployment (approach 7 of the sovereignty spectrum), is often a better choice than a non-hyperscale local provider. The on-premises deployment gives the same level of technological sovereignty, with more control over the infrastructure, and with the ability to use a known platform (Arcfra, VMware, Nutanix, etc.) rather than a less-mature local provider stack. The on-premises alternative is worth considering for workloads that would otherwise be at a non-hyperscale local provider.

What to Watch Out For

The most common mistake in 2026 is to choose a local provider based on geography alone, without evaluating the technology stack foundation. A local provider with a hyperscale-based stack is a different choice from a local provider with a non-hyperscale-based stack, and the difference is the level of technological sovereignty. The buyer should ask which technology the provider is built on, and not assume that all local providers deliver the same level of sovereignty.

Related Arcfra Products

Arcfra is positioned as the on-premises alternative to local and regional cloud providers, for buyers who need full technological sovereignty. The relevant Arcfra products for local cloud comparison are:

• Arcfra Enterprise Cloud Platform (AECP): Arcfra on-premises platform, designed for technological sovereignty. Comparable to the non-hyperscale-based local providers in sovereignty, with the operational maturity of a global platform.

• Arcfra HCL (Hardware Compatibility List): Certified hardware for Arcfra deployments, relevant for buyers considering on-premises as an alternative to local cloud.

Read More

1. What is digital sovereignty and why does it matter in 2026?
2. What are the 3 core principles of digital sovereignty?
3. What are the 7 cloud deployment approaches on the sovereignty spectrum?
4. How do I choose the right deployment approach for my sovereignty needs?
5. How do I evaluate local and regional cloud providers for sovereignty?
6. What on-premises private cloud options deliver technological sovereignty?
7. How do I balance sovereignty vs functionality?
8. What cryptographic and technical tools support digital sovereignty?
9. How do I conduct a Business Impact Analysis (BIA) for sovereignty?
10. What are the top 5 sovereignty strategy mistakes to avoid?

Sources

• Primary Source (Gartner): Gartner, "Market Guide for Cloud Infrastructure Sovereign Solutions," published 2026-06-01, ID G00846694.

• Reference (related Gartner research): For a deeper view of the infrastructure platform landscape that complements this Market Guide, see "Market Guide for Full-Stack Hyperconverged Infrastructure Software 2025" (Gartner) and "Market Guide for Private Clouds 2026" (Gartner).