Pay-per-Use Billing

Application Scenarios

FunctionGraph is suitable for various scenarios, such as real-time file processing, real-time data stream processing, web & mobile application backends, and AI applications.

Billing Items

The price of FunctionGraph consists of the price for requests, price for execution duration, and other fees. For details about each billing item, see Table 1.

**Table 1** Billing items
Billing Item	Description
Price for requests	Total number of times all of your functions are invoked.
Execution duration (non-reserved instances)	The execution duration fee depends on the execution duration and memory allocated to the function. The following describes how computing resources are calculated: FunctionGraph calculates the resource consumption of a function by multiplying the selected memory by the execution duration. The execution duration is calculated from the time when your function code starts to execute to the time when it returns a response or terminates. It is rounded up to the nearest 1 ms. If the duration is less than 1 ms, you will be billed for 1 ms.
Execution duration (reserved instances)	The execution duration fee depends on the execution duration and memory allocated to the function. The following describes how computing resources are calculated: FunctionGraph calculates the resource consumption of a function by multiplying the selected memory by the execution duration. The execution duration is calculated from the time when reserved instances are successfully created to the time when you call an API to release these instances. Reserved instances that stay alive for less than 1 minute will be billed for 1 minute. Those that stay alive for a longer time will be rounded up to the nearest 1s.
Other fees	Additional charges will apply if other cloud services, such as OBS and SMN, are used with FunctionGraph. For more information, see FunctionGraph Pricing Details.

Billed Usage Period

You pay only for what you use, and there is no minimum charge. FunctionGraph uses tiered pricing and is billed by day. Fees of a day are deducted after 03:00:00 of the next day. For example, the fees generated between May 11, 2023 00:00:00 and May 11, 2021 23:59:59 were deducted at around 03:00:00 of May 12, 2023.

"Requests" means the total number of requests for all functions. A request is recorded when a function is executed to respond to an event notification or invocation (including test invocations on the console).
If no reserved instances are used, the execution duration is calculated from the time when your function code starts to execute to the time when it returns a response or terminates. It is rounded up to the nearest 1 ms. If the duration is less than 1 ms, you will be billed for 1 ms. For example, if function A is executed for 0.5 ms and function B is executed for 2.3 ms, the execution duration of function A is 1 ms and that of function B is 3 ms.
If reserved instances are used, the execution duration is calculated from the time when instances are successfully created to the time when you call an API to release these instances. Reserved instances are metered by second. Instances that stay alive for less than 1 minute will be billed for 1 minute, and those that stay alive for a longer time will be rounded up to the nearest 1s. For example, if a reserved instance stays alive for 51s, you will be billed for 60s; if an instance stays alive for 60.5s, you will be billed for 61s.

Impact of Arrears

Arrears Reminder
The system will bill you for pay-per-use resources after each billing cycle ends. If your account goes into arrears, we will notify you by email, SMS, or internal message.
Impacts of Arrears
If your account is in arrears due to automatic fee deduction, you cannot create functions or perform any operations on resources.
- For details about top-up, see Topping Up an Account.