Britain's state-owned electricity system operator recently handed Palantir a twenty-one million pound contract extension without inviting a single rival bid.
If you've been following how public tech money gets spent across the UK, this won't surprise you. The National Energy System Operator, known as Neso, claimed technical dependency forced their hand. They argued that switching providers wasn't feasible because the existing data architecture is already built around Palantir's software stack.
It's the classic vendor lock-in cycle in action. Once a massive government body or critical infrastructure provider installs a proprietary platform, escaping it becomes terrifyingly expensive and operationally risky. Neso relied on a legal exemption designed for situations where only one supplier can technically do the job.
This deal covers two deeply unglamorous but critical operational workflows: managing electricity grid connections and tracking skip rates. Skip rates measure how frequently the operator bypasses cheaper power generation options to use more expensive power stations instead. With grid connections facing immense scrutiny after an independent expert panel recently rated Neso's performance well below expectations, software efficiency matters more than ever.
The Bigger Picture of UK Government Reliance
This isn't an isolated incident. Palantir's footprint inside British public infrastructure keeps expanding through massive single-source deals.
Earlier this year, the Ministry of Defence awarded the company a massive follow-on enterprise agreement worth two hundred and forty million pounds, similarly structured without a competitive tender. Add those figures to the controversial multi-million-pound data contracts inside the National Health Service and smaller deals with regulators like the Financial Conduct Authority, and a clear pattern emerges.
Critics from multiple political parties are raising red flags. Lawmakers point out that building this level of dependence on a single foreign tech provider creates structural vulnerabilities. When critical national infrastructure relies on proprietary U.S. software to keep the lights on and manage power queues, the line between commercial convenience and national security gets blurry.
Why Technical Dependency Trumps Open Competition
Procurement rules sound straightforward on paper. Public bodies are supposed to run open, competitive tenders to secure the best value for taxpayers.
Reality is messier. Modern data integration platforms aren't interchangeable pieces of Lego. Once an organization spends years feeding its messy, legacy data streams into Palantir's Foundry platform, custom workflows and proprietary data models take root.
If Neso suddenly decided to run a competitive tender for these grid functions today, they would face massive operational hurdles. A new vendor would need months or years to replicate the backend data ingestion pipelines. During that transition, managing grid connections—already a massive bottleneck for renewable energy developers waiting to plug into the system—could grind to a complete halt.
Neso insists this new arrangement is temporary. The contract runs anywhere from ten to twenty-two months, with officials claiming they plan to open the work to proper market competition once the underlying architecture can support a transition. Whether that actually happens or simply turns into another rolling extension remains to be seen.
If you want to understand where public technology spending is heading, watch how these procurement loopholes get used. Vendor lock-in isn't an accident. It's a business model, and right now, it's winning.
