Cloud repatriation: when the numbers support moving back
In brief
A TCO frame for cloud repatriation: what to count, what the exit-fee waivers cover, what 37signals' numbers show, and when moving back doesn't pay.
Steve Elliott · · 6 min read
On this page
The numbers support moving a workload back from public cloud when its demand is steady, its bill is large, and the case survives adding the staff, facilities, software and migration costs the cloud bill used to hide. In our view, the line that decides most cases is staffing, not hardware or egress.
The exit-fee waivers AWS and Google announced in 2024, and Microsoft's equivalent credit, made leaving cheaper, but they remove a one-time cost, not a running one, and they come with conditions. In our view, the best public evidence is still one company's own figures, from a setup most companies don't share.
What should a repatriation business case count?
A cloud TCO comparison works only if both sides carry the same scope.
| Cost line | Cloud side | Owned or colocated side |
|---|---|---|
| Compute and storage | On-demand and committed rates | Hardware, depreciated over its expected life, plus warranty and support |
| Facilities | Included | Rack space, power, cooling, remote hands |
| Network | Egress fees, inter-region traffic | Transit, cross-connects, links to any cloud services you keep |
| Software | Often bundled in managed services | Licenses for databases, virtualization, backup, monitoring |
| People | Cloud and infrastructure engineering | The same, plus hardware, capacity and facilities work |
| Residual cloud | Not applicable | CDN, burst capacity, disaster recovery and anything not moved |
| One-time | Not applicable | Migration engineering, months of running both, exit egress |
| Commitments | Unexpired reservations, savings plans and private pricing | Not applicable |
| Opportunity cost | Engineering time on commitments and cost work | Engineering time on infrastructure instead of product |
Two rules matter most, in our view. Compare against the best cloud cost you could reach with cloud cost optimization, not this year's invoice. And time the move to your commitments. 37signals timed its storage exit to June 30, 2025, when its S3 contract expired.
Capitalized hardware and cloud operating expense hit the income statement and cash flow differently. Confirm the treatment with your finance and accounting advisers.
What do the exit-fee waivers actually cover?
Google announced free data transfer for departing customers on January 11, 2024, and AWS on March 5, 2024. Microsoft offers a similar credit. Their conditions, as of November 2026:
| AWS | Microsoft Azure | Google Cloud | |
|---|---|---|---|
| Scope | All data off all eligible accounts, or all data off one service across them | Data moved off Azure over the internet; all subscriptions on the account canceled afterward | All use of the exited service ended; you must intend to terminate its contract |
| How to start | Request through AWS Support at least two months before the planned start | Open an Azure Support request with start date and volume | Submit an Exit Notice before migrating |
| Time window | 180 days outside the EU; tell Support at once if you need longer | 60 days of egress credit from your stated start date; longer timelines go in the first request | 30 days to start after a 14-day setup, then at least 30 days to migrate, extendable once |
| How paid | Credits for the migrated data | Invoice-level credit after cancellation | Credit on the final invoice |
| Notable limits | Internet transfers only (CloudFront, Direct Connect and Snow excluded); remaining data deleted by the end of the window; EU and UK customers follow separate addenda | Excludes ExpressRoute, VPN, Front Door and CDN egress; UK-billed customers moving data out of UK datacenters can exit single services, with 180 days | Partial migrations of a service are not eligible; internet transfers only |
First, the window is negotiated case by case. In a January 2026 company podcast, a 37signals engineer said it negotiated 90 days with AWS. Its copy of about 10 PB across buckets (about 5 PB of unique objects) took under 10 days.
Second, in our view exit egress at list price is rarely the deciding number below petabyte scale. An illustrative 400 TB moved in one month at Azure's published North America and Europe internet rates ($0.087 down to $0.05 per GB after 100 GB free) costs roughly $23,700, small next to a run-rate decision worth hundreds of thousands a year. The waivers also don't touch ongoing traffic between your data center and the cloud services you keep, a monthly hybrid cloud cost.
What does the EU Data Act change?
The Data Act has applied since September 12, 2025. The European Commission says it removes switching charges, including data egress charges, from January 12, 2027; until then providers may charge the costs they incur. In November 2025 the Commission proposed, in its Digital Omnibus, exempting some custom-made services, and non-infrastructure services from SMEs and small mid-caps, from most switching rules, for contracts signed on or before September 12, 2025. The Council's negotiating mandate of October 22, 2026, keeps the charge-removal article, Article 29, applying to those services. As of November 2026 the omnibus is still a proposal. Confirm with counsel how either rule applies to your contracts.
What do 37signals' published numbers show?
37signals, maker of Basecamp and HEY, has published the most detailed figures we found, in its own posts rather than audited statements.
- The baseline. Its 2022 cloud spend was $3,201,564, including S3 at $907,838. That was already discounted: the team had long-term Reserved Instance and committed-use agreements under a private pricing agreement.
- The 2024 result. In October 2024 David Heinemeier Hansson reported a 2024 cloud bill of $1.3 million against a $3.2 million run rate, said the roughly $700,000 of Dell hardware was recouped during 2023, and projected savings of well over $10 million over five years once storage moved.
- Storage. His March 2025 post put the plan at about $1.5 million of Pure Storage hardware plus a bit under $1 million over five years for warranty and support, replacing S3 spend of just under $1.5 million a year.
The conditions behind the numbers matter more. The team did not change. The new hardware fit into existing data center racks and power limits, which he said is why savings beat the original $7 million estimate. A white-glove data center service provider, Deft, racks and stacks the servers. The math assumes a five-year hardware life. And the workload is steady: he suggests companies with regular demand spikes of 5 to 10 times baseline or more may be good cloud candidates, and for mixed cases advises to "buy the baseline, rent the spike."
In our view, a company without existing racks or an operations team that already runs its own hardware should not expect the same ratio.
An illustrative repatriation TCO
These numbers are made up to show the mechanics. Take a steady workload with a $2.4 million annual cloud bill, which commitments and rightsizing could cut to $2.0 million. Moving it means $1.0 million of hardware on a five-year life, $400,000 of migration engineering and three months of running both, costing $500,000.
| Annual run cost | Two added engineers | Four added engineers |
|---|---|---|
| Hardware depreciation | $200,000 | $200,000 |
| Hardware support | $80,000 | $80,000 |
| Colocation space, power, remote hands | $180,000 | $180,000 |
| Network and interconnect | $60,000 | $60,000 |
| Licenses previously bundled | $150,000 | $150,000 |
| Added staff at $220,000 fully loaded | $440,000 | $880,000 |
| Residual cloud | $250,000 | $250,000 |
| Total | $1,360,000 | $1,800,000 |
| Saving against the reduced cloud bill ($2.0M) | $640,000 | $200,000 |
| Annual cash saving (adds back depreciation) | $840,000 | $400,000 |
| Cash payback on $1.9M upfront | About 2.3 years | About 4.75 years |
| Five-year net cash saving | About $2.3M | About $0.1M |
Against the current $2.4 million bill, the two-engineer case would save $1.04 million a year. Two more engineers turn a strong case into a marginal one, which is why we think staffing deserves the most scrutiny.
When does repatriation make sense, and when doesn't it?
In our view it tends to make sense when:
- Demand is steady. Spikes are modest.
- The bill is large and concentrated. A few big workloads, not hundreds of small ones.
- Data keeps growing. Growing storage compounds the cloud cost.
- You already run hardware. Existing racks and staff cut the incremental cost.
- Commitments are ending. The exit lines up with contract expiry.
It tends not to when:
- Demand is spiky or uncertain. Owning peak capacity you rarely use erases the saving.
- Workloads depend on managed services. Andreessen Horowitz noted in 2021 that the restructuring needed to cut cloud costs sharply can take years, and that moving workloads off the cloud requires a strong infrastructure team that may not be in place.
- The bill is small. Two engineers can cost more than the saving.
- Lock-in is deep. Proprietary services and long commitments make vendor lock-in the real exit cost.
How strong is the wider evidence?
Thin, in our view. In the Andreessen Horowitz essay from May 2021, the authors cited an expert rule of thumb that repatriation costs one-third to one-half as much as equivalent cloud workloads, and said they were not arguing for repatriation. Uptime Institute's February 2025 report, titled "Cloud repatriation is overstated", says in its public summary that workloads leaving the cloud do not appear to reduce overall cloud use; it gives no sample size. We did not find a repatriation survey with published methods that we would rely on.
FinOps itself now reaches beyond public cloud. In the FinOps Foundation's State of FinOps 2026, with 1,192 respondents, 48% said data center spend is in their FinOps scope, up from 36% a year earlier, and 57% said private cloud is, up from 39%.
We think a repatriation case holds up best when cloud, data center, staff and commitments sit in one operating model, so the comparison is redone on the same terms each year rather than once.
Sources
- Google Cloud, Cloud switching just got easier: Removing data transfer fees when moving off Google Cloud, January 11, 2024
- Google Cloud, Applying for free data transfer when exiting Google Cloud, last updated September 11, 2025
- AWS News Blog, Free data transfer out to internet when moving out of AWS, March 5, 2024, updated October 8, 2026
- AWS, Amazon EC2 FAQs: AWS Free Data Transfer Out Program for Switching Customers, accessed November 2026
- Microsoft Learn, Cancel and delete your Azure subscription: data transfer fees when moving all data off Azure, last updated June 7, 2026
- Microsoft Azure, Bandwidth pricing, accessed November 2026
- European Commission, Data Act explained, last updated December 15, 2025
- European Commission, Digital package: general questions, last updated November 20, 2025
- Council of the European Union, Digital Omnibus: mandate for negotiations with the European Parliament, ST 14756/26, October 22, 2026
- 37signals, Our cloud spend in 2022, January 13, 2023
- David Heinemeier Hansson, The big cloud exit FAQ, December 19, 2023
- David Heinemeier Hansson, Our cloud exit savings will now top ten million over five years, October 17, 2024
- David Heinemeier Hansson, It's five grand a day to miss our S3 exit, March 26, 2025
- 37signals, Moving mountains of data off S3 (RECORDABLES podcast transcript), January 8, 2026
- Andreessen Horowitz, The Cost of Cloud, a Trillion Dollar Paradox, Sarah Wang and Martin Casado, May 27, 2021
- Uptime Institute, Cloud repatriation is overstated, Data Report 167, February 2025
- FinOps Foundation, State of FinOps 2026, 2026
Frequently asked questions
Does free egress make cloud repatriation cheaper?
Only for the move itself. AWS, Microsoft and Google waive internet data transfer fees for customers who leave, under conditions such as moving all data off an account or service and finishing within a set window. The waivers do not cover ongoing traffic between your data center and any cloud services you keep, which a hybrid design pays every month.
Can I get free egress if I only move some workloads?
It depends on the provider, as of November 2026. AWS credits customers who move all data off a particular service across their eligible accounts. Google requires ending all use of the exited service. Azure requires canceling all subscriptions on the account, except for UK-billed customers moving data out of UK datacenters, who can exit single services. Moving a few workloads within a service generally does not qualify.
How much did 37signals save by leaving the cloud?
By its own account, its cloud bill fell from a $3.2 million run rate to $1.3 million in 2024, after about $700,000 of compute hardware that it says was recouped during 2023. It projects well over $10 million in savings over five years, including storage. It added no staff and reused existing data center racks and power.
What cost is most often missing from a repatriation business case?
In our view, people. Hardware quotes are easy to get, but running owned infrastructure adds capacity planning, hardware lifecycle and facilities work. In our illustrative example, two more engineers cut a five-year net cash saving from about $2.3 million to about $0.1 million. The second most-missed item is comparing against today's cloud bill rather than the lowest one you could reach.
Steve Elliott
Published November 22, 2026
More on FinOps & Cloud
FOCUS, commitments, shared cost.
Keep reading
Negotiating cloud commitments when capacity is scarce
AWS and Google say demand outruns supply, and all three report backlogs over $550B. What that does to your bargaining power and which terms still move.
Forecasting cloud spend when usage won't sit still
Split committed, usage-driven and AI cloud spend, tie usage to business drivers, forecast in ranges and measure variance by line, with a worked example.
Should product teams own their cloud budgets?
Product teams should hold cloud budgets once allocation puts spend in their name and shared costs have an owner. Prerequisites, guardrails and failure modes.
FOCUS 1.4 and invoice reconciliation: matching cloud cost data to what accounts payable pays
Why cloud cost data rarely matches the invoice, what FOCUS 1.4's Invoice Detail and Billing Period datasets add, and a month-end routine for controllers.