Cloud Infrastructure / 2026 Data
Cloud Repatriation 2026: The Data Behind the CIO Shift
By The Neural Loop Desk · NeuralWired.com
GEICO’s infrastructure team ran the numbers and found something uncomfortable: storage in the cloud was one of the most expensive things they were doing, with AI workloads close behind. So the third largest auto insurer in the country started moving pieces of its stack back home. That single decision is a small window into a much bigger story: cloud repatriation is real, it’s measurable, and in 2026 it’s reshaping how enterprises decide where a workload actually belongs.
This isn’t the “cloud is dead” narrative some headlines are chasing. It’s messier and more useful than that. Below is what the 2025 and 2026 survey data actually shows, who’s really moving workloads and why, and where the skeptics have a point worth taking seriously.
In This Article
What Actually Changed in 2026
Hybrid cloud isn’t a transitional phase anymore. It’s the default. Flexera’s 2026 State of the Cloud Report, based on 753 cloud decision makers, found that 73% of organizations now operate a hybrid estate, up three percentage points year over year. Among organizations with more than 5,000 employees, that number climbs to 78%.
At the same time, public cloud spending keeps climbing. Gartner forecasts worldwide public cloud end user spending will hit $723.4 billion in 2025, a 21.5% increase. Those two facts sound contradictory until you understand what repatriation actually looks like on the ground: it’s workload by workload, not company by company.
Why this matters
Repatriation and cloud growth are rising at the same time because net new cloud adoption still outpaces the workloads moving out. This isn’t an exodus. It’s a correction, and it changes how every infrastructure team should evaluate a new deployment.
The Numbers: Planned vs. Actual Repatriation
The gap between intent and action is the most important, and most underreported, part of this story.
| Metric | Figure | Source |
|---|---|---|
| CIOs planning some workload repatriation in 2025 | 86% (highest ever recorded) | Barclays CIO Survey |
| Cloud workloads actually repatriated so far | 21%, up 2 points YoY | Flexera 2026 Report |
| Organizations planning a full cloud exit | 8% to 9% | IDC Server and Storage Workloads Survey |
| Cloud infrastructure spend considered wasted | 27%, down from 32% four years ago | Flexera 2026 Report |
Read those four rows together and a clearer picture forms. Most CIOs are open to moving something. Very few are moving everything. And the underlying driver, wasted spend, is actually improving as FinOps practices mature. That’s not the framing most “cloud is dying” articles use, but it’s the one the data supports.
Years ago, people talked about repatriation, but “no one was doing it, it just wasn’t a thing.” Brian Adler, Senior Director of Cloud Market Strategy, Flexera · CIO Dive
What changed since then is measurement. Adler’s colleague Jay Litkey, SVP of Cloud and FinOps at Flexera and a governing board member at the FinOps Foundation, put it plainly: teams have gotten good enough at cost allocation that “FinOps is providing the data to make repatriation decisions.” Before, repatriation was a hunch. Now it’s a spreadsheet.
Why Enterprises Are Rethinking Cloud-First
Four drivers show up consistently across the survey data and the case studies:
- Cost at scale. A third of surveyed organizations now budget $12 million or more a year for public cloud, according to CIO Dive’s reporting on Flexera’s survey. At that spending level, even small percentage savings translate into real capital.
- AI and GPU workloads. Steady, high utilization AI workloads often price out better on owned infrastructure than on elastic cloud billing, which is one reason GEICO named AI spend as a specific pain point alongside storage.
- Data sovereignty and compliance. Regulatory frameworks like the EU AI Act are pushing some workloads toward infrastructure with clearer jurisdictional control.
- Vendor lock-in fatigue. After a decade of cloud-first defaults, some infrastructure teams are simply asking whether “cloud” was ever the right answer for a specific, predictable workload, rather than a blanket policy.
IDC’s Natalya Yezhkova, Research VP in the firm’s Enterprise Infrastructure Practice, frames the shift as a change in posture rather than a reversal. Cloud only is “becoming a less prevalent approach,” she told Data Center Dynamics, replaced by what she calls a “cloud also” mindset.
Real Case Studies: GEICO, 37signals, Dropbox
GEICO: The Insurer Rethinking a 600-App Migration
GEICO began migrating to the cloud in 2013 across more than 600 applications. Over a decade later, Rebecca Weekly, VP of Platform and Infrastructure Engineering, confirmed to The Stack that the company is repatriating workloads as part of a broader architectural overhaul. Her reasoning was direct: “storage in the cloud is one of the most expensive things you can do.”
37signals: The Most Cited Number in Every Repatriation Article
37signals, the company behind Basecamp and HEY, pulled its infrastructure off AWS and Google Cloud starting in 2022. It now reports roughly $1.3 million to $1.5 million in annual savings, or close to $7 million over five years, according to figures compiled by HyScaler. It’s the go-to proof point in nearly every article on this topic, and for good reason. But it comes with a catch, more on that below.
Dropbox: The Original Case Study
Dropbox’s build out of its own storage system, known as Magic Pocket, starting around 2013, is widely considered the founding example of large scale repatriation, predating the current wave by roughly a decade.
The Counterargument: Is This Overstated?
Not everyone buys the resurgence narrative, and the skeptics deserve equal airtime here.
Corey Quinn, Chief Cloud Economist at The Duckbill Group, has argued that “cloud repatriation isn’t a thing” in any broad sense, and points out that the loudest advocates for leaving the cloud often have a commercial stake in that outcome. It’s worth noting Quinn’s own firm sells cloud cost optimization services, meaning his incentive runs the opposite direction: keep clients on the cloud, just spend less. Both sides of this debate have a horse in the race.
Gartner has gone further, publishing research titled “Moving Beyond the Myth of Repatriation,” arguing that on-premises vendors are pushing a false narrative and that most repatriation projects that fail were poorly scoped from the start, not doomed by the cloud itself.
There’s also a semantic wrinkle worth flagging. Gartner analyst Rene Buest calls much of what gets reported as European repatriation “geopatriation” instead, meaning companies are moving to local or regional cloud providers, not back to private infrastructure. In a survey of 241 Western European IT leaders conducted between May and July 2025, 61% said geopolitical factors would increase their reliance on regional cloud providers. That’s a real trend, but it’s a different trend than the one most headlines describe.
The honest caveat on 37signals
37signals runs steady, predictable, well understood workloads, which is close to the textbook best case for repatriation. Most enterprises have a far messier workload mix: bursty traffic, legacy dependencies, uneven ownership across teams. The $7 million savings figure is real, but treating it as a universal template is where a lot of repatriation projects go wrong.
What CTOs and FinOps Leads Should Do Now
The practical shift for infrastructure leaders isn’t “leave the cloud.” It’s building a documented, ongoing framework for deciding where each workload belongs, evaluated on cost, compliance, latency, and data gravity, rather than defaulting to cloud-first for everything new. We broke down exactly that process, including a five-step workload placement model and ROI benchmarks, in our companion piece on a five-step AI workload placement framework for structuring that shift.
A few things worth doing before committing capital to any repatriation project:
- Get real cost-per-workload data before deciding anything. Litkey’s point stands: FinOps maturity is what makes these decisions defensible instead of reactive.
- Separate “predictable and steady” workloads from “bursty and uncertain” ones. The former are repatriation candidates. The latter usually still favor elastic cloud pricing.
- Factor in the 27% cloud waste figure before assuming repatriation is the only lever. Flexera’s data suggests a meaningful chunk of the cost problem can be solved without moving anything.
- Treat compliance-driven moves and cost-driven moves as separate decisions with separate criteria, since they often point to different infrastructure choices entirely.
Related on-site reading: our breakdown of why Kubernetes runs 82% of enterprise production workloads while average CPU utilization sits at just 8% is directly relevant to the cost overrun conversation, and our analysis of AWS’s bet on edge computing offers a useful counterpoint for teams weighing regional infrastructure instead of a full repatriation.
FAQ
What is cloud repatriation?
Cloud repatriation is the process of moving applications, workloads, or data from public cloud providers like AWS, Azure, or Google Cloud back to on-premises infrastructure, private clouds, or colocation facilities. It’s rarely a full exit. Most organizations move only specific, cost-sensitive workloads.
Why are companies leaving the cloud?
The leading drivers are unpredictable costs at scale, data sovereignty and compliance requirements, performance needs for AI and latency-sensitive workloads, and vendor lock-in. Flexera reports 27% of cloud spend is considered wasted, while IDC finds cost and compliance are the top repatriation motivators.
How many companies are doing cloud repatriation?
Roughly 86% of CIOs planned some level of workload repatriation in 2025, the highest rate ever recorded, per Barclays’ CIO Survey. But only about 8% to 9% plan a full exit, per IDC, and actual repatriated workloads sit at 21%, per Flexera’s 2026 report.
Is cloud repatriation a real trend or hype?
Both views have credible backing. Gartner and cloud cost consultants like Corey Quinn argue repatriation is overstated and often vendor driven. Flexera’s survey data shows a real, measurable two point year over year increase in actual repatriated workloads, suggesting a modest but genuine shift, not a mass exodus.
What companies have done cloud repatriation?
The most cited examples are Dropbox, which built its own Magic Pocket storage system starting in 2013, 37signals (Basecamp, HEY), which left AWS and Google Cloud in 2022 and reports close to $7 million in five year savings, and GEICO, which is moving workloads back amid a major infrastructure overhaul after cloud storage and AI costs rose sharply.
Where This Goes Next
The two numbers to watch over the next 12 to 18 months are the 21% actual repatriation figure and the 27% cloud waste figure. If FinOps maturity keeps chipping away at waste, some of the pressure driving repatriation eases on its own. If it doesn’t, expect the 21% to keep climbing toward the 86% intent figure, and expect AI and GPU workload economics specifically to be the next flashpoint.
Three things worth tracking:
- Whether Flexera’s next report shows the 21% figure accelerating or plateauing
- How many enterprises follow GEICO’s lead on AI workload placement specifically, separate from general storage costs
- Whether “geopatriation” becomes its own tracked category in 2027 surveys, separate from true on-premises repatriation
What’s clear now, and wasn’t as clear a year ago, is that this isn’t a binary choice between cloud and on-premises. It’s a workload-by-workload calculation, and the companies getting it right are the ones treating it as an ongoing discipline rather than a one-time migration decision.
Want data like this in your inbox before it hits the front page? Subscribe to The Neural Loop at neuralwired.com/newsletter.
Leave a Reply