Community guidelines
Be specific and constructive. No vendor spam — promoting your own product belongs in a listing. Anyone can read; posting needs a free account.
our steady workloads cost far more in cloud than the original estimate, mostly RDS instances, egress and an always on EKS cluster we never scale down. Leadership now wants to move everything back on premises. Has anyone done the math honestly, including staff, hardware refresh and disaster recovery?
we moved a predictable batch platform back to a colo and saved money. We didn't move the whole company. The workload ran 24 by 7, needed little elasticity and transferred a lot of data. That's almost the perfect repatriation candidate
First clean up the cloud waste. We found idle environments, oversized databases and data crossing zones for no reason. After that, only two services still made sense to move. A bad cloud bill does not automatically mean hardware is the answer.
we definitely have waste, but the board already heard the word repatriation. i'm worried this turns into a political target rather than a workload decision
make a per workload scorecard. Utilization, growth, latency, data transfer, compliance, recovery and team skills. Put a five year number next to each option. You may end up hybrid, which is less exciting in a meeting but usually closer to reality