Overview

There are yearly/monthly, pay-per-use, and spot pricing billing modes. Each one has different advantages and disadvantages.

Yearly/Monthly is a prepaid billing. You pay in advance for a subscription term, and in exchange, you get a discounted rate. The longer the subscription period, the higher the discount. Yearly/Monthly billing is a good option for long-term, stable services.
Pay-per-use is a postpaid billing mode. You pay as you go and just pay for what you use. The ECS usage is calculated by the second but billed every hour. This mode allows you to adjust resource usage easily. You do not need to prepare resources in advance, and will not have excessive or insufficient preset resources. Pay-per-use is a good option for scenarios where there are sudden traffic bursts, such as e-commerce promotions.
Spot pricing is a postpaid billing mode. ECS prices are adjusted gradually based on long-term trends in supply and demand for spot instance capacity. The ECS usage is calculated by the second but billed every hour. Spot instances are made available at a discounted rate, but their performance is the same as ECSs billed in other modes. If inventory resources are insufficient or the market price exceeds your expected price, the spot ECS will be reclaimed. Spot pricing applies when you want to drive down cloud costs.
There are spot instances and spot block instances.
- ECSs that use spot pricing are called spot instances.
  You need to set a maximum price you are willing to pay for a spot instance. The maximum price must be greater than or equal to the market price but less than or equal to the pay-per-use price. If inventory resources are insufficient or the market price rises above your maximum price, the spot instance will be reclaimed.
- Spot instances with a predefined duration are called spot block instances.
  When purchasing a spot block instance, you need to set a predefined duration and the number of durations. During the predefined duration, your spot block instance will run continuously and will not be interrupted. If it is terminated by the system, you will not be billed for the resource usage within the predefined duration. If you delete it within the predefined duration, you will be billed based on the usage duration.

Table 1 lists the differences between the billing modes.

**Table 1** Differences between billing modes
Billing Mode	Yearly/Monthly	Pay-per-Use	Spot Pricing (for Spot Instances)	Spot Pricing (for Spot Block Instances)
Payment	Prepaid Billed by the subscription term you purchase	Postpaid Billed by service duration.	Postpaid Billed at the market price, which varies according to the changes in supply and demand. The start price is the market price when the ECS was purchased. The ECS is then billed at the market price every hour.	Postpaid Billed based on the usage duration and predefined duration. After the ECS is released, a new line item is generated on each hour.
Conditions for Purchase	N/A	N/A	You need to set a maximum price you are willing to pay for a spot instance. If your maximum price is greater than or equal to the market price and the inventory resources are sufficient, you will be provisioned with a spot instance. This spot instance will be billed at the current market price. If your maximum price is less than the market price, you will not be provisioned with a spot instance.	You need to set a predefined duration and the number of durations. Prices vary depending on the predefined duration.
Billing Method	Billed by the subscription term you purchase	Calculated by the second but billed every hour	Calculated by the second but billed every hour	Calculated by the second but billed every hour
Billed Items	Compute resources (vCPUs and memory), images, EVS disks, and EIPs	Compute resources (vCPUs and memory), images, EVS disks, and EIPs	Compute resources (including vCPUs and memory)	Compute resources (including vCPUs and memory)
Billing for Stopped ECSs	Stopping an ECS has no impact on the billing of a yearly/monthly ECS. ECSs are billed based on the subscription term you purchase.	After a common ECS is stopped, basic resources (vCPUs, memory, image, and GPUs) will not be billed. Other resources (EVS disks, EIPs, and bandwidth) associated with the ECS instance will continue to be billed. After a special ECS instance is stopped, its resources will be retained and continue to be billed. NOTE: Common instances include: Non-bare-metal instances Instances without local disks Instances without FPGA cards Special instances include: Bare metal instances ECSs attached with local disks, such as disk-intensive ECSs and ultra-high I/O ECSs ECSs with FPGA cards	After a common ECS is stopped, basic resources (vCPUs, memory, image, and GPUs) will not be billed. Other resources (EVS disks, EIPs, and bandwidth) associated with the ECS instance will continue to be billed. After a special ECS instance is stopped, its resources will be retained and continue to be billed. NOTE: Common instances include: Non-bare-metal instances Instances without local disks Instances without FPGA cards Special instances include: Bare metal instances ECSs attached with local disks, such as disk-intensive ECSs and ultra-high I/O ECSs ECSs with FPGA cards	The ECS will continue to be billed after it is stopped. To stop the ECS from being billed, delete it and its associated resources.
Changing the Billing Mode	Yearly/Monthly can be changed to pay-per-use. For details, see Yearly/Monthly to Pay-per-Use.	Pay-per-use can be changed to yearly/monthly. For details, see Pay-per-Use to Yearly/Monthly.	Spot pricing cannot be changed to pay-per-use or yearly/monthly.	Spot pricing cannot be changed to pay-per-use or yearly/monthly.
Changing the Specifications	Supported	Supported	Not supported	Not supported
System Disk Detachment	Supported	Supported	Not supported	Not supported
Conditions for Reclaiming	N/A	N/A	The market price is higher than the maximum price you are willing to pay. The inventory resources are insufficient. You release the ECS instances voluntarily.	The inventory resources are insufficient. You release the ECS instances voluntarily.
Application Scenarios	A cost-effective option for scenarios where the resource usage duration is predictable. Recommended for resources expected to be in use in the long term.	Recommended when the resource demands are likely to fluctuate and you want more flexibility.	Ideal for stateless, cost-sensitive applications that can tolerate interruptions. Not recommended for workloads that need to run for a long time or that require high stability.	Ideal for stateless, cost-sensitive applications that can tolerate interruptions. Not recommended for workloads that need to run for a long time or that require high stability.