Commitments and savings
Savings that count only when the bill agrees
UnitVane reads the bill and Kubernetes allocation for savings across commitments, compute, storage, clusters and AI. Each recommendation shows its evidence and how the estimate was made. After your team makes the change, the saving is measured on the bill before it counts as verified.
Commitments
Commit to the floor, never the average
Commitment recommendations cover 80% of the lowest daily on-demand compute of the last 30 days, the 10th percentile, so the commitment stays fully used. Existing Savings Plans, reservations and committed use discounts are checked for utilization, and unused commitment is listed with the workloads that could use it.
- Coverage and utilization from FOCUS commitment columns
- 1-year, no upfront by default
- Unused commitment flagged
Eight kinds of finding
From instance families to model routing
Older instance families with a current-generation equivalent, gp2 volumes that cost about 20% more than gp3, untagged volumes with no owner, idle cluster capacity, Kubernetes requests above the 95th percentile of use, dev compute running nights and weekends, and AI requests that a smaller model can serve through the UnitVane AI gateway.
- Each with evidence, method, confidence and risk
- Accept, mark done or dismiss
- Kubernetes findings link to KubeOn
Why cloud bills need owners
of organizations call managing cloud spend their top cloud challenge
Flexera, State of the Cloud 2025in open savings found at our sample company
Sample company, not a customer result
Verified savings
Estimated, implemented, verified
| State | How it is counted |
|---|---|
| Open | Monthly estimate from the recommendation's method |
| Implemented | Your team marked it done; still an estimate |
| Verified | The resource's cost in the 14 days after the change compared with the 14 days before |
Only verified savings are reported as savings delivered.
Savings with a paper trail
Commitment purchase
Sized to the 10th-percentile floor.
Commitment utilization
Unused commitment matched to workloads.
Rightsizing and storage
Older families and gp2 to gp3.
Schedules
Dev compute stopped outside working hours.
Verified on the bill
14 days before and after each change.
Commitments and savings: your questions answered
UnitVane
Keep exploring
Evaluate commitments and savings with your team
Bring your platform and FinOps priorities. We will walk through the data, controls and evidence for your evaluation.