THURSDAY, JUNE 4, 2026VOL. XXVI · NO. 17
Tech

When the Chips Don't Come, You Build Around Them

Countries that couldn't get compute didn't wait — they built something the U.S. didn't plan for.

By Chasing Seconds · JUNE 4, 20265 minute read

Photo · Rest of World -

The Queue Nobody Talks About

Picture a government minister, somewhere outside the Western hemisphere, sitting across from a U.S. cloud representative who is very politely explaining that the GPUs she needs are allocated through the end of next year. Maybe longer. She nods, takes the business card, and flies home. Then she calls someone else.

This is how the decoupling actually starts. Not with a speech, not with a trade war. With a waitlist.

The story of AI infrastructure has been told almost entirely from one direction — what the big American cloud providers are building, which data centers Microsoft or Google just broke ground on, how many billions are flowing into the Valley this quarter. That story is real. It's also incomplete. Because while that machinery was grinding forward, something else was quietly assembling itself in the gaps. Rest of World has been covering that other story, and across two recent pieces, a pattern emerges that the mainstream tech press has mostly treated as a footnote: countries that faced genuine compute scarcity didn't shrink. They built around the wall.

Scarcity as Design Constraint

In places like India, Brazil, the UAE, and parts of Africa, the constraint wasn't philosophical — it was physical. The GPUs weren't coming fast enough, or at the right price, or under terms that made sovereignty comfortable. So local developers and governments started building AI infrastructure designed to work within those limits. Lighter models. Locally hosted systems. Architectures that didn't assume infinite American cloud capacity as a baseline.

Rest of World reported on this directly — developers in these regions treating scarcity not as a failure state but as a specification. When you can't rely on the same resources, you optimize differently. You build for the hardware you have. You train on data that reflects your own languages and contexts, because the dominant English-language models aren't serving your users well anyway. The constraint and the cultural gap turn out to be the same problem, and solving one starts to solve the other.

I've watched this cycle in tech before. The regions that get overlooked by incumbents don't just adopt later — sometimes they adopt differently, and the difference ends up mattering. Mobile payments in markets that skipped the credit card era. Messaging apps that evolved under bandwidth constraints. The pattern keeps repeating, and it keeps surprising people who should know better.

The Deal That Rewrites the Template

Then there's the specific arrangement that Rest of World surfaced in its second piece, which feels like the clearest signal yet. G42, the UAE-based AI company, is deploying a U.S.-designed supercomputer in India. The hardware has American origins. The arrangement does not follow American cloud logic.

What's being described here is a government-ownership model — India getting physical control over AI hardware rather than renting access from a U.S. provider at arm's length. The distinction sounds bureaucratic until you think about what it means over a decade. If your AI infrastructure is a subscription, your leverage is whatever the contract allows. If it's a building full of hardware you own, the calculus changes entirely.

The U.S. has been accustomed to both selling the picks and running the mine. This arrangement starts to separate those two things. American chip design still wins a round. American cloud dominance does not.

G42 functions as the intermediary here — a Gulf-based entity with the capital and the relationships to broker this kind of deal, operating in a space that a U.S. hyperscaler wouldn't occupy the same way. That's not a coincidence. It's a structural opportunity that opened because American providers optimized for one kind of customer.

What the Incumbents Built

There's a version of this where U.S. cloud dominance was always a temporary condition — a first-mover advantage that looked permanent because the challengers hadn't organized yet. The infrastructure gap was real, and the American providers filled it fast, and for a long time there was no credible alternative. So the alternative got treated as a future problem.

The future problem is now a present arrangement, being signed and deployed, in one of the largest countries on earth.

The deeper irony is that scarcity — the thing that was supposed to keep the rest of the world dependent — became the forcing function for independence. When you can't get the resource reliably, you stop building systems that require it reliably. You develop different instincts. And those instincts, once developed, don't go away when supply improves. They become the foundation of something that doesn't need to ask permission.

There's a version of this in every industry. The supplier who made themselves indispensable, and then scarce, and then discovered that indispensable and scarce together is just a different word for replaceable. The U.S. tech industry has been so focused on the race between its own giants that it may have underestimated how many people were watching from outside the track, drawing their own maps.

The minister with the business card and the empty promise of GPU allocation? She stopped waiting. The question now is what she built while no one was looking.

End — Filed from the desk