Tencent Cloud EdgeOne
- Release Notes and Announcements
- Security Announcement
- Announcements
- Product Introduction
- Purchase Guide
- Billing Items
- Basic Service Fees
- Value-added Service Fees
- Instructions for overdue and refunds
- Getting Started
- Domain Service&Origin Configuration
- Domain Service
- Hosting DNS Records
- Domain Connection
- Traffic Scheduling
- HTTPS Certificate
- HTTPS Configuration
- SSL/TLS Security Configuration
- Origin Configuration
- Load Balancing
- Related References
- Origin-pull configuration
- Related References
- Site Acceleration
- Access Control
- Cache Configuration
- EdgeOne Cache Rules
- Cache Configuration
- Clear and Preheat Cach
- File Optimization
- Network Optimization
- HTTP/3(QUIC)
- QUIC SDK
- Modifying Header
- Modify the response content
- Rule Engine
- Related References
- Request and Response Actions
- DDoS & Web Protection
- DDoS Protection
- Configuration of Exclusive DDoS protection Rules
- Related References
- Web Protection
- Rate Limiting
- Bot Management
- Related References
- Related References
- Image&Video Processing
- Edge Functions
- Runtime APIs
- Streams
- Images
- Sample Functions
- Best Practices
- L4 Proxy
- Obtaining Real Client IPs
- Obtaining Real Client IPs Through Protocol V1/V2
- Data Analysis&Log Service
- Log Service
- Real-time Logs
- Data Analysis
- Related References
- Legacy Console Relevant Documentation
- Security Analysis
- Alarm Service
- Version Management
- Site and Billing Management
- Site Management
- General Policy
- Terraform
- Practical Tutorial
- Automatic Warm-up/Cache Purge
- Resource Abuse/hotlinking Protection Practical
- HTTPS Related Practices
- Acceleration Optimization
- Scheduling Traffic
- Origin-pull Based On User IP/geolocation
- APK Dynamic Packaging
- Data Analysis and Alerting
- API Documentation
- Making API Requests
- Site APIs
- Acceleration Domain Management APIs
- Site Acceleration Configuration APIs
- Edge Function APIs
- Alias Domain APIs
- Security Configuration APIs
- Layer 4 Application Proxy APIs
- Content Management APIs
- Data Analysis APIs
- Log Service APIs
- Billing APIs
- Certificate APIs
- Load Balancing APIs
- Diagnostic Tool APIs
- Custom Response Page APIs
- DNS Record APIs
- Content Identifier APIs
- Old Version APIs
- Version Management APIs
- Common Guidelines
- FAQs
- Troubleshooting
- Tool Guide
- Speed Test Tools
- Diagnostic Tool
- Agreements
DocumentationTencent Cloud EdgeOne Purchase Guide Billing ItemsValue-added Service FeesEdge Function Execution Fee (Pay-As-You-Go)
Edge Function Execution Fee (Pay-As-You-Go)
Last updated: 2025-03-31 16:53:57
Notes:
For the official billing time of edge function execution fees, please refer to [Tencent Cloud EdgeOne] Announcement on Edge Function Billing Adjustment.
Edge Functions provide a serverless code execution environment on EdgeOne edge nodes. You only need to write your business function code and set trigger rules, without configuring and managing servers or other infrastructure, to run your code elastically and securely on edge nodes close to users. Edge Functions are supported in all EdgeOne packages, each with a certain limit of edge function executions. Exceeding the limit will result in postpaid bills in two dimensions: Edge Function Request Count and Edge Function CPU Time.
Edge Function Request Count: Refers to the total number of external HTTP/HTTPS requests handled by the edge function.
Edge Function CPU Time: Refers to the CPU time consumed by the edge function script to execute code logic (in milliseconds), excluding the time spent waiting for I/O.
Edge Function Quotas Included In Different Packages
Each package includes a certain amount of edge function quotas after purchase, and the quotas for different packages are as follows:
Billing Item | Trial | Personal | Basic | Standard | Enterprise |
Edge function request count (times) | 100,000 | 3 million | 20 million | 50 million | |
Edge Function CPU Time (ms) | 100,000 | 3 million | 20 million | 50 million |
Notes:
1. The period for edge function quotas is the same as the update cycle of packages:
Trial version packages cannot be renewed, and quotas will not be issued once exhausted.
Personal/Basic/Standard Package Cycle: Valid from day T to day T of the following month. After the package is renewed, the limit is reissued.
Enterprise edition package cycle: Corresponding quotas are reissued on the 1st of each month.
2. The remaining quota of the edge function is not cumulative to the next month, and the usage quota is reissued every month.
3. If a package upgrade occurs, the change in edge function quotas will be consistent with the quota usage change described in the package upgrade notes. For details, see Plan Upgrade Guide.
Edge Function Execution Fee
After the edge function quota of different package versions is exhausted, it will automatically switch to postpaid settlement. The settlement method and price of postpaid are as follows:
Billing Item | Price | Trial/ Personal/ Basic/ Standard | Enterprise |
Edge function request count (USD/million times) | 0.2389 | Hourly | Monthly |
Edge Function CPU Time (USD/million milliseconds) | 0.0155 | | |
Example: Purchase a Personal Plan To Enable the Edge Function, Resulting In 10 Million Edge Function Requests and 10 Million Milliseconds Of CPU Time.
Assuming a user purchased and enabled the personal plan on March 3rd, there were 2 million edge function requests and 2 million milliseconds of CPU time between March 3rd 19:00:00 - 20:00:00, and 2 million edge function requests and 2 million milliseconds of CPU time between March 3rd 20:00:00 - 21:00:00.
The limits for the personal plan edge function are 3 million requests and 3 million milliseconds of CPU time, so the billing settlement for these two hours is as follows:
After offsetting the usage generated from March 3rd 19:00:00 - 20:00:00, there are still 1 million remaining request limit and 1 million milliseconds of CPU time limit. The excess fee for this hour: 0.
From March 3rd 20:00:00 - 21:00:00, the remaining credit was insufficient to offset the generated usage. The excess fee for this hour: (2 million - 1 million) * 0.2389 USD/million + (2 million milliseconds - 1 million milliseconds) * 0.0155 USD/million milliseconds = 0.2389 + 0.0155 = 0.2544 USD.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No