All Products
Search
Document Center

Serverless App Engine:Product billing

Last Updated:Nov 18, 2025

This topic describes billing for SAE, including free trials, pay-as-you-go, and resource plans. It also provides methods and examples to help you estimate your costs.

Cost calculation method

Single application

First, let's look at how to calculate costs for the basic scenario of running a single application in SAE. The cost is calculated in the following steps:

  1. Calculate the Raw Resource Usage, which includes VCPU Usage, Memory Usage, and Disk Usage. Resource usage duration is calculated in seconds, and any period 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 virtual CPU cores used by an application and the runtime in seconds.

    vCPU × second

    An application has two instances. Each instance has a CPU specification of 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. Each instance has a memory specification of 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 is not billed.

    To request more temporary disk space, submit a ticket. Usage exceeding 20 GiB is billed based on the product of the extra temporary disk space (GiB) and the runtime (seconds).

    GiB × second

    An application instance has 50 GiB of temporary disk space and runs for 10 seconds. After deducting the 20 GiB of free temporary disk space, the billable disk usage is (50 - 20) × 10 = 300 GiB × seconds.

  2. To calculate CU Usage, SAE converts the Raw Resource Usage (VCPU Usage, Memory Usage, and Disk Usage) into CU Usage (Cost Unit) for billing. The conversion formula is CU Usage = Raw Resource Usage × CU conversion coefficient. The CU conversion coefficient varies based on the application version (Lightweight Edition, Standard Edition, or Professional Edition) , raw resource type, and server type (Default or HyGon).

    CU conversion coefficient details

    Important

    The Lightweight and Professional editions are in invite-only beta testing. If you are not in the beta test, your applications are created as the Standard edition, and the billing method remains the same.

    Application edition/Job task

    Raw resource type

    CU conversion coefficient (by server type)

    CU conversion coefficient unit

    Default server

    Hygon server

    Lightweight

    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

    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

    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 you use a resource plan (subscription), the CU usage is offset by your plan. If you use the pay-as-you-go billing method, the unit prices for CU billing are shown in the following table. The prices are for reference only. The actual prices are subject to the commercial offer.

    CU unit price

    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 where you run multiple applications , the cost is calculated in the following steps:

Important

Applications of the same edition are billed together, while applications of different editions are billed separately.

For example, if you run both Lightweight Edition and Professional Edition applications, the costs for each edition are calculated and billed separately.

  1. Calculate the Raw Resource Usage, which includes VCPU Usage, Memory Usage, and Disk Usage. Resource usage duration is calculated in seconds, and any period less than 1 second is rounded up to 1 second.

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

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

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

  2. Calculate the total CU Usage.

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

  3. If you use a resource plan (subscription), the CU usage is offset by your plan. If you use the pay-as-you-go billing method, the cost is calculated based on the CU unit price.

    • Total cost = CU usage × CU unit price

Billing methods

You can activate SAE to use the service and enable billing. SAE supports two billing methods: pay-as-you-go and resource plan (subscription).

Pay-as-you-go

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

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

Example - Pay-as-you-go cost calculation

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

These examples assume that a user runs a single application for one month in the Chinese mainland, each application instance runs for the same duration each day, and the Default Server is used.

All examples use the pay-as-you-go billing method. In a real-world scenario, you can purchase a resource plan to reduce costs.

Lightweight edition

Calculation step

Example 1

Example 2

  1. Calculate raw resource usage

Daily runtime

10h

24h

Running days in the month

25 days

30 days

Total monthly runtime

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

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

Number of instances

2

8

Specification per instance

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 coefficient

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)

Converted 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

USD 0.000006859/CU

USD 0.000006859/CU

Total cost

3,240,000 × 0.000006859 = USD 22.22

307,929,600 × 0.000006859 = USD 2,112.09

Standard edition

Calculation step

Example 1

Example 2

  1. Calculate raw resource usage

