What is your cloud estate actually costing you?
Six inputs, an itemized saving estimate with the reasoning behind each lever. Conservative by design — every rate is the low end of published FinOps benchmarks.
Your estate
VMs, node pools, managed instances — as opposed to storage, data transfer and PaaS.
Dev, test and staging environments.
Reserved Instances or Savings Plans already in place.
- Non-production schedulinglow effort$142,560/yr
Stopping dev, test and staging outside working hours removes roughly 60% of their compute cost. Automated with a start/stop schedule and an opt-out tag.
- Rightsizingmedium effort$118,800/yr
Matching instance families and sizes to observed utilization typically recovers 15% of compute spend. Requires utilization history, so it follows monitoring.
- Commitment coveragelow effort$106,445/yr
Reserved Instances and Savings Plans discount steady-state production compute by around 30% against on-demand. Modeled at 80% coverage of the uncommitted production baseline.
- Orphaned resourceslow effort$43,200/yr
Unattached disks, idle load balancers, reserved IPs and stale snapshots accumulate at roughly 3% of spend where nothing sweeps for them.
- Cost attributionmedium effort$28,800/yr
Enforced tagging does not cut cost directly — it makes every other lever stick by giving each resource an accountable owner. Modeled as a 2% second-order effect.
Indicative only. Figures come from published FinOps benchmark ranges applied to the inputs above, deliberately taken at the conservative end. They are not a quotation and not a guarantee — a real assessment reads your actual billing and utilization data.
Get a real assessment