Gartner puts it plainly: 95% of new digital workloads will run on cloud-native platforms this year, up from just 30% in 2021. That’s the statistic everyone quotes.
What gets left out is less flattering: 60% of organisations still exceed their cloud migration budget, and nearly a third miss their planned timeline entirely. If you’re a UK business owner or technology lead weighing up a move to cloud-native architecture, you’re not choosing between old-fashioned and modern anymore. You’re choosing between doing it properly with a software development company in the UK and joining the majority who get burned on cost, security, or both.
The UK Cloud Picture Right Now Isn’t What You’d Guess
Cloud-native has become the default architecture for new software, and the data backs that up. Across the EU, 52.7% of enterprises used paid cloud services in 2025, with large enterprises at nearly 85% adoption and small businesses trailing at just under half. Kubernetes now sits inside 96% of enterprise software solutions in some form, and two out of three clusters run in the cloud rather than on self-managed hardware.
But here’s the part most vendor content skips over. Research from UK infrastructure provider Pulsant found 87% of UK businesses are planning to repatriate at least some workloads over the next two years. Cost, compliance, and data control — not technical limits — are driving that shift. Cloud-native no longer means “public cloud only”; increasingly it means the right workload on the right infrastructure, chosen deliberately rather than by default.
What Cloud-Native Actually Means
Cloud-native gets used loosely enough that it’s worth pinning down. It isn’t just “we run on AWS” or “we pay a subscription instead of buying servers.” It’s an architectural approach built around three things.
Microservices Instead of One Giant Application
Rather than one monolithic codebase, the application is broken into small, independently deployable services. Each one owns a specific job — payments, user accounts, inventory — and can be updated, scaled, or replaced without touching the rest. That’s why a retailer can push a checkout fix on a Tuesday afternoon without redeploying the entire site.
Containers and Orchestration
Containers package software with everything it needs to run, so it behaves the same on a developer’s laptop as it does in production. Kubernetes has become the default tool for managing containers at scale, deployed by roughly two-thirds of cloud-native teams. It handles the unglamorous work: restarting failed services, distributing load, scaling up during a traffic spike.
Automated Delivery Pipelines
Cloud-native teams build and test code continuously rather than in occasional big releases. Changes move through automated pipelines — build, test, deploy — often several times a day. This is what makes frequent, low-risk releases possible instead of the quarterly deployment freeze many UK businesses still live with.
Must read: AI-Driven Digital Transformation: A Practical Guide for UK Businesses
The Risks Nobody Puts in the Pitch Deck
Migration vendors are good at selling the upside. The data on what actually goes wrong is less flattering, and worth knowing before you sign anything.
Budget Overruns Are the Norm
IDC found that 38% of cloud migrations exceed their original budget, with the average overrun running 23% above plan. Gartner’s figure is higher still: 60% of organisations exceed their initial migration budget, with overruns of 30–50% common. Flexera’s research adds a sting — organisations underestimate their cloud spend by 23% on average even after the migration is finished, not before.
• Estimating cloud costs using on-premises pricing logic instead of consumption-based models
• No budget line for data transfer fees, parallel-running periods, or rollback capacity
• Idle or unused cloud resources nobody is tracking — present in roughly 60% of organisations
Security and Compliance Get Bolted On, Not Built In
GDPR fines can reach €20 million or 4% of global annual turnover, whichever is higher. For UK firms handling EU customer data, the EU Data Act’s cloud-switching and sovereignty requirements add another layer worth mapping before migration, not after. The UK’s own Cyber Security Breaches Survey found cloud backup is now more widely deployed than either two-factor authentication or VPNs for remote staff — a sign that cloud is trusted for resilience, even where broader security posture still lags behind.
The Skills Gap Is Not Going Away
University of Birmingham research warns the UK’s digital skills shortage could leave the equivalent of 380,000 roles unfilled, at a projected £27.6 billion economic cost by 2030. Separately, 81% of UK businesses report being negatively affected by an IT and tech skills shortage, with a fifth experiencing outages or data breaches as a direct result. Experienced cloud architects with Kubernetes expertise now command £700–£1,000 a day on UK contract rates — a fair signal of how stretched the talent pool is.
Also read: Enterprise Resource Planning Implementation in UK
Data Sovereignty Isn’t Optional Anymore
For UK organisations working with EU customers, subsidiaries, or suppliers, data locality has moved from a compliance footnote to a board-level question. The EU Data Act introduces cloud-switching rights and sovereignty obligations for providers operating in the EU, and UK financial services firms already face their own operational resilience expectations from the PRA and FCA around concentration risk with a single cloud provider.
None of this rules out public clouds. It does mean the question “which region is this data actually stored in” needs an answer before a contract is signed, not after a regulator asks.
A Framework That Actually Reduces the Surprises
None of the above is a reason to avoid cloud-native architecture — it’s the direction the industry is moving for good reason. It’s a reason to migrate against a plan rather than a deadline.
Run a formal readiness assessment first — organisations that do this see 2.4x higher migration success rates
• Migrate in phases against one flagship application or capability, not the entire estate at once
• Put FinOps practices in place before go-live, not after — first-year adopters report roughly 20% savings on cloud spend
• Map compliance and data residency requirements against the target architecture before choosing a provider or region
• Budget 10–20% of the total project for risk and contingency — rollback capacity, downtime buffers, audits — rather than treating it as padding
What This Looks Like in Practice
Consider a pattern common across UK mid-market firms moving from a single legacy application to microservices. The finance function is migrated first, since it’s well-bounded and low-risk for testing the new pipeline. Six months later, once the deployment process, monitoring, and cost controls are proven, the customer-facing platform follows.
The order matters as much as the destination. Starting with the highest-risk, highest-visibility system first is where many budget overruns and outages begin — the failures above are rarely about the technology itself, and almost always about sequencing and governance.
The Bottom Line for UK Businesses
Cloud-native isn’t a question of if anymore — the direction is settled. What’s still very much open is how well a given migration is planned, budgeted, and governed. The organisations getting burned aren’t the ones choosing cloud-native. They’re the ones treating it as a lift-and-shift project with a fixed deadline and an underfunded contingency line.
Get the readiness assessment done. Budget honestly. Sort out data residency before the contract is signed, and treat FinOps and security as part of the architecture rather than an afterthought. That’s the difference between landing in the 65% of migrations that finish on time and on budget, and becoming one more line in next year’s overrun statistics.
