Updated on 2025-08-28 GMT+08:00

Yearly/Monthly Package

Scenarios

Yearly/monthly billing can be more cost-effective than pay-per-use billing if the resource usage is predictable, especially for the following types of workloads:

  • Running for a long time with constant resources: For example, enterprise service systems. Yearly/Monthly billing provides higher cost-efficiency.
  • Long-term: For example, scientific research projects and large-scale events. Yearly/Monthly billing ensures stable resource supply throughout the project.
  • Predictable service peaks: For example, e-commerce promotions, festivals, and holidays. Resource insufficiency can be avoided by purchasing resources in advance for peak demands.
  • High data security: For services that require high data security, yearly/monthly billing facilitates continuous usage of the resources.

Billing Items

Table 1 Billing items

Billing Item

Description

Maximum concurrent scans

Billed by the number of packages

Required Duration

You can purchase a package for 1 to 9 months or 1 year.

If you select one year (12 months), you only need to pay for 10 months.

The price is displayed at the bottom of the purchase page.

Billing Cycle

The billing cycle of a yearly/monthly CodeArts Governance service is determined by purchase duration (UTC+8). The billing starts from the time you activate or renew your subscription (precise to seconds), and ends at 23:59:59 on the expiration date.

For example, if you purchased a CodeArts Governance service for one month at 15:50:04 on March 08, 2023, the billing period is from 15:50:04 March 08, 2023 to 23:59:59 April 08, 2023.

Billing Example

Assume that you purchased the CodeArts Governance service for one month at 15:50:04 on March 8, 2023 and manually renewed it for another month before it expires. Then:

  • The first billing period: March 08, 2023, 15:50:04 to April 08, 2023, 23:59:59
  • The second billing period: April 08, 2023, 23:59:59 to May 08, 2023, 23:59:59

Impact of Expiration

Figure 1 describes the status of each stage of a yearly/monthly CodeArts Governance service. After you purchase a resource, it runs properly during the billing period, which is also called "validity period". If the resource is not renewed when expires, it goes into the grace period and then the retention period.

Figure 1 Lifecycle of a yearly/monthly CodeArts Governance service

Expiration reminder

Before a yearly/monthly package expires, the system will send an expiration reminder to the creator of the account by email, SMS, and internal message.
  • A yearly subscription: The reminder is sent 30 days, 15 days, 7 days, 3 days, and 1 day before the resource expires.
  • A monthly subscription: The reminder is sent 15 days, 7 days, 3 days, and 1 day before the resource expires.

When the resource usage or traffic usage of the service reaches 80% or 100%, you will receive an expiration reminder.

Impact of expiration

If your yearly/monthly CodeArts Governance service is not renewed when expires, it goes into the grace period and the resource changes to the Expired state. During the grace period, you can still use the service.

If your account is still in arrears after the grace period ends, the resources enter the retention period and their status turns to Frozen. You cannot perform any operations on these resources.

After the retention period ends, if the service is still not renewed, it will be released and the related data cannot be recovered.