Product Billing
Last Updated:：2024-09-11 10:05:57
Billing Items
Billing items refer to the resources that are charged. A cloud server includes resources such as instance specifications, images, cloud disks, and public IP addresses. The specific billing items involved are as follows:
| Billing Items | Description | Supported Billing Modes |
|---|---|---|
| Instance Specifications | Refers to the fees charged for computing resources (vCPU, GPU, and memory) and local disks (if any) based on the selected instance specifications. |
|
| Image | Fees are determined according to the type and usage of the image. |
|
| Cloud Disk | Cloud disks include system disks and data disks, and fees are charged based on the unit price, capacity, and duration. |
|
| Additional Storage | Additional storage takes the form of NFS, DDN, and other types, and fees are charged based on the unit price, capacity, and duration. |
|
| Snapshot Billing | Fees are charged based on the capacity and duration of the snapshot. |
|
| Public IP | After binding a public IP to the cloud server, fees are charged for public network traffic and bandwidth. |
|
Billing Methods
Subscription
- Prepaid model, pay for one or multiple months or even years in advance.
- The platform offers discounts on some long-term plans, which can save expenses.
Pay-As-You-Go
- Elastic billing model, time is billed to the second, and billing is calculated once per hour.
- Resources can be activated and released on-demand.
For more information about billing, please refer to the Billing Method Overview.
Pricing Details
The prices of instances and their configuration options (system disk, data disk, public IP, etc.) are subject to the actual order result.
For more information on ordering, please refer to Purchase Instance.
Bill Management
The cloud platform summarizes users' consumption on the platform every week from different dimensions to help users understand their consumption behavior and plan resources and costs.
For more information on billing, please refer to the Billing Overview.
Changing Billing Methods
After purchasing resources, if the current billing method does not meet business needs, users can change their billing method.
- Changing from Pay-As-You-Go to Subscription
- Changing from Subscription to Pay-As-You-Go
For more information on billing after the operation, please refer to Modify Billing Methods.
Upgrading or Downgrading Product Configurations
If the current product configuration does not meet business needs, users can upgrade or downgrade the configuration to meet their needs. Pay-As-You-Go or Subscription instances support real-time upgrade and downgrade, and the new instance configuration will continue to be effective until the next modification or resource release.
For more information on billing after the operation, please refer to Adjust Product Configurations.
Renewal and Subscription Cancellation
After Subscription instances expire, they will affect the normal operation of instances. Users can renew their instances within a specified period if they wish to continue using the instances. For updated information, please refer to Expiration Introduction and Renewal Introduction.
If users no longer need Subscription instances, they can apply for cancellation. For more information, please refer to Subscription Cancellation Introduction.
After successful cancellation, resources will be moved to the recycle bin with a retention period. During this period, users can manually destroy or restore resources. If no action is taken, resources will be forcibly released and cannot be restored after the retention period. For more information, please refer to Destroy/Return Instance and Recycle or Restore Instance.
Account Overdue
For Pay-As-You-Go instances, if the account balance is not sufficient to settle payment, an overdue notice will be sent. To avoid affecting the normal operation of instances, please recharge in time. For more information, please refer to Overdue Introduction and Recharge Operation Guide.
After overdue, resources will be moved to the recycle bin with a retention period. During this period, users can manually destroy or restore resources. If no action is taken, resources will be forcibly released and cannot be restored after the retention period. For more information, please refer to Destroy/Return Instance and Recycle or Restore Instance.