Hyperscalers Are Building the Digital World Like It’s 2015 — And It Shows

I didn’t set out to diagnose hyperscalers. I wasn’t doing a grand industry analysis. I wasn’t mapping global architecture. I wasn’t trying to understand cloud strategy.

I was just trying to use a popular software provider — and everything kept breaking.

Every time something failed, I followed the thread. And every thread led to the same architectural gap. Eventually I realised I hadn’t been analysing hyperscalers at all. I’d accidentally mapped the substrate failure across the entire industry.

Once you see the pattern, you can’t unsee it.

Across Microsoft, AWS, Google, and Meta, the same structural drift appears:

• meaning drift
• identity drift
• trust drift
• state drift
• execution drift
• provenance drift
• agentic drift

Different companies. Different stacks. Different histories. Same substrate gap.

And it’s not just me. The world is waking up to these problems too.

Vendor lock in isn’t just a technical nuisance anymore — it’s becoming a public conversation. People are asking why their money keeps disappearing into the same handful of providers. Organisations are asking why their systems collapse the moment they try to leave. Governments are asking why critical infrastructure depends on architectures they cannot inspect, cannot govern, and cannot reproduce.

What started as a personal frustration with a popular software provider turns out to be the same structural issue everyone else is now discovering.

And sovereignty is entering the conversation — not as a political slogan, but as an architectural question. When national systems depend on fragmented substrates owned by a tiny cluster of vendors, sovereignty becomes a structural issue. The question isn’t “who controls the cloud?” It’s “who controls the substrate the cloud is built on?”

Follow the thread far enough and you reach a scenario nobody wants to think about: what happens in a moment of global stress when a hyperscaler’s fragmented substrate becomes a single point of failure?

Not a political crisis — a structural one. A world where identity drifts, state collapses, and operational behaviour diverges at the exact moment stability is needed most.

That’s the real risk of building the digital world on 2015 foundations.
And that’s when the penny drops:

Vendor lock in isn’t just a business model. It’s a structural inevitability when the substrate is fragmented.

When your meaning model drifts, you lock people in.
When your identity model drifts, you lock people in.
When your state model drifts, you lock people in.
When your execution model drifts, you lock people in.
When your provenance model drifts, you lock people in.
When your agentic behaviour drifts, you lock people in.

Not because you planned it. But because your architecture forces it.
And when most digital capability sits inside a tiny cluster of vendors, you don’t just get lock in. You get dependency — at national and international scale.

The pattern reinforces itself.

Anthropic’s recent alignment with US regulatory and commercial structures is a perfect example. Not political. Not controversial. Just structural.

And Palantir fits the pattern too — not as a hyperscaler, but as a national scale vendor building critical systems on top of the same fragmented substrate. Their capabilities are impressive, but they still inherit the drift underneath.

AI is still being built inside a very narrow worldview — because the substrate underneath it hasn’t evolved.

And that’s the real issue.

Hyperscalers aren’t just building AI like it’s 2015. They’re building everything like it’s 2015:

• cloud
• identity
• productivity
• devices
• operational logic
• agentic behaviour
• governance
• safety
• provenance

All sitting on fragmented substrates designed for a world where hyperscalers were the only vendors and everyone else had to adapt.

And to be fair, it’s not really their fault. When you’re inside a hyperscaler, you only ever see your slice of the stack — your service, your product, your identity model, your execution path. It’s almost impossible to see the substrate problem from inside the silo. And even harder to know how to retire legacy without collapsing everything built on top of it. The fragmentation isn’t intentional. It’s structural. But structural problems don’t fix themselves.

That world ended a decade ago.

The funny part is that I didn’t mean to map any of this. I just kept encountering the same failure modes — and the architecture kept revealing itself.

The good news is that the substrate gap is fixable — and I’ve already written the architecture that does it.

The real question now is who will be first to adopt it.

It will be led by whoever understands the architecture of global reality — and can prove it. And as nations begin to recognise the need to fix the substrate, they will choose vendors who can actually support a stable, sovereign, future proof digital foundation. Some hyperscalers will adapt. Some won’t.

And right now, hyperscalers ARE building the digital world like it’s 2015 — and it shows.