To use the Cloud Native Build service (hereinafter referred to as "the Service") provided by Tencent Cloud Computing (Beijing) Co., Ltd., you should read and comply with the "Cloud Native Build Service Level Agreement" (hereinafter referred to as "this Agreement" or "SLA") and the "Cloud Native Build Service Agreement". This Agreement includes the terms and definitions of the Service, service availability/service success rate indicators, compensation plans, disclaimers, and other related content. Please read carefully and fully understand the terms. Terms that limit, disclaim, or involve your significant rights may be highlighted in bold, underlined, or other forms to draw your attention. Unless you have fully read, understood, and accepted all the terms of this Agreement, please do not purchase the Service. By clicking "Agree", "Next", or through your purchase, use, or any other express or implied acceptance of this Agreement, you are deemed to have read and agreed to be bound by this Agreement. This Agreement shall take legal effect between you and the Cloud Native Build Service and become a legally binding document for both parties.

1. Terms and Definitions

1.1 Cloud Native Build Service

The Cloud Native Build Service is based on the Docker ecosystem, abstracting environments, caches, and plugins. It uses declarative syntax and a code-based approach to automate processes, reducing the cost of repetitive labor and minimizing manual operation errors, thereby improving development efficiency.

1.2 Service Unavailability

Error Rate Unavailability: Refers to the error rate of the Cloud Native Build Service exceeding 0.05% (excluding 0.05%) within a unit time (5 minutes as a statistical granularity), which is considered as error rate unavailability for that unit time.

Failed Request Unavailability: Refers to the Cloud Native Build Service being continuously unavailable for 10 minutes or longer. Periods shorter than 10 minutes are not counted as service unavailability time.

Both Error Rate Unavailability and Failed Request Unavailability are considered as Service Unavailability.

1.3 Error Rate

The Error Rate refers to the proportion of failed requests returned by the Cloud Native Build Service out of the total user requests within a unit time (5 minutes).

1.4 Failed Requests

Failed Requests refer to requests returned by the Cloud Native Build Service with server internal error codes, including Internal Error (500 error) or Service Unavailable (503 error), but excluding requests throttled due to rate limits or failed requests caused by Cloud Native Build upgrades, changes, or downtime.

User Requests refer to requests received by the Cloud Native Build Service server from users, excluding requests that are unauthenticated, fail authentication, or are in a state of service suspension due to unpaid fees. Requests from user-side attacks on the Cloud Native Build Service or requests executed asynchronously in the backend due to cross-region replication or lifecycle rules are not considered valid requests or failed requests.

1.5 Service Unavailable Time

Service Unavailable Time refers to the total minutes of Cloud Native Build Service unavailability within a Service Month. If both Error Rate Unavailability and Failed Request Unavailability occur at the same time, only one unavailability time is counted (as shown in Example 1). If different functional modules of the Cloud Native Build Service are unavailable, they should be uniformly regarded as Cloud Native Build Service unavailability, meaning the unavailability times of different functional modules at the same time are calculated uniformly and not accumulated (as shown in Example 2).

Example 1:

For example, after purchasing the Cloud Native Build Service, if there is a 15-minute Error Rate Unavailability from 17:01 to 17:16 on a certain day and a 15-minute Failed Request Unavailability from 17:06 to 17:21 on the same day, the overlapping period (17:06-17:16) is counted as one unavailability time. The total Service Unavailable Time for this instance is 20 minutes.

Example 2:

For example, if the Cloud Native Build Service you purchased includes functional module A and functional module B, and functional module A experiences 15 minutes of Service Unavailability from 17:01 to 17:16 on a certain day, while functional module B experiences 15 minutes of Service Unavailability from 17:06 to 17:21 on the same day, the overlapping period (17:06-17:16) is counted as one unavailability time. The total Service Unavailable Time for this instance is 20 minutes.

1.6 Service Month

Refers to each natural month included in the service period you purchased. For example, if you purchase the Service from March 17 to June 16, it includes 4 Service Months, where the first Service Month is from March 17 to March 31, the second Service Month is from April 1 to April 30, the third Service Month is from May 1 to May 31, and the fourth Service Month is from June 1 to June 16. Service Availability is calculated separately for each Service Month.

1.7 Monthly Service Fee

Refers to the total service fee you paid for using the Cloud Native Build Service in a specific Service Month.

1.8 Total Time in a Service Month

Calculated as the number of days in the Service Month × 24 (hours) × 60 (minutes).

2. Service Availability/Success Rate Calculation Method

2.1 Service Availability Calculation Method

Service Availability = (1 - Service Unavailable Time / Total Time in a Service Month) × 100%

2.2 Service Availability

The Service Availability provided by Cloud Native Build is: Cloud Native Build Service Availability is no less than 99.8%.

