Commitment, Spot and Licence Discount Recommendations
Four financially different levers, four different headlines, and a break-even gate before any commitment is suggested.
The discount category is about paying less for usage you will keep running, rather than running less of it. It spans four mechanisms, and ZopNight titles each one differently because they are financially distinct decisions:
- Commitment: “Purchase a reservation for …”, covering Reserved Instances, Savings Plans, reserved capacity and committed use discounts.
- Spot: “Move … to Spot capacity”, for workloads that tolerate interruption.
- Hybrid: “Apply Hybrid Benefit to …”, when an owned Windows licence could be applied on Azure.
- Migration: moving capacity off an existing reservation to Spot.
Commitments are advisory and priced honestly
Commitment recommendations fire only on sustained on-demand workloads, and they are advisory: ZopNight shows the option, you make the purchase. Each one offers a separate option for every 1-year or 3-year No-Upfront term the provider’s public pricing feed prices, each from its own live rate. Because a No-Upfront commitment bills every hour of its term, the saving is computed against measured uptime, never an assumed always-on box. If uptime is unknown the saving is shown as unknown, and a break-even gate suppresses the suggestion when the running cost does not clear the committed cost by a margin. Resources already covered by a reservation or savings plan do not re-fire.
Spot is gated on tolerance
Spot recommendations carry vetoes that matter more than the discount. VM Spot rules skip names that mark disaster-recovery or standby roles, and skip production by environment tag. The GCP Spot VM rule also skips Windows VMs. ECS Fargate Spot Opportunity for Dev/Test requires at least two tasks behind a load balancer, so a reclaimed task never leaves a service with nothing serving. Kubernetes node pools are treated as structurally safer, because the cluster autoscaler reschedules preempted pods.
Examples per cloud
- AWS: EC2 Reserved Instance Opportunity, EC2 Compute Savings Plan Opportunity, ElastiCache Reserved Node Opportunity, EMR Spot Task Nodes Opportunity. See AWS discounts.
- GCP: GCP Prod VM Without Committed Use Discount, GCP Cloud SQL Committed Use Discount Opportunity, GKE Spot Node Pool Opportunity. See GCP discounts.
- Azure: Azure Reserved VM Opportunity, Azure Hybrid Benefit Opportunity, Azure Redis Cache Could Use Reserved Capacity. See Azure discounts.
Background on the mechanisms: reserved instances, savings plans, committed use discounts and Spot instances.
Every commitment discount check ZopNight runs has its own page, with the reason it fires and the fix: see the commitment discount checks in the ZopNight rule catalogue.
Questions we get a lot.
Can ZopNight buy a reservation for me?
No. Commitment recommendations are advisory. ZopNight prices the available 1-year and 3-year options and shows the evidence; the purchase is yours.
Why is the saving on a commitment marked unknown?
The saving depends on how many hours the resource actually runs. When measured uptime is not available, ZopNight reports the saving as unknown rather than assuming the resource runs all month.