Resource Billing Description
This document describes the metering methods for each billable item of EdgeOne Makers by resource, and how overage beyond the plan quota is handled.
For the quota of each plan, see Plan Comparison.
For MU pricing and conversion ratios, see MU Billing.
Billing Methods Overview
Resource | Pro | Commercial |
Secure acceleration | Billed as specified in the contract | |
Edge Functions | | |
Build (build duration, total project storage, and more) | MU. Postpaid at MU rates after the quota is exceeded. | Billed as specified in the contract |
Cloud Functions | | |
Agents | | |
Sandbox | | |
Blob | | |
KV | Not billed for now | Not billed for now |
Models | | |
The free edition incurs no fees, and resources are restricted after the quota is exhausted. For Business plan options, contact us.
Quotas for quantities and specifications, such as the number of projects, custom domains, and concurrent connections, are not billed on a pay-as-you-go basis. For the limits of each plan, see Plan Comparison. In the Business plan, additional projects and custom domains can be purchased.
Security Acceleration
Billable Item | Measurement Method |
Secure acceleration traffic | Traffic generated by the platform in response to client requests, in GB |
Secure acceleration requests | Number of requests sent from clients to the platform |
After the Pro plan exceeds its quota, overage is billed at the EdgeOne Pay-as-You-Go. Traffic prices vary by region, and for region classifications, see Billing Regions.
Consistent with EdgeOne, billing is based on "clean traffic": requests and traffic blocked by security protection are not metered, while unblocked requests, such as those in observation mode or matching exception rules, are still metered. For details, see Clean Traffic Billing.
Edge Functions
Billable Item | Measurement Method |
Number of Executions | Number of Times a Function Is Triggered |
CPU time | Actual CPU time occupied during function execution, excluding time spent waiting for network I/O, in ms |
After the Pro plan exceeds its quota, overage is billed at the EdgeOne overage rates without consuming MU.
After the free edition quota is exhausted, function requests will be terminated, and no fees will be incurred.
After the plan expires, the included quota will no longer be applied. For details, see Overdue Payments and Plan Expiration.
Build
Billable Item | Measurement Method |
Build duration | Actual build duration × number of vCPUs for build compute power, in vCPU-s |
Total Project Storage | Storage space occupied by artifacts from all valid deployments of projects in the space |
All builds are counted toward the build duration based on the actual build time, including failed and canceled builds. Canceled builds are calculated based on the duration that elapsed before cancellation.
Higher build compute power consumes more build duration for the same elapsed time. For example, for a 5-minute build, the vCPU-s consumed by 8-core compute power is twice that of 4-core.
Expired historical deployments are not counted toward the total project storage.
Total project storage is billed based on average storage usage. For the calculation method, see MU Billing Instructions.
Cloud Functions
Billable Item | Measurement Method |
Number of Executions | The number of function invocations, regardless of the response status code. Requests served from the cache are not counted. |
Memory Duration | Function execution duration × memory specification, in GB-s |
Transmitting data | Public network outbound traffic of functions, in MB |
Because memory duration includes waiting time, time-consuming external requests in functions, such as calling third-party APIs or querying databases, increase memory duration.
Functions are metered as soon as they are actually invoked, including invocations that fail or time out. Requests that are not executed due to rate limiting or other reasons are not metered.
Agents and Sandbox
Agents and Sandbox are metered separately. Agents do not necessarily create a Sandbox when executing tasks. Sandbox usage is incurred only when Sandbox is actually used.
Resource | Billable Item | Measurement Method |
Agents | Number of Executions | Number of times Agents are executed |
| Memory Duration | Agents runtime × memory specification, in GB-s |
| Transmitting data | Public network outbound traffic of Agents, in MB |
Sandbox | Memory Duration | Sandbox instance runtime × memory specification, in GB-s |
| CPU Duration | Sandbox instance runtime × number of vCPUs, in vCPU-s |
Token usage generated by Agents calling models is not counted toward Agents fees and is handled according to the rules of Models.
Sandbox is metered based on actual running duration. Release it promptly after tasks are completed, or set a reasonable timeout.
Blob
Billable Item | Measurement Method |
Storage Space | Amount of stored data, billed based on average storage usage |
Simple Operations | Number of Read Operations |
Complex Operations | Write and list operations are billed by the number of operations. Delete operations are not billed. |
Transmitting data | Traffic generated by accessing Blob, in MB |
The Pro plan includes a certain amount of storage space, and only the excess portion consumes MUs.
Storage usage is sampled every 5 minutes and billed based on the daily average. After data is deleted, subsequent samples are no longer counted, and charges already incurred will not be reversed.
KV and Models
KV and Models are not billed for now and are used according to the quota of each plan. If you use your own model provider keys in Models, model call fees are charged by the model provider and are unrelated to Makers.
Usage Data Delay
Usage data in the console may be delayed by approximately 3 hours due to data collection and calculation methods. The final bill prevails.
