The Workloads Are Not Leaving

Where production workloads run today and in ten years, and what buyers are changing about them. If sovereignty were moving workloads to sovereign alternatives, the ten-year picture would show sovereign and regional providers gaining share. The largest US cloud providers are the only environment that grows across the decade; every other environment (sovereign and in-country hyperscaler offerings, regional and local providers, on-premises infrastructure, private cloud platforms, and managed hosting or colocation) loses share. The pattern is pervasively consistent across respondent roles, regions, industries, sizes, and sovereignty maturity. For an organization building a sovereignty plan, this settles where the workloads will sit in ten years. What remains open is the terms attached to that hosting: the contract and the architecture around it.

Where production workloads run, today and in three, five, and ten years All respondents

CategoryUS-headquartered hyperscaler cloudSovereign / in-country hyperscaler offeringsRegional or local cloud providersPrivate cloudOn-premises infrastructureManaged hosting or colocation
Today17%16%17%18%17%16%
In 3 years23%15%15%16%17%15%
In 5 years25%16%15%15%16%14%
In 10 years27%16%15%14%15%13%

Source: n=1,940 respondents, normalized by region

Share of production workloads that run on US hyperscalers today: 17.0%

Organizations that expect one environment to hold half or more of their workloads in ten years: 48.4%

Respondents that say it is extremely important that sovereignty comes from the vendors they already use: 41.3%

[We aren't moving] on-prem, but we are diversifying… we're working with another hosting company based in continental Europe for some of our workloads… it became a lot more important criteria [in RFIs and RFPs]. — CIO, retail organization (EMEA)

Organizations worried about depending on US providers are concentrating fastest

Concentration is rising alongside that shift: within ten years, many organizations expect a single environment to hold most of their production workloads, and for most of them, that environment will be a US hyperscaler. Concentration compounds the readiness problem: the more of an organization's workloads sit in one place, the larger any move would be and the fewer places it could go. Organizations most concerned about depending on US-headquartered providers, and organizations pulling work back in-house, expect the steepest rise in US hyperscaler share of anyone in the study. These buyers are staying with the largest providers because that is where new capabilities arrive first, treating a fallback plan as insurance while governing from inside an already concentrated position. Doing that safely requires a tested exit and a second source of support beforehand.

Notably, even holding data in-country in a facility owned by a company headquartered elsewhere does not put it outside the reach of that country's law, and encryption at rest does not change that as long as the provider holds the keys. The defensible test is what is contractually enforceable: who can be compelled to hand over the data, and what migration path exists before anyone needs it.

Workloads are concentrating, and the most worried organizations expect to concentrate fastest All respondents

CategoryAll respondents
Today15%
In ten years48%

Source: n=1,940 respondents, normalized by region

Workloads are concentrating, and the most worried organizations expect to concentrate fastest: share of US hyperscaler workloads by level of concern All respondents

CategoryTodayIn ten years
Not concerned17%23%
Moderately concerned17%25%
Extremely concerned15%26%
Pulling work in-house16%26%
All respondents17%27%

Source: n=363 / 843 / 734 / 456 / 1,940 respondents

We have no concern using U.S. cloud. Our group has bought AI companies in the U.S. But regulations in India mandate that our data reside in our own data centers. — CTO, financial services (Asia-Pacific)

The money is moving between vendors, not back in-house

Most organizations are switching providers, rebalancing workload by workload, or outsourcing more; only a minority are pulling work back in-house. Most buyers also want that sovereignty delivered by the vendors that already run their cloud and infrastructure (see callout). For a leader, the practical lever is the renewal conversation with an incumbent supplier, and the terms that matter are a documented migration path and a second source of support.

The money moves between vendors, not back in-house All respondents

CategoryAll respondents
Switching to sovereignty-aligned providers (same ratio)30%
Re-balancing by workload23%
Pulling more work back in-house23%
Outsourcing more (vetted partners)19%
No change5%

Source: n=1,940 respondents, normalized by region

The provider models buyers expect to engage confirm it. A US hyperscaler with a sovereign or in-country offering (30.4%) and a private cloud platform provider (29.5%) are tied at the top. Regional, local, or sovereign cloud providers, the option most public policy favors, come third (23.4%). No single class of workload dominates what is moving: analytics, backup and disaster recovery, AI training and inference, and core transactional systems are all being moved by roughly a third of organizations.

Provider Models Buyers Expect to Engage All respondents (respondents could select more than one)

CategoryAll respondents
US hyperscaler with sovereign or in-country offering30%
Private cloud platform providers30%
Regional/local/sovereign providers23%
On-premises with commercial open-source vendor19%
Telecom/managed hosting/colocation18%
Systems integrators or MSPs17%
Independent or specialized cloud providers17%
Build internally / on-premises14%

Source: n=1,940 respondents, normalized by region

Respondents expect consolidation; Futurum expects fragmentation

The ten-year projection captures what respondents expect from the estate they know today: fewer environments and a larger share of production workloads on US-headquartered hyperscalers. That is a useful record of buyer intent. It is not necessarily a forecast of the market those buyers will face.

Futurum's three-to five-year outlook points in a different direction. Regulation is becoming more region-specific and more enforceable. Sovereign and in-country cloud offerings are becoming operationally distinct rather than merely positioning. Local and regional providers are gaining relevance, and telecommunications operators are moving from buyers of infrastructure to suppliers of sovereign cloud and AI services.

The result is likely to be a more fragmented supply landscape, not a simple continuation of today's concentration. Public-sector and regulated buyers will have more reasons — and more options — to separate sensitive data, AI, and critical workloads from dependencies they judge difficult to govern, support, or exit. The question for leaders is not whether US hyperscalers will remain central. They will. It is whether a strategy built around today's provider hierarchy remains appropriate as regulation, local capacity, and sovereignty requirements change around it.

That uncertainty will require active management. The survey asked respondents to project their workload mix ten years ahead, yet the technology, regulatory, geopolitical, and supplier landscape has changed materially in only the past two or three years. A ten-year allocation should therefore be treated as a strategic assumption, not an operational plan.

Leaders should test that assumption on a fixed cadence. They should identify which workloads require the newest cloud capabilities today, which could run on regional, sovereign, private, or on-premises platforms as those alternatives mature, and what events would change the preferred placement. The relevant decision may also change as AI and cloud capabilities become more widely available. Where a local provider or sovereign offering trails a hyperscaler today, the capability gap may narrow; when it does, factors such as jurisdiction, support access, operational resilience, cost, energy availability, and proximity to data may matter more than access to the newest feature.

The practical conclusion is not to avoid consolidation. It is to avoid making an irreversible bet on it. Build the portability, support alternatives, contractual rights, and review mechanisms needed to change course before circumstances force the decision.