Cloud Repatriation: Not a Trend, a Business Decision
Between 2020 and 2023, Indian enterprises moved workloads to cloud at unprecedented speed. By 2025–2026, a significant number are moving some of those workloads back. This is not a failure of cloud — it is a sign that enterprises have matured in their understanding of where cloud delivers value and where it does not.
Why Indian Companies Are Repatriating Workloads
Reason 1: Cost at Scale
Cloud cost predictions rarely match actual bills at scale. An Indian mid-market company running 50 servers' worth of EC2 instances in AWS Mumbai pays ₹20–₹40 lakh/month. The equivalent certified refurbished hardware from Serverwale costs ₹50–₹80 lakh one-time — with payback in under 3 months and savings of ₹2+ crore over 3 years.
Reason 2: DPDP Act and Data Sovereignty
India's DPDP Act 2023 has created uncertainty about cross-border data flows. Companies processing sensitive personal data — banks, healthcare providers, HR platforms — are choosing on-premise infrastructure to have unambiguous control over data location and access.
Reason 3: Predictable Workloads Don't Need Cloud Flexibility
Cloud's value proposition is elasticity. If your database server runs at 70% utilisation 24/7/365, you are paying the cloud premium for elasticity you never use. These workloads are prime candidates for owned infrastructure.
Reason 4: Latency for India-First Applications
AWS Mumbai region adds 15–25ms to requests compared to a server in a Delhi colocation facility. For real-time applications (gaming, trading, live video), this is significant. Private infrastructure in Indian data centers wins on latency.
What Gets Repatriated vs What Stays in Cloud
| Repatriate (On-Premise) | Keep in Cloud |
|---|---|
| Production databases (predictable load) | Dev/test environments |
| AI/ML training (GPU workloads) | Global CDN (CloudFront, etc.) |
| ERP and core business systems | Email and collaboration |
| Data warehouse (large, static data) | Burst compute capacity |
| Video storage and processing | Managed databases (RDS) |
How to Execute a Cloud Repatriation
- Workload audit: Identify top 5 cloud cost centres. Calculate 3-year TCO of owned hardware equivalent.
- Colocation selection: Choose a Tier 3 Indian colo (Nxtra, CtrlS, Yotta, STT) near your primary user base.
- Hardware procurement: Certified refurbished servers from Serverwale keep CapEx low. Get quotes within 30 minutes.
- Migration planning: Use a "strangler pattern" — run old and new in parallel, migrate traffic gradually.
- Connectivity: 1Gbps dedicated internet from your colo to your office + cloud for burst.
The Result
Indian companies executing well-planned cloud repatriation consistently report 50–70% reduction in infrastructure costs. The "cloud is always cheaper" assumption is not universally true — and Indian enterprises are acting on that realisation.