How It Works
Cloud providers like AWS, Azure, and GCP offer discounted pricing in exchange for a usage commitment over a fixed period. That period is the commitment term. Most providers offer 1-year and 3-year options. Longer terms typically unlock deeper discounts but require the customer to accurately forecast usage over a longer horizon. On AWS, this applies to Reserved Instances and Savings Plans. Azure uses the same structure for Reservations and Azure Savings Plans. GCP applies it to Committed Use Discounts (CUDs). The discount rate the customer receives depends directly on which term they select at the time of purchase.
Why It Matters for Cloud Cost
Choosing the wrong term length is one of the most common sources of cloud waste. A 3-year commitment made during a period of high usage can become a liability if the team migrates services, scales down, or changes instance types. Conversely, staying on 1-year terms when usage is stable means leaving additional savings on the table year after year. The core tension is between maximizing discount depth and preserving flexibility. Without a deliberate term length strategy, finance teams often default to either excessive caution (always 1-year) or excessive risk (3-year commitments based on optimistic forecasts), neither of which produces optimal outcomes.
Usage.ai is a multicloud cost optimization platform for AWS, Microsoft Azure and Google Cloud. Its proprietary algorithm evaluates eligible usage and existing coverage, then manages eligible purchases and renewals in your cloud accounts within your approved controls. Your organization owns the commitments; provider terms and payment obligations continue to apply.
Eligibility for commitment term length depends on the selected provider instrument and current supported offer. Analysis runs daily; a purchase depends on sustained eligible demand and your approved controls. Review recommendations in Copilot or authorize Autopilot to execute eligible purchases. A read-only assessment does not authorize purchasing, and daily analysis does not mean a commitment is purchased or changed every day.
Eligible Flex Commitments may receive Cashback for qualifying losses assessed against the On-Demand cost of the same covered usage. Eligibility, exclusions, notice, credits or offsets, payout timing and service-exit treatment follow the applicable agreement. Partial underutilization alone does not guarantee reimbursement. Provider commitment charges are separate from Usage.ai’s service fee, and ending managed service does not cancel the underlying commitment.
The selected provider instrument determines commitment duration, payment options and continuing charges. These are separate from Usage.ai’s service fee and the applicable protection agreement. Review the quoted instrument and supported offer before approving a purchase. Ending managed service does not cancel the native commitment or create an automatic refund; review its effect on protection and accrued but unpaid amounts.
Explore cost optimization across AWS, Microsoft Azure and Google Cloud.
Related guidance: Usage Flex Savings Plan
Current Flex Commitment Program: August 16, 2024
Cashback follows the 2024 Flex Commitment Program. Qualifying Non-Usage Rebates are assessed monthly against the then-current On-Demand cost for the same applicable resource and month. They are provided 90 days after the calendar month in which they accrued, first as credits against the fees specified in section 6.1, including unpaid past/current fees and fees owed 90 days following the credit date. Any remainder is refunded.
Section 3 requires direct UsageAI purchase and eligibility designation at purchase, full provider payment, at least one month of remaining term, and its 30-day active-resource condition before a Purchaser purchases the unused capacity. This is not a universal 30-day-underutilization trigger. Advance-notice requirements, disqualifying activities, continued Agreement compliance and the exclusions in sections 4โ6.2 also apply.
Termination of the Agreement ends participation and eligibility for any Non-Usage Rebates, including underutilization that occurred during the Term (section 7). Ending management does not itself cancel native cloud commitments or remove provider payment obligations. The preamble’s qualifying prior-agreement provision remains. Read the full August 16, 2024 terms (PDF).