The debate has moved on from which model to deploy to where AI should actually live. New figures cited by The Register show enterprises shifting production AI inferencing away from public cloud and back onto infrastructure they own — a trend enterprises weighing cost, compliance and vendor lock-in can't ignore.
View the data behind this chart
| 2025 | 2026 | |
|---|---|---|
| Public cloud share of… | %56 | %41 |
Why the hosting question now matters more than the model
For the past two years, enterprise AI conversations centred on which large language model to adopt or which use case to tackle first. That question has been overtaken by a more consequential one: where the resulting workload should run. According to The Register's analysis, drifting into public cloud by default because it's familiar or delivers a quick pilot win tends to store up problems that compound as the deployment matures.
AI is not a workload that can be spun up, moved, or switched off without consequence. It is persistent, data-hungry, and increasingly wired into core business processes — which is precisely why the infrastructure decision now carries as much weight as the model selection itself.
The UK data sovereignty test buyers can't skip
Data sovereignty sits at the centre of this shift. Even when data is physically stored locally, foreign legal jurisdictions can retain access rights through the underlying cloud provider — a nuance that matters enormously for regulated sectors handling sensitive customer or proprietary information.
As Oliver Rowell, solution architect at Xtravirt, puts it, the question every organisation needs to ask is "who has the keys to your data?" For organisations in finance, healthcare, defence and the public sector, that single question increasingly determines whether public cloud remains viable for production AI, or whether private cloud, on-premise infrastructure or a managed private environment becomes the only defensible answer.
Cost predictability: the case against renting AI infrastructure
Broadcom's Private Cloud Outlook 2026, cited in The Register's reporting, found that 56 percent of enterprises are now running or planning to run production AI inferencing in private cloud environments, while public cloud usage for the same workloads dropped from 56 percent to 41 percent in a single year.
The reasoning is straightforward: full control over infrastructure gives far greater visibility into how compute resources are actually consumed, which supports a more predictable cost model as AI scales from pilot to production. Public cloud's pay-as-you-go flexibility, useful for experimentation, becomes a liability once inferencing volumes climb and bills become harder to forecast. UK buyers weighing this shift can calculate your cloud vs on-premise TCO before committing budget to either path.
Vendor lock-in: the embedding problem gets worse with time
The longer AI sits inside a given cloud environment, the more deeply it embeds itself in workflows, data pipelines and governance structures built around that provider. Untangling those dependencies later — to address spiralling costs, resolve governance gaps, or move to a more suitable environment — becomes progressively harder and more expensive.
This is the crux of the vendor lock-in risk facing UK buyers today: decisions made during a rushed pilot phase can lock an organisation into a hosting model years before anyone properly assessed its long-term fit. Those reassessing their position now can explore the AI workload repatriation business case before costs and dependencies compound further.

Where private AI already pays for itself
The Register's analysis points to two use cases delivering fast returns without ever exposing sensitive data to a public endpoint. The first is documentation and knowledge search, where Retrieval Augmented Generation draws contextual answers from fragmented internal documentation while keeping the data inside the organisation's own environment. Xtravirt reports rapid returns from RAG deployments running on VMware Cloud Foundation.
The second is secure coding environments for development teams in regulated or air-gapped settings, who need AI-assisted coding support without routing proprietary code through a public API. Buyers building either capability should build your first UK on-prem AI cluster around a clearly defined use case rather than a broad ambition, and estimate your AI GPU requirements before specifying hardware.
The competitive cost of waiting
Will Rodbard, master architect at Broadcom, puts it plainly: "As soon as you give parts of control away, somebody else has the encryption keys or access to the data, and you lose overall control. You can only control cost if you are in charge and in control over who can do what and when."
In our assessment, the gap between organisations that get their AI infrastructure right and those that don't looks set to widen quickly rather than gradually.
For IT teams under pressure to do more with less, private AI offers one of the clearest routes to freeing staff from repetitive work. Buyers evaluating the right hardware and finance route can view our range of GPU accelerators, understand server finance options, or configure a build directly via the Dell server configurator.
- 01The Register — AI needs a home, not a hotel · 13 July 2026
