B-Roads beats Motorways: Why data centre operators can only mesh their compute in the UK, and not megaproject it
Hyperscale Campuses will die on a hill in the UK - A distributed, meshed network of smaller node Data Centre sites are faster, cheaper, and quietly the better engineering.
There are two numbers that, on their own, sound like good news for British tech:
The first is the sheer weight of capital ready to build AI compute, and the UK makes good sense for european demand.
The second is the government’s enthusiasm to wave it all in.
Put them next to a third number, though, and the optimism curdles: around 50GW of prospective data centre demand is queuing for grid access against a peak national load of about 45GW. We are, in other words, being asked to roughly double the entire country’s peak electricity demand - and funnel most of it into London and the South East - on a grid that was largely designed six to eight decades ago, and was barely coping before the AI wave hit our shores.
The proposals so far really fall down at a conceptual stage, and is a key indicator of how applying US construction models to infrastructure just doesn’t translate with the same efficiencies in the UK.
The hyperscale model is the motorway approach to infrastructure: build one enormous, high-capacity artery, pour everything onto it, and accept years of disruption and astronomical cost to lay it down. That’s seductive on a planning map; but Britain’s roads didn’t get good because we built a handful of motorways - the country runs on a dense, redundant web of B-roads that get you almost anywhere, reroute around a crash, and were mostly already there. I want to make the harder argument that for the vast majority of UK compute, the B-road network is the better piece of engineering, and not the consolation prize.
The motorway dream meets the British reality
What hyperscale needs just isn’t what we can provide. A single hyperscale AI campus wants somewhere between 100 and 300MW of firm power; 100MW alone being enough to power roughly 100,000 homes. It wants that power continuously, in one place, at the cheapest possible rate. In my road metaphor, that’s like a six-lane motorway demanding its own dedicated junction.
The UK fails to provide that energy on all three counts, and it’s worth being specific about why:
The power isn’t there, and won’t be for years. The demand connection queue didn’t creep up, it totally detonated. Contracted demand-side offers jumped from 41GW to 125GW between late 2024 and mid-2025, and interconnection queues in London have stretched to 7-10 years. Even after NESO took a machete to the speculative pipeline, only around 13GW of firm demand can connect before 2030, with the bulk (86GW) slated for the 2030 to 2035 window.
The power is the most expensive in the developed world. This is the part that gets glossed over in the AI gold-rush coverage in UK contexts. UK industrial electricity prices in 2024 were the highest of all IEA members for which data exists, both including and excluding taxes. At around 25.85p/kWh, that’s roughly four times US industrial prices and 46% above the IEA median. A data center is, functionally, a machine for converting electricity into compute. Choosing to site the most power-hungry machine humanity has ever built in the country with the highest cost electricity is a decision that needs a very good reason. Sadly, “the government is keen” is not one.
More than three-quarters of developers are already taking the next exit. This isn’t hypothetical. More than three-quarters of UK data centre developers are now actively looking at sites abroad rather than wait, and in 2025 and 2026 both AWS and Meta publicly paused construction on billion-dollar facilities to reassess whether promised grid connections would materialise at all.
A quick word on Britain’s track record with big things
Aside from the grid restrictions, it’s worth thinking about our history with megaprojects. Simply put, we’re total shit at them.
Take Hinkley Point C. First planned at £18bn with operations expected around 2025, the cost has now surged past £48bn, and won’t start generating until 2030 at the earliest. That’s a near-triple on budget and a five-year-plus slip, on a project whose entire job is to produce the cheap, firm power these data centers need.
Or HS2; the purest example we have of the motorway mindset. Originally estimated at £35-45bn in 2019, now revised to a range topping out at £102.7bn, with the full route not operational until somewhere between 2040 and 2043 - and they’ve quietly slowed the trains down to claw back money. A complete cancellation was dismissed because the remediation cost for work already done came in at £58bn. Let that sink in: the bill to stop exceeded the original budget to build. One grand line between two cities, decades late, and the rest of the network it was meant to relieve gets nothing in the meantime.
The pattern is consistent and it’s structural. Britain is poor at delivering single, monolithic, mega-scale infrastructure on time and on budget. So why would we architect our compute future as a string of these things, each one a bespoke decade-long fight with the grid, the planners and the local community?
The hyperscale campus concept is the HS2 of computing - enormous, singular, fragile, and perpetually three years from a press release apologising for the delay. Meanwhile, the unglamorous B-road network quietly does most of the actual work - and so that’s where we need to build our data centre capacity.
The case for the mesh
For the vast majority of UK workloads, the answer is a distributed, meshed network of small-to-medium sites. I’ve made adjacent versions of this argument for manufacturing and for modular container-based deployment, but the grid reality makes it sharper for compute than anywhere else.
1. It spreads the load instead of concentrating it. A 200MW campus needs that 200MW connection in one spot - which, in the UK, doesn’t exist without years of reinforcement. Twenty 10MW sites can each tap into existing local capacity, distribution substations, and the headroom already sitting in the network across dozens of towns. You’re not demanding one impossible new motorway junction; you’re using forty B-road turnings that are already tarmacked. This is the data-centre equivalent of avoiding the factorial scaling problems I covered in previous articles; scale comes from the volume of facilities, not the output of a single site.
2. It’s dramatically faster. The entire delay in UK data centre commissioning is the connection queue. Smaller sites that fit inside existing connections sidestep the queue almost entirely, especially when paired with on-site generation and storage. In the US, roughly one third of planned new data centre capacity by early 2026 was designed to operate wholly or partly independently of the public grid - up from effectively zero a year earlier. A mesh of energised, already-connected buildings - exactly the distressed-retail conversion play I’ve suggested in other articles, can be switched on now, not in 2035.
3. It improves latency, which is increasingly the whole game. AI inference (the bit users actually touch) wants to be close to them. A local data centre network puts compute in the centre of the towns and cities that consume it, which is the right architecture regardless of the grid argument. The grid constraint just happens to push you toward the thing you should be doing anyway.
4. It’s resilient by design. A single hyperscale campus is a single point of failure - for power, for cooling, for connectivity, and for planning objection. Close a motorway and everything stops; close a B-road and the traffic reroutes through the next village along. Same principle here - if one node drops, traffic redistributes. It’s the same logic as my Elastic Failover Exchange and Carbon Flow Failover pieces; distributed capacity isn’t just cheaper, it’s structurally more reliable, and it opens the door to trading and greening that idle redundancy rather than letting it sit there as dead weight.
We do still need the motorways, but just build them where they belong
None of this means hyperscale has no place. It means that the hyperscale DC campuses should be rationed to the few locations that genuinely justify them, rather than treated as the default. There’s a strong argument for a small number of large, power-hungry sites sited deliberately next to the grid’s actual strong points - close to existing substations, transmission nodes, decommissioned power-station connections, and emerging AI Growth Zones co-located with new generation. The government is already trying to shift data centre demand to unconstrained locations, and that’s the right instinct: put the heavy haulage where the carriageway can take it, and mesh everything else onto the B-roads.
That’s the real strategic prize for the tech firms, too. The operator that stops fighting for the handful of impossible 200MW connections and instead assembles a distributed estate of modest, fast, already-energised nodes will be deploying live capacity while its competitors are still in pre-application meetings. In a market where hardware risks becoming outdated before power is ever delivered, speed of deployment isn’t a nice-to-have, it’s actually the entire competitive moat.
A genuine win-win, if we keep it honest
Laying it all out, it’s a relatively obvious solution - the grid gets a load it can actually absorb, spread across the country instead of piled onto one overloaded junction in the South East. The tech firms get capacity now, lower latency, and resilience baked in. Towns well off the motorway map get investment and infrastructure they’d never see from a single rural mega-campus. And the nation sidesteps yet another HS2-shaped hole in the ground that’s perpetually over budget and behind schedule.
But I’ll end where I usually do. A meshed, distributed model is healthier precisely because it’s plural; many sites, many operators, many landlords, spread across many communities. The danger is that the same handful of hyperscalers with the deepest pockets simply buy up all the good B-road frontage the way they’d have built the campuses, and we end up with a toll road wearing a B-road’s clothes. The network should be distributed all the way down - not just the racks, but the ownership. Build the web of roads. As always, we just need to make sure no single company gets to own every junction on it.
TH
You may find these of interest: