All Products
Search
Document Center

Serverless App Engine:Billing

Last Updated:Sep 16, 2025

This topic describes the billing methods for SAE, including free trials, pay-as-you-go, and resource plans. It also explains how to calculate costs and provides examples.

Cost calculation method

Single application

To understand how costs are calculated, let's start with the most basic scenario: a single application running in SAE. The cost is calculated as follows:

  1. Calculate the Raw Resource Usage (VCPU Usage, Memory Usage, and Disk Usage). Resource usage duration is calculated in seconds. Any period of less than 1 second is rounded up to 1 second.

    Raw resource types

    Raw resource type

    Description

    Unit

    Example

    vCPU usage

    The product of the number of vCPU cores used by an application and the runtime in seconds.

    vCPU × second

    An application has two instances. The CPU of a single instance is 1 core. All instances run for 100 seconds. The vCPU usage is 2 × 1 × 100 = 200 vCPU × seconds.

    Memory usage

    The product of the memory in GB used by an application and the runtime in seconds.

    GB × second

    An application has two instances. The memory of a single instance is 2 GB. All instances run for 100 seconds. The memory usage is 2 × 2 × 100 = 400 GB × seconds.

    Disk usage

    SAE provides 20 GiB of temporary disk space for each application instance by default. This portion is not billed.

    If you need more temporary disk space, submit a ticket to apply. The portion that exceeds 20 GiB is billed based on the product of the excess temporary disk space (GiB) and the runtime (seconds).

    GiB × second

    The temporary disk space of a single instance of an application is 50 GiB. The instance runs for 10 seconds. After the free 20 GiB of temporary disk space is deducted, the billable disk usage is (50 - 20) × 10 = 300 GiB × seconds.

  2. For billing purposes, SAE calculates CU Usage by converting Raw Resource Usage (VCPU Usage, Memory Usage, and Disk Usage) into CU (Cost Unit) Usage. The conversion formula is CU usage = Raw resource usage × CU conversion coefficient. The CU conversion coefficient varies depending on the application version (Lightweight Edition, Standard Edition, or Professional Edition) , raw resource category, and server type (Default or HyGon).

    CU conversion factor details

    Important

    Lightweight Edition and Professional Edition are currently in the preview phase and available only to invited users. If you are not part of the preview, applications are created as Standard Edition, and the billing method remains the same.

    Application version/Job

    Raw resource type

    CU conversion factor (by server type)

    CU conversion factor unit

    Default server

    Hygon server

    Lightweight Edition

    vCPU usage

    0.6

    0.7644

    CU/(vCPU × second)

    Memory usage

    0.15

    0.1911

    CU/(GB × second)

    Disk usage

    0.015

    0.015

    CU/(GiB × second)

    Standard Edition

    vCPU usage

    1

    1.274

    CU/(vCPU × second)

    Memory usage

    0.25

    0.3185

    CU/(GB × second)

    Disk usage

    0.015

    0.015

    CU/(GiB × second)

    Professional Edition

    vCPU usage

    1.1

    1.4014

    CU/(vCPU × second)

    Memory usage

    0.275

    0.35035

    CU/(GB × second)

    Disk usage

    0.015

    0.015

    CU/(GiB × second)

  3. If the billing method is Resource plan (subscription), the CU usage is directly deducted from the CU resource plan. If the billing method is Pay-as-you-go (postpaid), the unit price for CU billing is shown in the following table. The prices are for reference only. The actual prices are specified in the commercial offer.

    CU unit prices

    Region

    Unit price (USD/CU)

    China (Beijing)

    China (Shanghai)

    0.000006859

    China (Hong Kong)

    Japan (Tokyo)

    0.00001176

    Singapore

    Indonesia (Jakarta)

    Germany (Frankfurt)

    0.00001069

Multiple applications

In more complex scenarios, you may run multiple applications in SAE. The cost is calculated as follows:

Important

Applications of the same version are billed together. Applications of different versions are billed separately.

