Cloud Repatriation Case Studies: 5 Companies That Saved 60%+
Posted: March 5, 2026 to Technology.
Cloud Repatriation Case Studies: 5 Companies That Saved 60%+
Cloud repatriation is no longer a theoretical exercise. Companies across industries and sizes have moved workloads off public cloud platforms and back to on-premises infrastructure, documenting significant cost savings, performance improvements, and operational benefits. These five case studies demonstrate that cloud repatriation is a proven strategy, not a contrarian gamble.
Case Study 1: 37signals (Basecamp and HEY)
Background
37signals, the company behind the project management tool Basecamp and email service HEY, was one of the most prominent cloud repatriation stories of 2023 through 2024. Under CTO David Heinemeier Hansson, the company publicly documented its migration from AWS to owned hardware.
The Numbers
37signals was spending approximately $3.2 million per year on AWS cloud services. After purchasing their own server hardware and colocating it in a datacenter, their projected five-year savings exceeded $7 million. The initial hardware investment was approximately $600,000, which they expected to recoup within six months through eliminated cloud spending.
What They Moved
The company moved their core application infrastructure, including web servers, application servers, database servers, and storage. They retained cloud services for edge caching (CDN), DNS, and a small number of workloads that benefited from cloud's geographic distribution.
Key Takeaway
37signals demonstrated that mid-sized SaaS companies with stable, predictable workloads can achieve dramatic savings through repatriation. Their public transparency about the process encouraged other organizations to evaluate their own cloud costs critically.
Case Study 2: Dropbox
Background
Dropbox began its cloud exit from AWS in 2016, building its own custom infrastructure called Magic Pocket. While this predates the current repatriation wave, it remains one of the most significant cloud exits in terms of scale.
The Numbers
Dropbox saved approximately $75 million over two years by moving the majority of its storage infrastructure off AWS. Their gross margins improved by 10 percentage points, from approximately 33 percent to 43 percent, a direct result of reduced infrastructure costs.
What They Moved
Dropbox moved over 500 petabytes of file storage from AWS S3 to custom-built storage infrastructure in colocated datacenters. They retained AWS for some ancillary services and for geographic edge presence.
Key Takeaway
For data-intensive businesses, the cost of cloud storage at scale is prohibitive. Owned storage infrastructure, while requiring significant engineering investment, provides dramatically better economics at petabyte scale.
Case Study 3: GEICO
Background
GEICO, one of the largest insurance companies in the United States, publicly announced in 2024 its shift away from cloud-first to a hybrid infrastructure strategy that favors on-premises for core workloads. After extensive cloud migration to Azure, the company determined that the costs and complexity did not justify the approach for their stable, regulation-heavy workloads.
The Numbers
While GEICO has not publicly disclosed exact figures, industry analysts estimated their cloud spend was in the hundreds of millions annually. Their shift back to on-premises for core processing workloads was projected to reduce infrastructure costs by 40 to 60 percent over a multi-year period.
What They Moved
GEICO focused on moving core insurance processing, claims management, and data analytics workloads back to their own datacenters. Customer-facing web applications and mobile backend services were evaluated on a case-by-case basis.
Key Takeaway
Even Fortune 500 companies with massive budgets are finding that cloud costs at scale do not deliver the expected value for stable, compliance-regulated workloads. The insurance and financial services industries, with their stringent regulatory requirements and predictable processing patterns, are particularly well-suited for on-premises infrastructure.
Case Study 4: European Manufacturing Firm
Background
A European manufacturing company with 2,000 employees migrated their ERP system, production management software, and engineering workstations from Azure to on-premises infrastructure running Proxmox VE. This case study is representative of the mid-market manufacturing sector's repatriation trend.
The Numbers
Their Azure spend for the ERP and production management workloads was approximately 15,000 EUR per month (180,000 EUR per year). The on-premises replacement cost 65,000 EUR in hardware (three Proxmox servers with ZFS storage) plus approximately 2,000 EUR per month in operational costs. The three-year TCO was approximately 137,000 EUR versus 540,000 EUR for Azure, a savings of 75 percent.
What They Moved
The company moved their SAP ERP system, production management databases, engineering CAD file storage, and internal collaboration tools. They retained Azure AD for identity management and Microsoft 365 for email and productivity.
Key Takeaway
Manufacturing companies with ERP and production workloads benefit significantly from on-premises infrastructure. These workloads are stable, latency-sensitive (production floor systems need fast database access), and subject to data sovereignty requirements under GDPR.
Case Study 5: Defense Contractor (CMMC Compliance)
Background
A small defense contractor with 50 employees needed to achieve CMMC Level 2 compliance to maintain Department of Defense contracts. Their initial approach was to use a CMMC-compliant cloud enclave (GovCloud), but the costs were prohibitive for a company of their size.
The Numbers
The GovCloud solution was quoted at approximately $8,000 per month ($96,000 per year) for their workload profile. An on-premises Proxmox cluster with LUKS encryption, proper network segmentation, and compliance-grade backup was built for approximately $20,000 in hardware plus $500 per month in operational costs. The first-year total was $26,000 versus $96,000, a savings of 73 percent. Subsequent years saved even more as the hardware cost was already absorbed.
What They Moved
The contractor built their entire CUI (Controlled Unclassified Information) enclave on-premises, including file storage, email archive, project management, and engineering collaboration tools. Non-CUI workloads remained on standard cloud services.
Key Takeaway
For defense contractors and organizations handling sensitive data, on-premises infrastructure often provides a more cost-effective and simpler path to compliance than cloud-based alternatives. The compliance boundary is smaller and more controllable when you own and operate the infrastructure.
Common Themes Across These Case Studies
Several patterns emerge from these repatriation examples. Stable workloads save the most because the cloud premium over owned hardware is highest for consistent, predictable compute. Data-intensive workloads amplify savings because cloud storage and egress costs scale linearly while on-premises storage costs are largely fixed after the initial investment. Compliance-driven workloads benefit from simpler boundaries because on-premises reduces the compliance surface area. Hybrid approaches are common because most organizations keep some cloud services while repatriating their core compute and storage.
Is Cloud Repatriation Right for Your Organization
If your organization shares characteristics with these case studies, whether stable workloads, high cloud costs, data-intensive operations, or compliance requirements, cloud repatriation deserves serious evaluation. At Petronella Technology Group, we help organizations perform the analysis, design the target infrastructure, and execute the migration. Our own infrastructure runs on-premises using Proxmox VE, and we bring that operational experience to every client engagement. Contact us for a cloud cost assessment and repatriation feasibility study.
