Cloud Repatriation
Cloud repatriation is the migration of workloads off public cloud providers onto owned or colocated hardware. The economics favor stable, well-understood workloads at material spend levels, operated by teams with real infrastructure capability. The best-documented mid-sized case, 37signals, cut a $3.2M annual cloud bill to a fraction after buying its own hardware - with self-reported figures and preconditions (stable workloads, strong ops team) that transfer to few companies unexamined.
Buyers rarely search for “repatriation” - they say “our AWS bill is too high” and “back to on-prem.” The analyst term matters mainly when someone needs validation data to take an exit case to leadership.
The honest decision is a fork: optimize in-cloud (often the right first move) versus exit for the workloads that pass a stability-and-spend screen with operations staffing priced in.
Related terms
- Data Egress Fees — Charges for moving data out of a cloud provider - a named villain of cloud bills and a structural component of vendor lock-in.
- Total Cost of Ownership (TCO) — The full multi-year cost of owning a system - build, run, maintain, staff, and risk - as opposed to the purchase or build price alone.
- Vendor Lock-In — The condition where leaving a software vendor is prohibitively expensive because of data, integrations, contract terms, or accumulated dependency.
Where this gets applied
- Unit Economics — CAC payback, NRR, gross margin by segment, cohort analysis, paid-on-bookings vs. paid-on-cash.
- Migration & Integration — Post-merger integrations that hold customer and staff retention. 95% / 100% achieved on complex divestitures.