[Billing Change] EMAS Serverless Function Compute Billing Rule Change

New Hourly Minimum Consumption Rule

• When calculating daily bills, the system first assesses resource consumption based on a per-function, per-hour dimension.

• If a function generates **compute resource consumption (GBs > 0)** within a specific hour, the compute resource fee for that hour will be at least **0.01 CNY**.

  • If the actual consumption is 0.01 CNY or more, you are billed for the actual amount.

  • If the actual consumption is less than 0.01 CNY, you are billed **0.01 CNY**.

• **Functions that do not run are not billed and can still achieve a "zero-cost" operation.**

Most Users Unaffected

• If your function invocation frequency is normal and one-time execution resource consumption is reasonable, your **bill will remain largely unchanged**.

• If a function is **not invoked or does not generate compute resource consumption** within an hour, it **will not trigger the minimum consumption rule or incur any fees**.

Low-Frequency/Extremely Low Consumption Scenarios Incur Small Fees

• Statistics show that more than half of our **users have functions that are in an extremely low-frequency invocation state**, such as functions that are invoked only a few times a day with very short running times and minimal memory usage per execution.

• Under the new rules, if these functions have a running record within an hour, they will be billed at **0.01 CNY/hour/function** and this amount will be added to the total daily fee, even if the actual consumption is much less than 0.01 CNY.

Extreme Case Example (For Reference)

• Assume you have **100 functions**, and each is **invoked once per hour** with extremely low consumption per invocation (less than 0.01 CNY):

  • **Pay-as-you-go users**: The maximum daily additional fee is 100 functions × 24 hours × 0.01 CNY = **24 CNY**.

  • **Subscription users**: This scenario might lead to an **increase in resource usage (GBs)**. If your current package has limited remaining resources, you should monitor your resource usage. If necessary, upgrade your package promptly to prevent functions from failing or scheduled tasks from being paused due to resource depletion.

Q1: Can I still achieve a "zero-cost" operation?

A1: **Yes, you can.** If a function is **not invoked** or **does not occupy any compute resources** within an hour, it will not incur any fees. This allows for a true pay-as-you-go experience.

Q2: Does the minimum consumption apply to all billable items?

A2: **No, it does not.** It **applies only to resource usage (GBs)**. Other billable items, such as invocation count and outbound traffic, are still billed based on actual usage, with no minimum consumption limit.

Q3: Why can't I see per-function, per-hour usage in the console?

A3: Currently, the EMAS Serverless console still **aggregates and displays usage and fees on a daily basis**. The new rule applies the minimum consumption on a per-function, per-hour basis only in the **backend billing engine**. The final amount is then merged into the daily bill. You do not need to perform any additional operations or view these details.

Q4: How can I reduce potential small fees?

A4: We suggest the following:

• Merge low-frequency functions that have similar functionalities to reduce the total number of functions.

• Regularly clean up unused test functions or deprecated functions.

• For low-frequency functions that must be retained, you may need to accept that they might incur small fees, which are typically a few CNY per month.