.png)
You already know cloud compute costs money. What you may not realize is how much you are overpaying simply by not committing to it in advance. Cloud providers charge a penalty for paying by the hour with no commitment — it is called the on-demand rate. A Compute Savings Plan is how you eliminate that penalty.
It is not complicated. You tell the cloud provider: I will spend at least $X per hour on compute for the next year (or three years). In return, they slash your compute rates. The discount is automatic. You do not pick which instances benefit — the provider applies the savings to your existing usage, starting with the combination that gives you the highest discount. You just pay less.
Also read: AWS Savings Plan: A Complete Guide
How Does a Compute Savings Plan Work?
The mechanics are the same on both AWS and Azure. You commit to a dollar-per-hour floor. The provider applies discounted rates to your actual compute usage up to that floor. Usage above the floor bills at normal on-demand rates. Unused commitment below the floor is charged anyway — every hour, no rollover.
Here is a simple example. You commit to $4.00 per hour. In a given hour, you run compute worth $6.00 at on-demand rates. With the Savings Plan, the first $4.00 worth of usage is discounted (you might pay $2.00-2.50 for it at the discounted rate). The remaining $2.00 bills at standard on-demand. That hour costs you roughly $4.00-4.50 instead of $6.00.
Now imagine you have a quiet hour and only run $2.00 worth of compute. You still pay $4.00 — your full commitment. The $2.00 you did not use is charged and gone. This is why sizing the commitment correctly matters: commit to what you reliably spend, not to your peak.
The right commitment level is your stable hourly compute baseline — roughly the P70 to P80 of your hourly spend over the last 30 days. Committing to your peak wastes money in quiet periods. Committing too low leaves savings uncaptured.
What Does a Compute Savings Plan Cover?
Coverage differs between AWS and Azure. Here is exactly what each includes.
AWS Compute Savings Plan Coverage
EC2: all instance families (M, C, R, T, G, and more), all regions, all operating systems. This is the key advantage over EC2 Instance Savings Plans — no family lock. If you migrate from Intel M5 to Graviton M7g during your term, the savings plan follows.
Fargate: compute charges for ECS and EKS tasks. Savings of up to approximately 52% on 3-year terms.
Lambda: duration charges (GB-seconds) only. Requests are not covered. Savings of approximately 17%.
Not covered: RDS, ElastiCache, DynamoDB, and all other database and analytics services. Those require separate Reserved Instance products.
Azure Savings Plan for Compute Coverage
All Azure VMs across all series and regions. AKS node pool VMs. Azure Virtual Desktop. Azure Databricks compute. Container Instances. Dedicated Host. App Service Premium v3 and Isolated v2. Azure Functions Premium plan.
Not covered: Azure SQL Database, Cosmos DB, Redis Cache, and PostgreSQL/MySQL databases. Those use Azure Reserved Capacity.
Who Should Use a Compute Savings Plan?
Almost every team running production workloads on AWS or Azure for more than a few months benefits from a Compute Savings Plan. But three types of team benefit most.
Teams with mixed compute workloads: if you run a combination of EC2 servers, containerized services on Fargate or AKS, and event-driven Lambda or Azure Functions, a single Compute Savings Plan covers all of it. Managing separate Reserved Instances per service adds complexity without proportionally better savings.
Teams whose architecture evolves frequently: migrating instance families, switching regions, moving workloads between EC2 and containers. A Compute Savings Plan keeps applying through all of it. A Reserved Instance stops applying the moment the configuration changes.
Teams just starting with cloud commitments: the flexibility of a Compute Savings Plan with a 1-year No Upfront term means you can start saving immediately with zero upfront cost and no configuration lock-in. It is the lowest-friction entry point into commitment-based discounts.
Compute Savings Plan vs Reserved Instance: The Key Difference
Both save money on cloud compute. The difference is how they do it.
A Reserved Instance is locked to a specific configuration: this instance type, this region, this operating system. If anything changes, the reservation may not apply — and you keep paying for it. It offers a slightly higher maximum discount (up to 72% on AWS) precisely because it accepts that configuration lock.
A Compute Savings Plan is locked only to a dollar amount. Your instances can change completely and the savings keep flowing. The maximum discount is slightly lower (up to 66% on AWS) in exchange for that flexibility.
For most teams — especially those whose cloud architecture is still evolving — the flexibility of a Compute Savings Plan is worth that 6-percentage-point gap. For teams with a completely stable, well-defined EC2 fleet that will not change for three years, Reserved Instances capture slightly more savings.
Deep comparison: Compute Savings Plan vs Reserved Instances
How Much Can You Save with a Compute Savings Plan?
On AWS, up to 66% savings on EC2 and Fargate compute with a 3-year All Upfront plan. A 1-year No Upfront plan saves approximately 30-42% depending on instance type and region.
On Azure, up to 65% savings on VM compute with a 3-year plan. A 1-year plan saves approximately 11-37% on most VM series.
Actual savings depend on which instances are running, which region they are in, and which operating system they run. Verify current rates at aws.amazon.com/savingsplans/compute-pricing for AWS and azure.microsoft.com/pricing/offers/savings-plan-compute for Azure — rates change frequently.
Here is a grounded example. An AWS c5.xlarge running Linux in US East costs $0.170/hr on-demand. With a 3-year All Upfront Compute Savings Plan, the effective rate drops to approximately $0.068/hr — a 60% reduction. Running that instance 24/7 for a year saves approximately $890 versus on-demand. Multiply that across a fleet of 50 similar instances: roughly $44,000 in annual savings from a single commitment decision.
How Do You Buy a Compute Savings Plan?
On AWS: AWS console > Cost Management > Savings Plans > Purchase Savings Plans. Select Compute Savings Plans (not EC2 Instance Savings Plans). Choose 1-year or 3-year term, No Upfront / Partial Upfront / All Upfront payment, and enter your hourly commitment amount. Cost Explorer provides a recommendation — use it as a starting point, but validate it against your own P70-P80 spend calculation. The commitment takes effect at the next full hour.
On Azure: Azure portal > Cost Management + Billing > Savings Plans > Add. Select Azure Savings Plan for Compute. Choose 1-year or 3-year term, enter the hourly commitment, and choose whether it applies to a single subscription or shared across the billing account. Azure does not offer a Partial Upfront option — you choose monthly payments (equivalent to No Upfront) or All Upfront.
One important note for both platforms: once purchased, the commitment cannot be cancelled or modified. The full term runs whether your usage changes or not. If your workload shrinks significantly after purchase, you will pay for unused committed hours. Size the commitment carefully before buying.
Usage.ai Insured Flex Commitments solve the cancellation problem: they carry a buyback guarantee. If a commitment becomes underutilized because your workload changes, Usage.ai buys it back and returns the value as cashback — in real money, not credits. The commitment also adjusts quarterly rather than being fixed for 1-3 years. Verified from Usage.ai project documentation.
See how Usage.ai automates Compute Savings Plan purchasing with zero lock-in risk
Frequently Asked Questions
1. What is a Compute Savings Plan?
A Compute Savings Plan is a 1-year or 3-year commitment to spend a minimum dollar amount per hour on cloud compute. AWS offers discounts of up to 66% on EC2, Fargate, and Lambda. Azure offers discounts of up to 65% on Virtual Machines, AKS workloads, Container Instances, and Azure Functions Premium. The discount applies automatically across all instance families and regions — no specific configuration matching required.
2. Is a Compute Savings Plan worth it?
Yes, for any team running consistent compute workloads. A 1-year No Upfront Compute Savings Plan saves 30-42% on AWS with zero upfront cost. The only scenario where it is not worth it: workloads running for fewer than 6-8 months, or workloads with such variable usage that consistently hitting the committed hourly spend is unreliable. For stable production workloads, it is almost always the right choice.
3. What is the difference between a Compute Savings Plan and a Reserved Instance?
A Reserved Instance locks to a specific instance type, region, and operating system for up to 72% savings. A Compute Savings Plan locks only to a dollar-per-hour spend commitment and applies across all instance families, regions, and operating systems for up to 66% savings. Choose Compute Savings Plans for flexibility; Reserved Instances for maximum savings on a completely stable, specific configuration.
4. Can I cancel a Compute Savings Plan?
No. AWS Compute Savings Plans and Azure Savings Plans for Compute cannot be cancelled or modified after purchase. The full term runs. If your usage drops below the commitment, you pay for unused committed hours. This is why sizing commitments conservatively (at P70-P80 of your hourly baseline, not your peak) matters before you buy.
5. What does an AWS Compute Savings Plan not cover?
AWS Compute Savings Plans do not cover database services: RDS, ElastiCache, DynamoDB, OpenSearch, or Redshift. Those require separate Reserved Instance products. Lambda request charges (only duration/GB-seconds are covered). EBS storage, data transfer, and S3 are not covered by any Savings Plan — those are billed independently.
6. How is a Compute Savings Plan different from an EC2 Instance Savings Plan?
An EC2 Instance Savings Plan is locked to one EC2 instance family in one region but offers up to 72% savings — slightly more than Compute Savings Plans. Compute Savings Plans cover all EC2 families and regions, plus Fargate and Lambda, at up to 66%. Choose EC2 Instance Savings Plans when you have a stable, specific EC2 fleet; choose Compute Savings Plans for flexibility and multi-service coverage.