For example, if your SAE runs several Lightweight Edition applications and Professional Edition applications at the same time, first calculate the total cost for the Lightweight Edition applications, and then calculate the total cost for the Professional Edition applications.

  1. Calculate the Raw Resource Usage (VCPU Usage, Memory Usage, and Disk Usage). When calculating the duration of resource usage, any period of less than 1 second is counted as 1 second.

    • vCPU usage = ∑(Number of instances × CPU cores per instance × Runtime in the current month in seconds)

    • Memory usage = ∑(Number of instances × Memory size per instance in GB × Runtime in the current month in seconds)

    • Disk usage = ∑(Number of instances × (Disk size per instance in GiB - Free disk size of 20 GiB) × Runtime in the current month in seconds)

  2. Calculate the CU Usage.

    • CU usage = ∑(Usage of each resource type × Corresponding CU conversion factor)

  3. If the billing method is Resource plan (subscription), the CU usage is directly deducted from the CU resource plan. If the billing method is Pay-as-you-go (postpaid), the cost is calculated based on the CU unit price.

    • Total cost = CU usage × CU unit price

Billing methods

First, activate SAE. After activation, you can use the service and will be billed accordingly. SAE supports two billing methods: pay-as-you-go (postpaid) and resource plan (subscription).

Pay-as-you-go (postpaid)

With this method, you do not need to purchase resources in advance. You are billed for your actual resource consumption. A bill is generated hourly based on your resource usage, and the cost is automatically deducted from your account.

Bill generation is delayed by approximately 3 hours. For example, you can view the bill for the period from 01:00 to 02:00 after 04:00.

Example - Cost calculation for pay-as-you-go

The following examples are for reference only. Your actual costs are shown on your bill.

All examples assume that a user runs only one application in the current month. The application is deployed in the Chinese mainland, each application instance runs for the same duration each day, and the Default Server is used.

The pay-as-you-go billing method is used in all examples. In practice, you can purchase a suitable resource plan to reduce costs.

Lightweight Edition

Calculation step

Example 1

Example 2

  1. Calculate raw resource usage

Daily runtime

10h

24h

Number of running days in the month

25 days

30 days

Total runtime in the month

25 × 10 × 3,600 = 900,000 seconds

30 × 24 × 3,600 = 2,592,000 seconds

Number of instances

2

8

Instance type

2-core vCPU

4 GB memory

8-core vCPU

64 GB memory

50 GiB disk

Monthly usage

2 × 2 × 900,000 = 3,600,000 vCPU × seconds

2 × 4 × 900,000 = 7,200,000 GB × seconds

8 × 8 × 2,592,000 = 165,888,000 vCPU × seconds

8 × 64 × 2,592,000 = 1,327,104,000 GB × seconds

8 × (50 - 20) × 2,592,000 = 622,080,000 GiB × seconds

  1. Calculate CU usage

CU conversion factor

0.6 CU/(vCPU × second)

0.15 CU/(GB × second)

0.6 CU/(vCPU × second)

0.15 CU/(GB × second)

0.015 CU/(GiB × second)

Convert to CU usage

3,600,000 × 0.6 = 2,160,000 CU

7,200,000 × 0.15 = 1,080,000 CU

165,888,000 × 0.6 = 99,532,800 CU

1,327,104,000 × 0.15 = 199,065,600 CU

622,080,000 × 0.015 = 9,331,200 CU

Total CU usage

2,160,000 + 1,080,000 = 3,240,000 CU

99,532,800 + 199,065,600 + 9,331,200 = 307,929,600 CU

  1. Calculate cost

CU unit price

0.000006859 USD/CU

0.000006859 USD/CU

Total cost

3,240,000 × 0.000006859 = 22.22 USD

307,929,600 × 0.000006859 = 2112.09 USD

Standard Edition

Calculation step

Example 1

Example 2

  1. Calculate raw resource usage

Daily runtime

10h

24h

Number of running days in the month

25 days

30 days

Total runtime in the month

25 × 10 × 3,600 = 900,000 seconds

30 × 24 × 3,600 = 2,592,000 seconds

Number of instances

2

8

Instance type

2-core vCPU

4 GB memory

8-core vCPU

64 GB memory

50 GiB disk

Monthly usage

2 × 2 × 900,000 = 3,600,000 vCPU × seconds

2 × 4 × 900,000 = 7,200,000 GB × seconds

8 × 8 × 2,592,000 = 165,888,000 vCPU × seconds

8 × 64 × 2,592,000 = 1,327,104,000 GB × seconds

8 × (50 - 20) × 2,592,000 = 622,080,000 GiB × seconds

  1. Calculate CU usage

CU conversion factor

1 CU/(vCPU × second)

0.25 CU/(GB × second)

1 CU/(vCPU × second)

0.25 CU/(GB × second)

