Cloud & DevOps · 7 min read
Your cloud bill is 30–40% too high. Here's where it hides.
After auditing dozens of AWS and Azure environments, the waste is always in the same five places. None of them require re-architecture to fix.
Every cloud cost review we run starts with the customer saying some version of "we think it is mostly optimized." It almost never is. Across the last few dozen environments we have audited, the median saving was 31% — without re-architecting anything, without performance loss, and usually within the first quarter.
1. Compute that is sized for a day that never comes
The biggest line item is almost always over-provisioned compute: instances sized for a traffic estimate from two years ago, or for a peak that autoscaling should be handling instead. Right-sizing based on actual 95th-percentile utilization — not on what feels safe — typically recovers 10–15% of the total bill on its own.
2. Non-production environments running 24/7
Staging, QA, and dev environments doing nothing at 3 a.m. on a Sunday are pure waste. Scheduling them to match working hours is an afternoon of work and routinely cuts their cost by 60–70%. We find full-size production replicas idling overnight in more than half of the audits we run.
3. Storage nobody has looked at since launch
Orphaned volumes from terminated instances, snapshots with no retention policy, and logs kept forever in hot storage. Storage is individually cheap, which is exactly why it accumulates unexamined until it is 20% of the bill. Lifecycle policies fix this permanently, not just once.
4. Paying on-demand prices for predictable workloads
If a workload has run every day for a year, it should not be billed at on-demand rates. Reserved instances and savings plans are unglamorous and reliably worth 30–40% on the workloads they cover. The hesitation is always commitment fear — solved by covering only your provable baseline, not your hopes.
5. Data transfer surprises
Cross-AZ chatter between services that could be co-located, traffic leaving the cloud that a CDN should absorb, and NAT gateway charges that nobody attributes until they audit. Transfer costs are architectural, so they hide in everyone else's line items.
What to actually do
You do not need a FinOps platform subscription to start. Pull 90 days of billing data, sort by service, and ask "what is this and who owns it" for the top ten lines. If nobody can answer in a sentence, that line is a candidate. Or have someone like us do it — our cost reviews pay for themselves in the first month or we say so up front.
About Axiora Trust
We are a 40-person engineering partner covering custom software, cloud, security, and managed operations. Articles like this one come out of real client work — the case studies have the receipts.