Daily runtime

10h

24h

Running days in the month

25 days

30 days

Total monthly runtime

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

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

Number of instances

2

8

Specification per instance

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 coefficient

1 CU/(vCPU × second)

0.25 CU/(GB × second)

1 CU/(vCPU × second)

0.25 CU/(GB × second)

0.015 CU/(GiB × second)

Converted 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

USD 0.000006859/CU

USD 0.000006859/CU

Total cost

5,400,000 × 0.000006859 = USD 37.04

506,995,200 × 0.000006859 = USD 3,477.48

Professional edition

Calculation step

Example 1

Example 2

  1. Calculate raw resource usage

Daily runtime

10h

24h

Running days in the month

25 days

30 days

Total monthly runtime

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

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

Number of instances

2

8

Specification per instance

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 coefficient

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)

Converted 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

USD 0.000006859/CU

USD 0.000006859/CU

Total cost

5,940,000 × 0.000006859 = USD 40.74

556,761,600 × 0.000006859 = USD 3,818.83

Resource plan (subscription)

You can purchase a resource plan in advance to obtain a lower 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 your budget is clearly defined. Typically, the larger the capacity of the resource plan, the greater the discount.

Resource plan types and pricing

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

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

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

USD 6.85

USD 6.51

10 million CU/year

USD 68.00

USD 64.60

30 million CU/year

USD 201.00

USD 190.95

100 million CU/year

USD 665.00

USD 631.75

500 million CU/year

USD 3,292.00

USD 3,127.40

2 billion CU/year

USD 13,030.00

USD 12,378.50

Hong Kong (China), Macao (China), Taiwan (China), and other regions

Resource plan capacity

Price per CU resource plan

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

1 million CU/year

USD 10.60

USD 10.07

10 million CU/year

USD 105.00

USD 99.75

30 million CU/year

USD 314.00

USD 298.30

100 million CU/year

USD 1,037.00

USD 985.15

500 million CU/year

USD 5,131.00

USD 4,874.45

2 billion CU/year

USD 20,311.00

USD 19,295.45

Purchase a resource plan

  1. Select a suitable resource plan based on your predicted resource usage. To give you an idea, 10 million CU can support one Standard Edition application instance with 1 core and 2 GB of memory (using a default server) running continuously for about 77 days.

  2. Purchase an SAE CU resource plan.

Resource plan validity period

When you purchase a resource plan, carefully read the description of its validity period on the purchase page. For example, if you purchase a one-year resource plan at 14:00 on February 12, 2025, it expires at 14:00 on February 12, 2026.

Applicable regions for resource plans

Resource plans can be used in all available regions.

Resource plan offset order

You can purchase multiple resource plans. The system offsets usage against the plans in the order they expire, with the one expiring soonest used first. 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 used up or has expired, the pay-as-you-go method is used.

View resource plans

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

Resource plan unsubscription rules

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

Resource plan FAQ

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

For example, if you previously deployed four identical instances of an application on a 4-core, 16 GiB ECS instance, we recommend that you 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 metrics, such as Queries Per Second (QPS).

Additional billable items

If your SAE application integrates with other Alibaba Cloud services, additional fees are incurred for services such as networking, storage, databases, middleware, logging, and observability.

Warning

When you delete an SAE application , SAE stops billing for that resource.

However, if your SAE application depends on other services, such as Classic Load Balancer (CLB), these services will continue to incur fees.

To avoid unnecessary expenses, make sure to stop or delete these services when they are no longer needed and confirm their status to prevent further billing.

Service type

Requirements and scenarios

Implementation method

Billing reference

Network

Your SAE application needs to be accessed from the internet (inbound traffic)

Access the application based on SAE Ingress (gateway routing):

Cloud Native API Gateway billing

ALB billing

MSE cloud-native gateway billing

Access the application based on SAE Service:

NLB billing

CLB billing

Your SAE application needs 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

