UK government replaces Palantir software with internally-built refugee system
UK officials have replaced a Palantir-built platform used for the Homes for Ukraine refugee scheme with an in-house system, arguing they can now meet longer-term needs more cheaply and with better control. Commenters note that integrating tens of thousands of applications and accommodation offers is a routine task for government digital teams, and see this as evidence that public-sector tech can often be built internally rather than outsourced to expensive vendors. The move also feeds into wider concerns about Palantir’s role in UK public services, especially the NHS, touching on issues of cost, vendor lock-in, data privacy, and the influence of lobbying and revolving-door careers.
Scope of the Palantir Refugee System & Replacement
- Palantir rapidly built the initial “Homes for Ukraine” platform during an emergency; first six months were free, followed by two paid 12‑month terms (~£10m total).
- The ministry later transitioned to an in‑house system for “steadier service” and lower long‑term costs.
- Several commenters say the problem (forms, integrations, basic workflows) is a standard government CRUD/data-integration task that small teams routinely deliver.
Feasibility and Cost of Building In‑House
- Multiple contributors with gov/health IT experience say such systems could be built by 3–5 developers in a few months, with annual costs in the low hundreds of thousands and often shared across multiple products.
- “Tens of thousands of applications” and “hundreds of thousands of offers” are described as modest scale by modern standards.
- Some argue simple tools (even spreadsheets) could handle this volume, citing past UK COVID data issues as a cautionary tale about naive use.
Procurement, Incentives, and Vendor Lock‑In
- Strong criticism that governments overpay large vendors (Palantir, big consultancies, similar to Salesforce/Oracle) due to:
- Risk aversion (“no one gets fired for buying a big name”).
- Public‑sector pay caps preventing hiring strong engineers directly.
- Procurement rules that favor large, “safe” suppliers.
- Career incentives and “revolving doors” between government and vendors.
- Others note that using contractors can provide flexibility and political cover if projects fail.
Broader Concerns About Palantir
- Many are hostile to Palantir:
- Seen as a surveillance / “spy‑tech” firm embedded in policing, immigration, military targeting, and health data.
- Fears of vendor lock‑in once its platforms sit at the center of workflows.
- Political worries (MAGA alignment, US intelligence links, “adversarial nation” risk, “treason” rhetoric).
- NHS deals especially controversial (large contract values, redacted terms, public distrust, data‑access worries).
- A minority defend Palantir’s core tech (e.g., Foundry) as powerful and well-built and argue outsiders underestimate its capabilities.
State Capacity and Digital Sovereignty
- Repeated calls for the UK to:
- Build more systems via GDS and departmental digital teams.
- Pay competitive salaries to attract talent instead of overpaying contractors.
- Treat domestic, open‑source, “sovereign” solutions as strategic investments that keep skills and tax revenue onshore.