UK Cloud Policy Turns Toward Supplier Exit Rights

The UK Parliament's Science, Industry and Technology Committee has urged the government to use procurement rules, open standards and contract break clauses to reduce public-sector dependence on a small group of US technology suppliers.

The committee's report, Rewiring the state: Delivering digital government, calls for a "period of over-correction" to break supplier lock-in and support a domestic cloud ecosystem.

Its most direct recommendation is that the government should exercise the break clause in the Palantir Federated Data Platform (FDP) contract in the National Health Service (NHS) and publish a fully costed exit plan by the end of 2026.

The policy signal is specific: cloud sovereignty is being framed less as a branding issue and more as a procurement-control issue.

If the recommendations move into government policy, public bodies would face more pressure to prove that contracts preserve competition, interoperability and exit options.

Contract Concentration Becomes the Evidence Base

The report puts government cloud spending at about £10bn a year and uses a March 2026 HM Revenue & Customs (HMRC) award to Amazon Web Services (AWS) to illustrate the competition concern.

AWS was the only bidder for the 10-year, £472m deal, while the report raises concerns about restrictive licensing practices.

The committee also names Microsoft, AWS and Palantir as US-based providers behind what it describes as dangerous levels of supplier lock-in and systemic fragility.

It links those dependencies to proprietary software, opaque contracts, constraints on small and medium-sized enterprises (SMEs), and possible operational risk around US Cloud Act data-access provisions.

The report recommends a cloud consumption dashboard showing contract awards by company, value, break clauses, licensing terms and value-for-money assessments.

It also calls for the Government Digital Service (GDS) to produce a supplier-lock-in strategy with diversification targets and quarterly reporting.

Open Source Moves From Preference to Procurement Test

The committee wants the government to define technology sovereignty, review that definition annually and use the update to the Procurement Act 2023 to require public bodies to prioritise open source tools and technology over proprietary systems.

It also recommends a minimum procurement share for UK-based and UK-owned startups and SMEs, with quarterly reporting by central departments and public bodies.

For the NHS single patient record, the report says the government should prioritise UK-owned and UK-based suppliers and use open, transparent procurement.

Nicky Stewart, senior advisor to the Open Cloud Coalition, backed the push to reduce public-sector vendor lock-in and said the system should reward choice, interoperability and fair competition.

Conservative peer Lord Chris Holmes said the most important recommendation is to increase competition in the UK cloud market.

He called cloud concentration risk a question of resilience and said the current UK position is "beyond worrying."

The Next Signal Is the Government Response

The recommendations are not legally binding, but the committee's report creates a formal accountability point for digital-government policy.

Select committee findings normally require a government response, while their practical effect depends on whether ministers adopt the measures.

Bill McCluggage, a former deputy government CIO, said the report should be treated as parliamentary scrutiny rather than a government commitment.

Select committees "shine a light," he said, but do not themselves drive change.

Owen Sayers of Secon Solutions called the recommendations the most radical set he had seen in a Parliamentary report in 10 years, but questioned whether the government would move toward a less US-centric policy.

The practical question is whether the government turns the committee's cloud-sovereignty recommendations into procurement rules, contract disclosures and enforceable exit plans.