Serverless Cloud Function
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Billable Items and Billing Modes
- SCF Pricing
- User Guide
- Quota Management
- Managing Functions
- Web Function Management
- Concurrence Management
- Trigger Management
- A Custom Domain Name
- Version Management
- Permission Management
- Managing Monitors and Alarms
- Network Configuration
- Layer Management
- Execution Configuration
- Extended Storage Management
- Triggers
- API Gateway Trigger
- Websocket
- COS Trigger
- CLS Trigger
- Timer Trigger
- CKafka Trigger
- Apache Kafka Trigger
- Development Guide
- Developer Tools
- Serverless Cloud Framework
- Calling SDK Across Functions
- Third-Party Tools
- Malagu Framework
- Code Development
- Node.js
- Java
- Custom Runtime
- Deploying Image as Function
- Web Framework Development
- Practical Tutorial
- Business Development
- ServerlessFramework Practices
- API Gateway
- Using API Gateway to Provide API Service
- TRTC Practices
- COS Practices
- Acquire Image on COS and Create a Thumbnail
- MapReduce Method that Uses WordCount as an Example
- CKafka Practice
- CLS
- CLB Practice
- MPS
- Scheduled Task
- Video Processing
- Success Stories
- Online Video Industry
- API Documentation
- Making API Requests
- Function APIs
- Layer Management APIs
- Async Event Management APIs
- Other APIs
- FAQs
- Related Agreement
DocumentationServerless Cloud FunctionPurchase GuideBillable Items and Billing ModesPay-As-You-Go (Postpaid)
Pay-As-You-Go (Postpaid)
Last updated: 2024-12-02 20:27:11
Billing Mode
You can estimate your SCF usage and calculate the corresponding fees by using the SCF Price Calculator. For more information on SCF billing, see Pricing and Notes on Overdue Payment.
SCF is pay-as-you-go hourly in USD based on your actual usage in excess of the free tier and basic package. An event-triggered or HTTP-triggered function bill consists of the following parts (each part is billed according to its statistics and calculation method, and the fees are accurate to two decimal places in USD).
Note:
After three months of activation of SCF, you will no longer be entitled to a free tier, and the system will grant a basic package tier and automatically deduct 1.8 USD (by deducting 0.06 USD per day) every month. If you have activated SCF for less than three months and are entitled to a free tier or have valid packages or remaining resource packs, or the function resource usage, number of invocations, and public network outbound traffic in the last calendar month are all 0, the system will not deduct the basic package fees.
Event-Triggered Function | HTTP-Triggered Function |
Resource usage fees Invocation fees Public network outbound traffic fees Idle provisioned concurrency fees Basic package fees | Resource usage fees HTTP-triggered function invocation fees Public network outbound traffic fees Idle provisioned concurrency fees Basic package fees HTTP-triggered function response traffic fees (HTTP-triggered functions with different types of triggers have different billing modes. For more information, see HTTP-Triggered Function Billing.) |
For the unit prices of resource usage, invocations, public network outbound traffic, idle provisioned concurrency, and basic package, see Pricing.
Billing Principles
SCF fees will be incurred by the actual loading and execution of the function code. If the function code is not actually executed, no fees will be incurred unless provisioned concurrency and basic package are configured. Below is an example:
Scenario | Function Execution Status | Billable Usage | Billed |
A request error occurs due to an incorrect parameter, incorrect function name, or non-existent function. | Not executed | No | No |
An error occurs due to function execution timeout or function execution memory overrun. | Executed | Yes | Yes |
An error occurs due to a function code problem. | Executed | Yes | Yes |
A request error occurs due to concurrency overrun. | Not executed | No | No |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No