The Cloud Repatriation Myth That Enterprise IT Keeps Getting Wrong

Episode 17 of The Cloud Business Podcast tackles the cloud repatriation narrative head-on. Lucas and Luna dig into a recent survey of 500 enterprise IT leaders at companies with over $1 billion in revenue. The headline: 38 percent reported moving some workloads off public cloud in the past 12 months. But the real story is what they moved and why. The hosts unpack the difference between repatriation and rebalancing, looking at the specific workloads that actually leave — almost always predictable, steady-state compute in regions with high egress costs. They contrast that with the workloads staying put: burst, AI inference, and anything with variable demand. The conversation centres on a case study from a Fortune 500 retailer that moved its inventory forecasting batch jobs off AWS to an in-house colo, only to discover the three-year total cost of ownership was nearly identical once they accounted for staffing and hardware refresh. Lucas argues that the 'cloud repatriation' framing is a distraction from the harder question: how to systematically decide what belongs where. Luna pushes back with data on the hidden costs of running your own metal. The episode closes with a forward look at the next frontier: whether the hyperscalers' custom silicon and tighter software stacks will eventually make on-premise compute irrelevant for all but the most latency-sensitive or regulated workloads. #CloudRepatriation #EnterpriseInfrastructure #AWS #Azure #GCP #HybridCloud #FinOps #CloudEconomics #TotalCostOfOwnership #DataCenter #Colocation #InventoryForecasting #BatchCompute #SteadyStateWorkloads #AIInference #EgressFees #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo