MU Billing Overview
MU is the unified usage billing unit of EdgeOne Makers. This document describes the applicable scope of MUs, pricing, MUs included in plans, and the conversion ratios and calculation methods for each resource.
MU Scope of Application
Applicable resources: Usage of compute and storage resources within the platform is converted to MUs at a fixed ratio and then billed. For specific billable items, see Conversion Ratios. Security Acceleration and Edge Functions follow the EdgeOne metering method and do not use MUs. For details, see Resource Billing Description.
Applicable plans: Billing usage for the Pro and Business plans is converted to MUs. The free edition does not use MUs, and each quota is fixed and available until exhausted.
MU Pricing
Site | Price |
China Site | CNY 1 / 1,000 MUs |
Tencent Cloud | USD 0.143 / 1,000 MUs |
MUs that exceed the included quota in the Pro plan are billed at this price on a postpaid basis. They are settled hourly, while storage resources are settled daily. See below for details. Pricing and settlement methods for the Business plan are subject to the contract.
How to Use MU in Each Plan
Package | MU Usage |
Pro | The plan fee is converted into a monthly quota of 140,000 MUs based on the MU price, which is shared by all resources billed by MUs: After the quota is exhausted, usage is billed at the MU price on a postpaid basis, and the service remains uninterrupted. The quota resets monthly. Any unused portion is not carried over or refunded. After the plan expires, the included MUs will no longer be applied. For details, see Overdue Payments and Plan Expiration. |
Commercial | No unified MU quota is set. The quota, billing method, and settlement cycle of each resource can be customized based on business needs, subject to the contract. |
Conversion Ratio
Category | Billable Item | Conversion Ratio | Metering Description |
Build | Build duration | 0.2 units / vCPU-s | Billing starts when a build is generated, including failed builds. |
| Total Project Storage | 5 units / GB / day | Storage usage exceeding the plan quota is billed based on the storage amount. For the settlement method, see below. |
Cloud Functions | Call quantity | 20 units / 10,000 invocations | Billing is based on the number of function invocations, regardless of the response status code. Requests served from the cache are not counted. |
| Memory Duration | 0.1 units / GB-s | Including time spent waiting for I/O |
| Transmitting data | 1 unit / MB | Public network outbound traffic of functions |
Agents | Number of Executions | 20 units / 10,000 invocations | Counted by the number of Agent invocations |
| Memory Duration | 0.1 units / GB-s | Including time spent waiting for I/O, such as network requests, database queries, or model invocations |
| Transmitting data | 1 unit / MB | Public network outbound traffic of Agents |
Sandbox | Memory Duration | 0.04 units / GB-s | Memory usage of Sandbox instances |
| CPU Duration | 0.2 units / vCPU-s | CPU usage of Sandbox instances |
Blob | Storage Space | 5 units / GB / day | Storage usage exceeding the plan quota is billed based on the storage amount. For the settlement method, see below. |
| Simple Operations | 20 units / 10,000 invocations | Read Operations |
| Complex Operations | 200 units / 10,000 invocations | Write and list operations are billed. Delete operations are not billed. |
| Transmitting data | 0.3 units / MB | Traffic generated by accessing Blob |
Note:
The minimum billing unit for duration-based billable items is 0.01 MU.
How Storage Resources Are Calculated
Storage resources are billed based on average storage usage, not peak usage. The Pro plan includes a certain amount of storage space, and only the excess portion consumes MUs:
The system samples storage usage every 5 minutes, resulting in 288 sampling points per day.
Daily storage cost = Sum of all sample values for the day ÷ 288 × Daily unit price. The usage of the previous day is settled on the next day.
Therefore, for the same 100 GB stored, data stored at the beginning of the month consumes more MUs in that month than data stored at the end of the month. After data is deleted, subsequent samples are no longer counted, and charges already incurred will not be reversed.
Calculation Examples
Assume that a Pro plan generates the following usage within a month:
Billable Item | Usage | Conversion | MU Consumed |
Cloud Functions invocations | 10 million times | 10 million ÷ 10,000 × 20 | 20,000 |
Cloud Functions memory duration | 1 million GB-s | 1 million × 0.1 | 100,000 |
Build duration | 100 builds, each with 4 vCPU × 300 seconds | 120,000 vCPU-s × 0.2 | 24,000 |
Total | | | 144,000 |
This cycle includes 140,000 MUs, with an excess of 4,000 MUs. Calculated based on the China site, the excess usage costs 4,000 ÷ 1,000 × CNY 1 = CNY 4.
Viewing MU Usage
You can view the total MUs, used MUs, and consumption details of each resource for the current cycle in Plan Consumption on the right side of the project list page. For details, see Plan Consumption and Usage.