0.015 CU/(GiB × second)

Convert to CU usage

3,600,000 × 1 = 3,600,000 CU

7,200,000 × 0.25 = 1,800,000 CU

165,888,000 × 1 = 165,888,000 CU

1,327,104,000 × 0.25 = 331,776,000 CU

622,080,000 × 0.015 = 9,331,200 CU

Total CU usage

3,600,000 + 1,800,000 = 5,400,000 CU

165,888,000 + 331,776,000 + 9,331,200 = 506,995,200 CU

  1. Calculate cost

CU unit price

0.000006859 USD/CU

0.000006859 USD/CU

Total cost

5,400,000 × 0.000006859 = 37.04 USD

506,995,200 × 0.000006859 = 3477.48 USD

Professional Edition

Calculation step

Example 1

Example 2

  1. Calculate raw resource usage

Daily runtime

10h

24h

Number of running days in the month

25 days

30 days

Total runtime in the month

25 × 10 × 3,600 = 900,000 seconds

30 × 24 × 3,600 = 2,592,000 seconds

Number of instances

2

8

Instance type

2-core vCPU

4 GB memory

8-core vCPU

64 GB memory

50 GiB disk

Monthly usage

2 × 2 × 900,000 = 3,600,000 vCPU × seconds

2 × 4 × 900,000 = 7,200,000 GB × seconds

8 × 8 × 2,592,000 = 165,888,000 vCPU × seconds

8 × 64 × 2,592,000 = 1,327,104,000 GB × seconds

8 × (50 - 20) × 2,592,000 = 622,080,000 GiB × seconds

  1. Calculate CU usage

CU conversion factor

1.1 CU/(vCPU × second)

0.275 CU/(GB × second)

1.1 CU/(vCPU × second)

0.275 CU/(GB × second)

0.015 CU/(GiB × second)

Convert to CU usage

3,600,000 × 1.1 = 3,960,000 CU

7,200,000 × 0.275 = 1,980,000 CU

165,888,000 × 1.1 = 182,476,800 CU

1,327,104,000 × 0.275 = 364,953,600 CU

622,080,000 × 0.015 = 9,331,200 CU

Total CU usage

3,960,000 + 1,980,000 = 5,940,000 CU

182,476,800 + 364,953,600 + 9,331,200 = 556,761,600 CU

  1. Calculate cost

CU unit price

0.000006859 USD/CU

0.000006859 USD/CU

Total cost

5,940,000 × 0.000006859 = 40.74 USD

556,761,600 × 0.000006859 = 3818.83 USD

Resource plan (subscription)

You can purchase a resource plan with a fixed amount of resources in advance to receive a more favorable price compared to the pay-as-you-go method. This method is suitable for scenarios where resource usage is stable and exceeds 1 million CU/year, service traffic has regular peaks and troughs, and the budget is clear. In general, the larger the capacity of a resource plan, the greater the discount.

Resource plan types and pricing

Important
  • Starting from 00:00 (UTC+8) on February 12, 2025, SAE has launched CU resource plans. The CU resource plan is a yearly package.

  • If you have previously purchased CPU and memory resource plans, the system first converts vCPU usage and memory usage into CU usage. Then, the quota of one resource plan is used to offset the total CU usage until the quota of that plan is exhausted. After that, the quota of the other resource plan is used.

The Chinese mainland

Resource plan capacity

Price per CU resource plan

Promotional price (Promotion period: February 17, 2025 to March 31, 2026)

1 million CU/year

6.85 USD

6.51 USD

10 million CU/year

68.00 USD

64.60 USD

30 million CU/year

201.00 USD

190.95 USD

100 million CU/year

665.00 USD

631.75 USD

500 million CU/year

3,292.00 USD

3,127.40 USD

2 billion CU/year

13,030.00 USD

12,378.50 USD

Hong Kong (China), Macao (China), Taiwan (China), and other regions outside the Chinese mainland

Resource plan capacity

Price per CU resource plan

Promotional price (Promotion period: February 17, 2025 to March 31, 2026)

1 million CU/year

10.60 USD

10.07 USD

10 million CU/year

105.00 USD

99.75 USD

30 million CU/year

314.00 USD

298.30 USD

100 million CU/year

1,037.00 USD

985.15 USD

500 million CU/year

5,131.00 USD

4,874.45 USD

2 billion CU/year

20,311.00 USD

19,295.45 USD

