Cloud Cost Optimizer
Break your cloud bill down by service and see how much rightsizing, commitments, scheduling, and storage tiering can save.
Example scenario—not a forecast or verified benchmark. Enable JavaScript to edit inputs, view charts, save locally and export your analysis.
Example inputs
- Monthly cloud bill by service
- [{"service":"Production app servers","category":"compute","monthly":3200,"utilization":40,"committedPct":0,"alwaysOn":true},{"service":"Dev / test environments","category":"compute","monthly":900,"utilization":20,"committedPct":0,"alwaysOn":false},{"service":"Production database","category":"database","monthly":1900,"utilization":45,"committedPct":0,"alwaysOn":true},{"service":"Object storage & backups","category":"storage","monthly":900,"utilization":0,"committedPct":0,"alwaysOn":true},{"service":"Data transfer / CDN","category":"network","monthly":450,"utilization":0,"committedPct":0,"alwaysOn":true}]
- Target utilization after rightsizing
- 60
- Share of theoretical rightsizing you can capture
- 50
- Discount from 1-year commitments
- 30
- Share of steady usage you are willing to commit
- 70
- Savings from shutting non-production off nights/weekends
- 50
- Savings from storage tiering & cleanup
- 20
Example results
About $30K/yr (33% of a $88K annual cloud bill) is recoverable, led by rightsizing.
- Annual savings
- $29,519
- Share of bill recoverable
- 33.5%
- Optimized monthly bill
- $4,890
- Current monthly bill
- $7,350
- Rightsizing (monthly)
- $921
- Commitments (monthly)
- $909
- Off-hours scheduling (monthly)
- $450
- Storage tiering (monthly)
- $180
What stands out
Rightsizing is the biggest lever: $11K/yr
That is 37% of total identified savings.
Non-production runs 24/7: $5,400/yr wasted
Dev and test environments rarely need to run nights and weekends. Automated start/stop schedules fix this in a day.
33% of your bill is avoidable
That level of waste usually means nobody owns cloud cost. Assign an owner and a monthly review.
Next actions
- Sequence matters: schedule and rightsize first, then buy commitments on the smaller steady baseline so you do not lock in waste.
- Start with "Production app servers" ($13K/yr): it holds the largest single saving.
- Commit no more than 70% of steady usage on 1-year terms, and review coverage quarterly.
- Set budget alerts and a monthly 30-minute cost review with whoever owns the cloud account.
Model assumptions & limitations
- Rightsizing captures 50% of the theoretical saving from scaling capacity to 60% target utilization, allowing for fixed instance sizes and peak loads.
- Commitment discount of 30% is an input; verify against your provider's current pricing for your region and term.
- Off-hours scheduling saves 50% of non-production compute; storage tiering/cleanup saves 20% of storage. Both are rules of thumb.
- Levers are applied in sequence (schedule, rightsize, commit, tier) so savings are not double-counted.