tencent cloud

Serverless Cloud Function

Release Notes and Announcements
Release Notes
Announcements
User Guide
Product Introduction
Overview
Related Concepts
How It Works
Strengths
Scenarios
Related Products
Purchase Guide
Billing Overview
Billing Mode
Billable Items and Billing Modes
Function Computing Power Support
Free Tier
SCF Pricing
Billing Example
Payment Overdue
Getting Started
Creating Event Function in Console
User Guide
Quota Management
Managing Functions
Web Function Management
Log Management
Concurrence Management
Trigger Management
Function URL
A Custom Domain Name
Version Management
Alias Management
Permission Management
Running Instance Management
Plugin Management
Managing Monitors and Alarms
Network Configuration
Layer Management
Execution Configuration
Extended Storage Management
DNS Caching Configuration
Resource Managed Mode Management
Near-Offline Resource Hosting Model
Workflow
Triggers
Trigger Overview
Trigger Event Message Structure Summary
API Gateway Trigger
COS Trigger
CLS Trigger
Timer Trigger
CKafka Trigger
Apache Kafka Trigger
MQTT Trigger
Trigger Configuration Description
MPS Trigger
CLB Trigger Description
TencentCloud API Trigger
Development Guide
Basic Concepts
Testing a Function
Environment Variables
Dependency Installation
Using Container Image
Error Types and Retry Policies
Dead Letter Queue
Connecting SCF to Database
Automated Deployment
Cloud Function Status Code
Common Errors and Solutions
Developer Tools
Serverless Web IDE
Calling SDK Across Functions
Third-Party Tools
Code Development
Python
Node.js
Golang
PHP
Java
Custom Runtime
Deploying Image as Function
Web Framework Development
Deploying Framework on Command Line
Quickly Deploying Egg Framework
Quickly Deploying Express Framework
Quickly Deploying Flask Framework
Quickly Deploying Koa Framework
Quickly Deploying Laravel Framework
Quickly Deploying Nest.js Framework
Quickly Deploying Next.js Framework
Quickly Deploying Nuxt.js Framework
Quickly Deploying Django Framework
Use Cases
Overview
Solutions with Tencent Cloud Services
Business Development
TRTC Practices
COS Practices
CKafka Practice
CLS
CLB Practice
MPS
CDN
CDWPG
VOD
SMS
ES
Scheduled Task
Video Processing
Success Stories
Tencent Online Education
Online Video Industry
Tencent Online Education
Best Practice of Tencent IEG Going Global
API Documentation
History
Introduction
API Category
Making API Requests
Other APIs
Namespace APIs
Layer Management APIs
Async Event Management APIs
Trigger APIs
Function APIs
Function and Layer Status Description
Data Types
Error Codes
SDK Documentation
FAQs
General
Web Function
Billing FAQs
Network FAQs
Log FAQs
SCF utility class
Event Handling FAQs
API Gateway Trigger FAQs
Related Agreement
Service Level Agreement
Contact Us
Glossary
DocumentaçãoServerless Cloud FunctionPurchase GuideBillable Items and Billing ModesPay-As-You-Go (Postpaid)

Pay-As-You-Go (Postpaid)

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 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

Anterior: Subscription PackagesPróximo: Function Computing Power Support

Ajuda e Suporte

Esta página foi útil?

comentários