Assuming a month has 30 days, the available time for the Cloud Native Build Service should be 30 days × 24 hours × 60 minutes × 99.8% = 43,113.6 minutes, meaning the allowed unavailability time is 43,200 - 43,113.6 = 86.4 minutes.

3. Compensation Plan

For this Service, if the Service Availability falls below the standard specified in Article 2 of this Agreement, paid customers have the right to receive compensation according to the following terms:

3.1 Compensation Standards

(1) Compensation will be provided in the form of virtual credits issued by Tencent Cloud. The virtual credits cannot be cashed out or invoiced and can only be used by you through your account for the Service. You may not transfer or gift the credits.

(2) If the Service Availability standard is not met in a Service Month, the compensation amount will be calculated separately for that non-compliant Service Month. The total compensation shall not exceed the corresponding Monthly Service Fee you paid for the Service in the non-compliant Service Month (excluding fees deducted by credits, coupons, or service fee waivers).

Service Availability in a Service Month	Compensation Credit Amount
Below 99.8% but equal to or above 99.0%	10% of the Monthly Service Fee for the non-compliant Service Month
Below 99.0% but equal to or above 95.0%	25% of the Monthly Service Fee for the non-compliant Service Month
Below 95.0%	50% of the Monthly Service Fee for the non-compliant Service Month

3.2 Compensation Application Deadline

(1) If the Service Availability standard is not met in a Service Month, you may submit a compensation application through the ticket system of your corresponding account no earlier than the fifth (5th) working day after the end of the non-compliant Service Month. After you submit the compensation application, Cloud Native Build will conduct verification. If there is a dispute regarding the calculation of Service Availability in a Service Month, both parties agree that the final determination shall be based on Cloud Native Build's backend records.

(2) The latest time for you to submit a compensation application shall not exceed sixty (60) natural days after the end of the non-compliant Service Month. If you do not submit a compensation application within sixty (60) days after the end of the non-compliant Service Month, or if you submit the application after sixty (60) days, or if you submit the application through non-agreed methods, it will be deemed that you have automatically waived the right to claim compensation and other rights against Cloud Native Build. Cloud Native Build reserves the right to reject your compensation application and will not provide any compensation or remedy.

4. Disclaimer

Service Unavailability caused by the following reasons is not included in the calculation of Service Unavailability or Cloud Native Build's compensation scope. Cloud Native Build shall not be liable to you:

4.1 System maintenance notified in advance by Cloud Native Build, including cutover, repair, upgrades, and simulated fault drills.

4.2 Any network, device failure, or configuration adjustment outside the equipment owned by Cloud Native Build.

4.3 Routine system maintenance time, unavailability of implicitly dependent services such as cloud servers, cloud disks, load balancing, private networks, or cloud monitoring.

4.4 Build failures or prolonged build blocking caused by the inability to connect to user code repositories, third-party open-source repositories, or third-party image repositories associated with build tasks.

4.5 Attacks or other improper actions against your application interfaces or data.

4.6 Loss or leakage of data, passwords, or other credentials due to improper maintenance or confidentiality by you.

4.7 Negligent authorization, incorrect operations, or issues with your own equipment or third-party software/devices.

4.8 Failure to follow Cloud Native Build product documentation or usage recommendations.

4.9 Errors caused by content violations or other reasons leading to domain blocking.

4.10 Reduced availability due to sudden large-scale traffic growth without prior written notice to Cloud Native Build.

4.11 Service unavailability or non-compliance not caused by Cloud Native Build or the product.

4.12 Situations described in relevant laws, agreements, rules, or Cloud Native Build's separately published rules or notices where Cloud Native Build is exempt from liability or compensation.

5. Other

5.1 Both parties confirm and agree that under any circumstances, if you suffer losses due to Cloud Native Build's breach of contract during your use of the Service, the total compensation for Cloud Native Build's breach shall not exceed the total service fee you have paid for the corresponding non-compliant Service.

5.2 Cloud Native Build reserves the right to modify the terms of this Agreement as needed. You can review the latest version of the Agreement on the Cloud Native Build official website (https://cnb.cool). If you do not agree with the modifications made by Cloud Native Build, you have the right to stop using the Service. If you continue to use the Service, it will be deemed that you accept the modified Agreement.

5.3 As an annex to the "Cloud Native Build Service Agreement", this Agreement has the same legal effect as the "Cloud Native Build Service Agreement". For matters not covered in this Agreement, you must comply with the relevant terms of the "Cloud Native Build Service Agreement". If there is any conflict or inconsistency between this Agreement and the "Cloud Native Build Service Agreement", this Agreement shall prevail, but only to the extent of such conflict or inconsistency. (End)