Cloud repatriation has become an increasingly common talking point as organisations scrutinise infrastructure spending. The economics are real, but they are highly workload-specific.
Where cloud gets expensive
Persistent high-volume workloads, data transfer and poorly controlled consumption can produce surprising bills.
What on-premises comparisons miss
Hardware depreciation is only part of the cost. Teams also need to account for facilities, operations, resilience and capacity planning.
A portfolio decision
The most practical answer is often neither cloud-first nor repatriation-first, but placing each workload where its economics and operational requirements make sense.
