This document describes the billing rules for Cloud Native Build Service.
Billing Overview
Cloud Native Build uses pay-as-you-go billing, charging fees according to actual consumption. Version billing explanation is shown in the table below:
|
Cloud Native Build Community Edition | Each top-level organization is billed independently. At the beginning of the month, product usage fees are charged based on the organization's scale of usage in the previous calendar month. | |
Cloud Native Build Enterprise Edition | Each standalone deployment of Cloud Native Build Enterprise Edition is charged for product service based on the deployed instance's scale of usage in the previous calendar month at month start.
Supplementary explanation: Since the Enterprise Edition is deployed in the Customer VPC, deployment resource consumption will occur. This resource consumption will be charged directly by the corresponding resource provider. Cloud Native Build only charges for product service on a usage-based basis. | |
Renewal, Arrears and Refund
The Community Edition and Enterprise Edition both adopt a monthly settlement and postpaid billing mode. At the beginning of the month, the product service fee is automatically deducted based on the usage of the previous calendar month. Therefore, renewal and refund scenarios are not involved.
The Community Edition changes to read-only state when in arrears, forbidding write actions. For example:
Code repository, artifact repository push forbidden.
Prohibit starting new cloud-native construction pipelines.
Prohibit starting new cloud-native development spaces.
Cloud Native Build enterprise edition service will stop receiving after-sales support from the product side in case of arrears, such as feedback processing and upgrade assistance.
Among them, the resource fee for enterprise edition deployment is charged by the resource provider. If the resource falls into arrears, the provider may reclaim the resources. After recycling, the data stored will face termination.
Note:
Note: The recycling policy may be different for different resources. You can go to Document Center to check the resource recycling instructions for the target product.