ra2 studio - Fotolia
AI’s next compute layer is likely to come from outside Silicon Valley
AI infrastructure is moving beyond hubs like Silicon Valley. Nations like India, Brazil, and the UAE are building sovereign, power-conscious capacity to solve local compute scarcity
For years, the assumption around AI infrastructure was easy to accept. Serious compute would be built where hyperscale cloud, developer density, and capital were already concentrated, namely California, Seattle, London, and a small circle of established technology hubs.
There was a practical reason for that geography. Training and deploying AI at scale requires datacentres, compute, networking capacity, energy, and advanced infrastructure to work together.
OECD analysis notes that this has pushed AI firms toward services operated by the largest cloud computing suppliers. Over time, that dependence hardened into market concentration. In the third quarter of 2025, Synergy Research Group put Amazon, Microsoft, and Google's combined share of global enterprise cloud infrastructure spending at 63%.
That logic now looks less durable. Compute is becoming more expensive, more power-intensive, and harder to access outside a small group of dominant providers. Builders are starting to confront questions that hyperscale cloud mostly let them ignore.
Where will the power come from? Can chips be shipped to this jurisdiction? Whose laws apply to the data once it moves?
Those questions are getting answered in different places now, and most of them are not in Silicon Valley.
What scarcity teaches
In established cloud markets, the default answer to rising AI demand is to add more capacity through larger cloud contracts, denser datacentre buildout, and deeper dependence on the same centralised stack.
That answer is becoming harder to scale. Datacentres consumed about 1.5% of the world's electricity in 2024, which was enough to make energy one of the pressure points in AI infrastructure. The International Energy Agency expects that share to rise to just under 3% by 2030, making compute harder to treat as a hidden layer behind AI products.
In much of the developing world, that pressure was already the starting point. Builders there have rarely had the option of treating compute access, power, and distribution as someone else's problem. They have had to design for it.
The result is a quieter pattern that does not get much attention in Silicon Valley coverage. Namely that serious AI infrastructure is now being built in places where scarcity is treated as a design problem rather than an afterthought.
What this looks like in practice
The pattern is most visible across four regions.
In India, Yotta Data Services runs Shakti Cloud on more than 16,000 NvidiaH100 GPUs and is on track to roughly double that by the end of 2025. Over half of the compute behind the IndiaAI Mission – the government's push to build indigenous foundation models – sits on Yotta's hardware.
In February 2026, the national multilingual platform Bhashini moved off foreign hyperscalers and onto Shakti Cloud, picking up roughly 40% in performance along the way. Bhashini runs real-time translation across 11 Indian languages at population scale and the people running it had decided that infrastructure they could not govern was the wrong place to put it.
Across Africa, Cassava Technologies, founded by Zimbabwean entrepreneur Strive Masiyiwa, is deploying 12,000 Nvidia GPUs across datacentres in South Africa, Egypt, Kenya, Morocco, and Nigeria.
Cassava is the first Nvidia Cloud Partner on the continent. Before this buildout, Nvidia estimated that roughly 80 of its GPUs were installed across the entire African continent. The constraint was not only compute pricing; it was the basic absence of advanced silicon.
Cassava's response is a pan-African network running on its own fibre backbone, designed so that African startups, researchers, and governments do not have to route through Europe or the United States to train and deploy AI.
In Brazil, the government's SoberanIA project reserves 500MW for a sovereign AI factory in Piauí, powered entirely by renewable energy, with Scala datacentres as lead infrastructure partner.
Meanwhile, Brazil has committed to attracting up to $370 billion in datacentre investment over the next decade, tied to the REDATA program's tax incentives for projects sourcing 100% renewable power. Roughly 65% of Brazilian data is still stored abroad. The wager is that abundant hydroelectric and solar power gives Brazil the kind of compute the US and China have to work harder to build – clean by default, cheap by geography.
The United Arab Emirates is taking the most expensive route. Core42, part of the G42 group, sells inference capacity on a mix of Nvidia and Qualcomm chips out of Abu Dhabi, and the country has committed jointly with the United States to a 10-square-mile, 5GW AI campus that should be partially operational by the end of the decade.
The Emirati pitch is straightforward. Countries that want sovereign AI but cannot build the underlying stack themselves can rent one from a friendly government. The Middle East Institute describes it as a deliberate strategy of vertical integration – owning the chips, the power, the datacentres, and the foreign relationships in one piece.
These projects do not share a politics or an ownership model. What they share is a starting assumption that compute access, power, land, and chip supply are first-order design problems rather than externalities. That assumption produces different infrastructure.
Why inference changes the map
Training large models still rewards dense clusters, large capital budgets, and access to advanced chips. That work is unlikely to leave the largest hyperscale facilities soon.
Inference is a different problem. Models are used continuously, by customers, devices, agents, and enterprise systems. McKinsey expects inference to overtake training in AI datacentres by 2030, to account for more than half of AI compute and roughly 30% to 40% of total datacentre demand.
Inference asks different questions than training does. Rather than where the largest cluster can be built, the questions become where compute should sit, how fast it can respond, how reliably workloads can be routed, and whose laws govern the data while it does so. Those questions have geographic answers that hyperscale concentration does not handle well, especially for the billions of people who do not live within easy latency of a US or European datacentre.
The compute fabric that inference demand requires is broader than hyperscale cloud alone can provide. Distributed GPU capacity, regional inference clusters, sovereign clouds, and emerging neoclouds in places such as Mumbai, Nairobi, São Paulo, and Abu Dhabi are not substitutes for hyperscale. They are the layer hyperscale cannot serve on its own.
What this means for the map
The old map of AI infrastructure was drawn around places where cloud capacity was already concentrated. That map made sense when compute was treated as cheap and abundant.
The next map will look different. It will be drawn around places that learned to build when compute was costly and strategic, and where the question of who controls the stack was never theoretical. The companies and governments doing that work are not catching up with Silicon Valley. They arrived at the problem first, because they had to.
Ilman Shazhaev is founder and CEO of Dizzaract, an AI infrastructure company headquartered in Abu Dhabi. He serves as a UN/UNODC expert panel member advising on AI applications in developing economies and has authored 46 scientific articles and 10 registered invention patents.
Read more about datacentre pipeline
- Data dive: A new American Century in the datacentre pipeline? Looking at datacentre development internationally, we see how the UK faces apparent relative decline, how countries are responding to the AI age, and what MW vs GDP can tell us
- Hit the north! UK datacentre focus shifts to M62 and points north. Barbour ABI data shows 8GW of total datacentre pipeline with most big projects in the north and Scotland, while London and the M4 corridor are about 25% of projected capacity