Use a registry to enable communication between microservice applications

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

SAE's built-in Nacos registry is free.

MSE Nacos registry

Enable internal network communication between applications

Access the application based on SAE Ingress (gateway routing):

Cloud Native API Gateway billing

ALB billing

MSE cloud-native gateway billing

Access the application based on SAE Service:

NLB billing

CLB billing

Storage

Enable data persistence for SAE applications

NAS storage

NAS billing

OSS storage

OSS billing

Database

Your 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

Your SAE Standard and Professional Edition applications integrate with the microservice administration capabilities of MSE

Microservice administration

Professional Edition: Microservice administration is free.

Standard Edition: Microservice administration requires separate activation and is billed.

Log

Centrally collect and analyze logs for SAE applications

Set up log collection to SLS

SLS billing

Set up log collection to Kafka

Kafka billing

Observability

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

ARMS advanced monitoring

Professional Edition: ARMS advanced monitoring is free.

Standard Edition: ARMS advanced monitoring requires separate activation and is billed.

View bills

View billing details

  1. Log on to Expenses and Costs and go to the Monthly Billing Overview page to view your monthly consumption. You can switch accounts to view the summarized consumption information of associated RAM users.

    image

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

    • Billing Records: View the consumption records of your account for each hourly billing cycle. For example, if you use SAE continuously from 00:00 to 24:00 on August 1, 24 consumption records are generated, one for each hour from 00:00 to 24:00.

      Important

      SAE bill generation is delayed by approximately 2 hours. For example, you can query the SAE consumption record for the 13:00 to 14:00 period at around 16:00 in the Expenses and Costs console.

      image

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

      image

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

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

      The following is an example of an Application ID.

      sc_app_id_intl

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

      image

View resource plan usage details

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

SAE resource plans are of the total decreasing type. During the validity period, the plan's capacity decreases with use until it is exhausted or expires. The remaining amount is calculated as follows: Remaining amount after deduction = Remaining amount before deduction - Deducted amount. The deducted amount is the resource usage of the instance during a specific 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 my SAE resource bills?

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

After I stop using resources, why does my bill show that SAE is still consuming 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, you can check the Billing Records tab around 16:00 to view the bill details. You can also export detailed data from 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 prepaid 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 linking your Alipay account.

  7. Other express payment bank cards linked to your Alipay account.

  8. Yu'e Bao balance of your linked Alipay account (requires you to enable the Yu'e Bao auto-debit feature in Alipay).

The credit limit for enterprise users, valid coupons, and cash balance in your Alibaba Cloud account cannot be used simultaneously.

Overdue payments and renewals

If the available balance in your account, including your Alibaba Cloud account balance and coupons, is insufficient to pay your outstanding bills, your account immediately has an overdue payment.

Note

If you no longer need to use SAE, release 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, additional fees are incurred for services such as networking, storage, databases, middleware, logging, and observability. Before you delete these resources, make sure to back up any necessary data.

Overdue payments

Overdue duration

Description

Overdue for less than 7 days

If your account has an overdue payment for less than 7 days (168 hours), your application instances in SAE continue to occupy cloud resources and incur fees, unless they are deleted or stopped.

When your SAE service has an overdue payment, the following limits apply.

  • Normal billing and operations:

    • Existing application instances can still be used and continue to be billed.

    • Unrestricted functions include stopping, scaling in, and deleting applications.

  • Restricted management functions:

    • Restricted application functions include creating, copying, starting, restarting, scaling out, and deploying applications.

Overdue for more than 7 days

If you fail to pay all outstanding bills within 7 days (168 hours) of the payment becoming overdue, SAE services are stopped. At the same time, the application and task instances that you created in are released, and their data is deleted and cannot be recovered.

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

View consumption overview

  1. Log on to Expenses and Costs.

  2. On the Account Overview page, you can 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 pay the overdue amount.

    awOqyy2vzR