Commitments

Each cloud sells discounted capacity in exchange for a term commitment. CCO pulls them from the provider APIs and normalizes them into a single view, so you can see across clouds what you've committed to and how well it's being used.

For every commitment CCO surfaces the two numbers that matter for a FinOps review:

• ✓Coverage — how much of your eligible on-demand usage is covered by a commitment (the gap is what you could still commit)
• ✓Utilization — how much of what you already committed to is actually being used (the gap is money already spent but wasted)
• ✓Term details — start and end dates, scope, and the resource family each commitment applies to

A commitment that lapses silently means a sudden jump back to on-demand pricing. CCO watches for two conditions and can notify you:

• ✓Expiring soon — a commitment ending within a configurable window, so you can renew or let it lapse deliberately
• ✓Underutilized — a commitment running below a utilization threshold, so you can right-size the next term

Both are available as notification events in the Alerts & Notifications hub — create a rule to have them emailed, or routed to Slack, Teams, or a webhook.

• ✓Commitments page — the full inventory with coverage and utilization per commitment
• ✓Recommendations — the reserved-instance / savings-plan / committed-use engine suggests new commitments where coverage is low
• ✓Reports — the Commitments report type exports the inventory to PDF or Excel
• ✓Alerts & Notifications — expiring and underutilized commitment events