Purchase a resource plan

  1. Select a suitable resource plan based on your predicted resource usage. For example, 10 million CU can support one Standard Edition application instance with 1 CPU core and 2 GB of memory (using a Default server) to run continuously for 77 days.

  2. Purchase an SAE CU resource plan.

Resource plan validity

When you purchase a resource plan, review the validity period on the purchase page. For example, if you purchase a one-year resource plan at 14:00 on February 12, 2025, the plan will expire at 14:00 on February 12, 2026.

Applicable regions for resource plans

Resource plans can be used in all available regions.

Resource plan deduction order

You can purchase multiple resource plans. The system deducts resources from the plans based on their expiration date, starting with the one that expires soonest. If multiple resource plans have the same expiration time, they are used in the order they were purchased.

If you have not purchased a resource plan, or your resource plan is exhausted or has expired, the pay-as-you-go billing method is used.

View resource plans

After you purchase a resource plan (subscription), you can log on to the SAE console. In the Resource Plan section in the upper-right corner of the Overview page, you can view the usage details of your resource plans.

Resource plan unsubscription rules

You can request a full refund for an unused resource plan within 5 days of purchase. You can perform a self-service unsubscription online. If a resource plan was purchased more than 5 days ago or has been used, it cannot be refunded. For more information, see Unsubscription rules.

Resource plan FAQ

How do I set the instance type when migrating from ECS to SAE?

For example, if you previously deployed four identical instances of the same application on a 4-core 16 GiB ECS instance, you can deploy four 1-core 4 GiB application instances in SAE after migration.

After deployment, you can use a stress testing tool to test application performance, such as queries per second (QPS).

Extra billable items

If your SAE application integrates with other Alibaba Cloud services, you will incur extra fees for services such as networking, storage, databases, middleware, logging, and observability.

Warning

When you delete an SAE application , SAE stops billing for it.

However, if your SAE application depends on other services, such as CLB (a load balancing service), these dependent services continue to incur fees.

To avoid unnecessary expenses, make sure to stop or delete these services when they are no longer needed and verify their status to ensure that billing has completely stopped.

Service type

Requirements and scenarios

Implementation

Billing reference

Network

SAE applications need to be accessed from the internet (inbound traffic).

Access applications based on SAE Ingress (gateway routing):

Cloud-native API Gateway billing

ALB billing

MSE cloud-native gateway billing

Access applications based on SAE Service:

NLB billing

CLB billing

SAE applications need to access the internet (outbound traffic).

Configure an Internet NAT gateway for the VPC associated with the SAE application

NAT Gateway billing

Attach an EIP to each instance of the SAE application

EIP billing

Enable communication between microservice applications using a registry.

Implement service registration and discovery based on a registry such as Nacos

The built-in Nacos registry in SAE is free of charge.

MSE Nacos registry

Enable internal communication between applications.

Access applications based on SAE Ingress (gateway routing):

Cloud-native API Gateway billing

ALB billing

MSE cloud-native gateway billing

Access applications based on SAE Service:

NLB billing

CLB billing

Storage

Persistent storage for SAE application data

NAS storage

NAS billing

OSS storage

OSS billing

Database

SAE application connects to a database service provided by Alibaba Cloud.

Application accesses an Alibaba Cloud database

See the billing documentation for the specific database service.

Middleware

SAE Standard Edition and Professional Edition applications integrate with the microservice governance capabilities provided by MSE.

Microservice governance

Professional Edition: Microservice governance is free of charge.

Standard Edition: Microservice governance must be activated separately and is billed.

Log

Centralized collection and analysis of SAE application logs

Configure log collection to SLS

SLS billing

Configure log collection to Kafka

Kafka billing

Observability

SAE Standard Edition and Professional Edition applications integrate with the capabilities of ARMS Premium Edition.

ARMS advanced monitoring

Professional Edition: ARMS advanced monitoring is free of charge.

Standard Edition: ARMS advanced monitoring must be activated separately and is billed.

View bills

