One report, refracted into color. An Emerging Markets view of global cloud, grounded in primary telemetry from 25 production accounts across 13 enterprises in India, Southeast Asia, the Middle East, and Latin America.
This edition is refracted into color zones. Blue is infrastructure. Orange is spend. Green is outcomes. Scroll and the reading environment retints to tell you where you are.
The 16.9% number, the three personas, and the action gap. Chapters 3 to 5.
Resource sprawl, footprint as a choice, and why the fix is human, not technical.
10 of 10 hypotheses confirmed, and where $1 in every $6 of cloud spend is hiding.
After fifteen years of migration the question is no longer whether to be on the cloud. It is why the bill is what it is, and what it could be if we treated it like a product.
16.9% of every cloud dollar is recoverable, and 87% of those items are forgotten resources, not bad architecture.
Teams identify waste roughly 30 times faster than they fix it. The bottleneck is execution, not awareness.
Optimizers cut spend 50% in 9 weeks. Drifters inflate 10% a quarter. Scalers grow 4x and bake in waste.
Currency exposure, sovereign cloud, and labor economics shape decisions US-centric reports miss.
AI spend is under 2% today. By Q2 2027 it crosses 15%. Same anti-patterns, three more zeros.
Of every cloud dollar, provable without architectural change.
Ten falsifiable hypotheses, written before a single dashboard opened.
Across 25,225 live resources and 32 active cloud regions.
Three views: spend, footprint, and trajectory. AWS still takes two-thirds of every cloud dollar, genuine multi-cloud is 1 in 13, and footprint is now a choice most enterprises never made consciously.
Account count and spend are not the same shape. Azure commands disproportionate enterprise spend on far fewer accounts. GCP is the long tail.
Exactly one enterprise in thirteen ran production across all three hyperscalers. The rest are single-cloud: 6 AWS, 4 Azure, 2 GCP.
One firm spread across 32 regions at ~$60 each. Another concentrated in 3 at ~$5,900 each. Two patterns are deliberate. Two are accident.
One customer halves spend while another quadruples it, in the same quarter. Every bill sits on one of three trajectories.
FinOps embedded in engineering. Recommendations get triaged, owners assigned, savings tracked. No migration. No rebuild. Pure hygiene.
Tooling in place, nobody owns the output. Cost grows quietly 5 to 10% a quarter from accumulated unfixed waste. The default state of enterprise cloud.
Each new team gets its own workspace, region, NAT gateway, snapshot policy. The growth is legitimate. The waste embedded in it is not.
Which trajectory are we on, and is it the one we chose?
87% of cloud waste is not strategic. It is forgotten. The biggest cloud waste problem is not that you bought the wrong thing. It is that you forgot to delete the right thing.
Vendor narratives focus on Reserved Instances, Savings Plans, Spot. Those are 6% of the recommendations we flagged. The real waste is things nobody remembers creating.
Unattached volumes, orphan snapshots, abandoned IPs. About 5 minutes each to fix.
Every dev creates a snapshot before risky changes. Almost no one deletes them.
Fix only the top ten anti-patterns and you recover four-fifths of the waste.
None of these are strategic decisions to revisit. They are hygiene to install. If your platform team cannot recite this list from memory, you have a 16.9% problem.
EBS snapshots with no source volume, charged forever. Found in 100% of AWS users.
Premium SSD in non-prod Databricks on Azure. 100% of Databricks-on-Azure environments.
EC2 not covered by a Savings Plan. Roughly 90% of production fleets.
Dev and test workloads running 24/7 by default. 100% of dev environments.
Single volumes leak ~$2,500 a year. Found in 100% of AWS users.
You did not buy the wrong thing. You forgot to delete the right thing.
Detection has been solved. Execution has not. Teams identify waste roughly 30 times faster than they act on it. The industry spent a decade building detection tools. Action is still an open problem.
Fewer than 1% of detected waste signals are formally applied through a remediation workflow. The work happens, or does not, in the cloud console.
Of detected waste, applied through a remediation workflow.
Not intent. Resources disappear because owners leave, not because anyone acted.
The market for FinOps that detects is mature. The market that acts is wide open.
The Optimizer in our cohort had the same tools as everyone else. Their secret was that someone owned the list, every day, and worked through it.
The account belongs to platform. The workload belongs to the app team. The cost belongs to finance. Nobody owns the recommendation.
Deleting a snapshot might break something, a visible, personal risk. Not deleting it costs money, a diffuse one. The first wins.
Most FinOps platforms show recommendations. Almost none execute them safely, including, by our own count, ours.
One Optimizer proved it takes weeks, not tools. They cut daily cloud spend from $1,565 to $786 in 69 days. No migration. No rebuild. Someone simply owned the list and worked through it, one recommendation at a time.
The market for FinOps that detects is mature. The market that acts is wide open.
Five numbers carry the argument. The conventional wisdom is right. What is missing is the will to act on it.
hypotheses confirmed. All ten, written before a single dashboard opened, held against the evidence.
recoverable waste. The proven floor. The true figure is likely 30 to 40% of cloud spend.
of spend on AWS. Genuine multi-cloud is 1 in 13. Footprint is mostly accidental.
of detected waste is formally remediated. Detection is solved. Action is the open decade.
The most important thing you can do with this report is contest it. We published the full methodology so you can replicate, challenge, and improve on it. Grounded in telemetry from 25 accounts across 13 firms in India, SEA, the Middle East, and LatAm. Published June 2026.