The Hotel Analogy
Imagine living in a hotel.
- Short term: It's excellent. Room service, daily cleaning, no maintenance headaches. If you need to leave tomorrow, you just check out — no lease, no penalty.
- Long term: If you live there for five years, you will pay ten times the cost of a mortgage, and at the end you own nothing.
Public cloud is a hotel. You pay a significant premium for the ability to scale up or walk away at any moment. On-premises hardware is a house. You pay a down payment (CapEx), but your monthly costs (OpEx) are low, stable, and predictable — and at the end of the depreciation cycle, you still have the asset.
The Steady-State Premium
The math becomes stark when you look at a specific, concrete workload. Consider a database server that runs at consistent utilization — 64 vCPUs and 256 GB RAM — every hour of every day for three years.
| Cost Category | Cloud (3-Year Reserved) | On-Prem Hardware Purchase |
|---|---|---|
| Total Cost | ~$50,000 | ~$15,000 |
| Monthly Cost | ~$1,389 | ~$417 |
| Ownership at End | None | You own the server |
The Repatriation Dividend: The $35,000 difference per server is pure margin recovered. At scale — say, 50 such servers — that is $1.75 million returned to the business over three years.
The break-even point (where buying becomes cheaper than renting) typically occurs between 12 and 24 months for steady-state workloads. Beyond that point, every month is savings.
Interviewers at senior levels often ask: "When would you not repatriate, even if the math looks favorable?" The correct answer addresses hidden costs: the engineering labor to manage hardware, the loss of managed services (RDS automated backups, auto-scaling), the risk of hardware failure without a cloud fallback, and the opportunity cost of engineers doing rack-and-stack instead of product work. A strong candidate acknowledges that the TCO (Total Cost of Ownership) calculation must include all costs, not just the server invoice.