View billing details

  1. Log on to Expenses and Costs and go to the Monthly Bills Overview page to view your account's monthly consumption. You can switch accounts to view the summary of consumption for associated RAM users.

    image

  2. Go to the Billing Details page, click the corresponding tab, and then view your consumption details.

    • Billing Records: This section shows the consumption records of your account in hourly billing cycles. For example, if you continuously use SAE from 00:00 to 24:00 on August 1, 24 consumption records are displayed, corresponding to the consumption from 00:00 to 01:00, 01:00 to 02:00, and so on, up to 23:00 to 24:00.

      Important

      SAE bill generation is delayed by approximately 2 hours. For example, you can view the consumption record of SAE from 13:00 to 14:00 in the Expenses and Costs console at about 16:00.

      image

    • Billing Details: You can filter billing details by Statistic Item and Statistic Period. The details include product details, consumption type, billable item, price, and deduction information.

      image

      Important
      • The Instance ID in the billing details corresponds to your Application ID (① and ② in the figure) or Task Template ID. You can view and copy the target ID on the application details page or task template details page. Then, on the Billing Details tab, you can search for the bill for a single application or task template by Instance ID (③ in the figure).

      • The Billable Item (④ in the figure) indicates the billable items of the application or task template. You can reconcile your bill against your resource usage based on the billable item type.

      The following is an example of an application ID.

      sc_app_id_intl

    • View Usage Details: Follow the on-screen instructions to download usage information in CSV format.

      image

View resource plan usage details

Log on to Expenses and Costs. Go to the Usage Details page of your resource plan, enter the specific resource instance name, and view the detailed deduction records of the resource plan.

SAE resource plans are decrementing. During the validity period, the plan's quota is consumed over time until it is exhausted or expires. Remaining quota after deduction = Remaining quota before deduction - Deducted amount, where the deducted amount is the amount of resources used by the instance in a specific time period.

You can also view the usage of your purchased CU resource plans in the Resource Plan area on the right side of the Overview Page.

Billing reconciliation FAQ

How do I reconcile SAE resource bills?

For more information, see View billing details and View resource plan usage details.

Why is SAE still being consumed on my bill after I stopped using the resources?

Assume that you used SAE resources from 13:00 to 14:00, stopped using them at 14:00, and immediately checked the Billing Records and Billing Details tabs. You find that SAE still has consumption records after 14:00.

This is normal because SAE bill generation is delayed by approximately 2 hours. Therefore, after you stop using SAE resources at 14:00, check the Billing Records tab at approximately 16:00 to view the billing details. You can also export the detailed data on the View Usage Details tab if needed.

Account deduction order

  1. Credit limit for enterprise users.

  2. Valid coupons in your Alibaba Cloud account.

  3. Valid stored value cards in your Alibaba Cloud account.

  4. Cash balance in your Alibaba Cloud account.

  5. Balance of your linked Alipay account.

  6. Bank card specified when you linked your Alipay account.

  7. Other express-linked bank cards in your Alipay account.

  8. Yu'e Bao balance of your linked Alipay account (You must enable the Yu'e Bao consumption deduction switch in Alipay).

The credit limit for enterprise users, valid coupons, and the cash balance in your Alibaba Cloud account are applied sequentially and cannot be used simultaneously for the same charge.

Overdue payments and renewals

When the available credit in your account (including your Alibaba Cloud account balance and coupons) is insufficient to pay an outstanding bill, your account immediately becomes overdue.

Note

If you no longer need to use SAE, delete the related resources to avoid further charges:

  • To delete an SAE application, see Delete an application.

  • If your application integrates with other Alibaba Cloud services, you will incur extra fees for services such as networking, storage, databases, middleware, logging, and observability. Before you delete these resources, back up necessary data.

Overdue payments

Overdue duration

Description

Overdue for less than 7 days

If your account is overdue for less than 7 days (7 × 24 = 168 hours), the application instances you have created remain active and will continue to be billed.

When your SAE service is overdue, you cannot deploy or scale out new application instances, nor can you perform operations such as deployment, restart, or specification changes on existing instances.

Overdue for more than 7 days

If you do not pay all overdue bills within 7 days (7 × 24 = 168 hours) from the date the payment becomes overdue, the system will suspend your SAE services at the end of this period. At the same time, the application instances you created in SAE are released, and their data is deleted and cannot be recovered.

To ensure that your services are not affected, make the payment promptly.

View consumption overview

  1. Log on to Expenses and Costs.

  2. On the Account Overview page, view the consumption overview.

Renewal policy

  1. Log on to Expenses and Costs.

  2. In the navigation pane on the left, click Payment Details. On the Payment Details page, on the Pending Payment tab, click Pay in the Actions column and follow the on-screen instructions to add funds.

    awOqyy2vzR