Billing Mode | First Hour (Running 30 Instances) | Second Hour (Running 20 Instances) | Third Hour (Running 10 Instances) |
Total regular pay-as-you-go price without any SP | Total amount = 0.4 x 0.8 x 30 = 9.6 USD | Total amount = 0.4 x 0.8 x 20 = 6.4 USD | Total amount = 0.4 x 0.8 x 10 = 3.2 USD |
Total price with a savings plan applied | 0.4 x 0.5 x 30 = 6 USD > Hourly commitment of 4 USD The hourly commitment can offset up to 20 instances (4/0.4/0.5) For extra 10 instances, extras fees to be paid are calculated as follows: Regular pay-as-you-go unit price x Customer discount = 0.4 x 0.8 x 10 = 3.2 USD The total amount for partial offset is 4 USD + 3.2 USD = 7.2 USD | 0.4 x 0.5 x 20 = 4 USD (hourly commitment) The total amount for full offset is 4 USD | 0.4 x 0.5 x 10 = 2 USD < Hourly commitment of 4 USD The total amount for full offset, without refund for overpayments is 4 USD |
Business Scenario | Diagram | Suggested Billing Mode |
Stable business | | A savings plan is used for pay-as-you-go instances. In stable business scenarios, all resources are managed as needed, without the need for batch maintenance. You can adjust resources and calculate budgets at any time, without the need for capacity estimation. |
Hybrid business | | A savings plan is used for pay-as-you-go instances. In hybrid business scenarios, all resources are managed as needed, without the need for batch maintenance. You can adjust resources and calculate budgets at any time, without the need for capacity estimation. |
Flexible configuration | | A savings plan is used for pay-as-you-go instances. In flexible configuration scenarios, the complex monthly subscription can be converted to the billing mode for pay-as-you-go instances with SP applied. The unlimited specification feature of a savings plan will ease resource management. |
Continuous growth | | A savings plan is used for pay-as-you-go instances. In continuous growth scenarios, SP packages can be continuously stacked to support business expansion. |
All Upfront | Partial Upfront | Zero Upfront |
Make a one-time payment for N years to offset the pay-as-you-go bills. Total cost supported = Hourly commitment x 24 x 365 x Number of years Supported upfront cost = Total cost Supported hourly cost = 0 USD | Pay 50% of the total cost for N-year upfront. From the next full hour after successful payment, 50% of the hourly commitment will be offset by hour, until the SP expires. Total cost supported = Hourly commitment x 24 x 365 x Number of years Supported upfront cost = Total cost x 50% Supported hourly cost = Hourly commitment x 50% | Offsets start from the next full hour after the savings plan service is successfully activated (the committed amount per hour) until the savings plan expires. Total cost supported = Hourly commitment x 24 x 365 x Number of years Supported upfront cost = 0 USD Supported hourly cost = Hourly commitment |
Comparison Item | All-Product Plan | Single-Product Plan |
Use across products | Support for cross-product offset Support for no limit on the model, instance size, and operating system | Limit on specific products and product combinations Support for no limit on the instance size and operating system For example, Cloud Virtual Machine (CVM) supports product bundles and single products; Product bundle: CVM standard bundle. The large offset range supports some standard models. However, the SP actually supports offset for computing resources of fixed models, including the CPU, memory, and GPU but not the network and disk. Single product: The SP supports offset of the above computing resources within standard model S1, excluding the network and disk. |
Region limit | Support for cross-region offset | Limit on single regions but not availability zones |
Offset rules | Generally higher offset coefficient | The offset coefficient is generally lower than that of the general type. |
Item | Description |
Quantity for each account | You can purchase up to 40 SPs for each UIN. Supported internal accounts can purchase SPs only of types 4, 6, and 9, while other types of internal accounts cannot purchase SPs. |
Order of application when multiple discount plans coexist | When multiple discount plans are effective at the same time, they are applied in the following order: Reserved instances (RIs) (quantity offset first) SPs (amount offset next) Vouchers, coupons, and then cash |
Whether SPs can be used with other discount modes | SPs cannot be concurrently used with billing-level discount plans (official website, user, and promotional discount plans) for pay-as-you-go instances. To use more favorable user discount plans for SP bundles, you need to contact business personnel for a quotation. SPs cannot be simultaneously used with finance-level discount plans. If a finance-level discount plan is available, you cannot purchase any SPs, and vice versa. |
Limit on offset for pay-as-you-go instances | SPs can be used only for pay-as-you-go instances billed hourly (excluding preemptible instances and instances billed daily or monthly). |
Cross-account usage scenario | Cross-account offset for SP bundles is not supported. |
Was this page helpful?