Pay-as-you-go charges are based on sandbox specifications, runtime state, and actual usage duration. After a sandbox starts, it can be in the active, light hibernation, deep hibernation, or destroyed state, and different states incur charges for different resources. If the Snapshot feature is used, the Snapshot billing rules apply.
Billing granularity
-
Billing granularity: Charges are calculated by the second. Usage shorter than 1 second is billed as 1 second.
-
Billing cycle: Charges are settled once per hour.
Subscription plans
Billing rules are described for the Eco, Std, and Pro subscription plans. Each plan supports a different set of sandbox states. The plans available for activation are as shown in the console.
|
Subscription Plan |
Applicable Scenarios |
Active |
Deep Hibernation |
Light Hibernation |
|
Eco (Economy) |
Suitable for AI startups, individual debugging, and Tool Use validation. |
Supported |
Supported |
Not supported |
|
Std (Standard), recommended |
Suitable for consumer-facing high-concurrency agents, complex computing, and large-scale sampling and reinforcement learning (RL) simulation. |
Supported |
Supported |
Not supported |
|
Pro (Professional) |
Dedicated resources with zero compute fluctuation. Suitable for production-grade RL training, quantitative finance, and long multi-agent workflows. |
Supported |
Supported |
Supported |
Billing rules
Active state
When a sandbox is in the active state, you are charged for virtual CPU (vCPU), memory, and disk. Disk usage includes a free allowance of 15 GiB.
Fee = vCPU fee + memory fee + disk fee
Billable disk size = max(0, disk size - 15) GiB
Light hibernation state
After a sandbox enters light hibernation, vCPU charges stop. You are charged only for memory and disk. Disk usage includes a free allowance of 15 GiB.
Fee = memory fee + disk fee
Billable disk size = max(0, disk size - 15) GiB
Light hibernation is supported only by the Pro plan.
Deep hibernation state
After a sandbox enters deep hibernation, vCPU and memory charges stop. You are charged only for disk based on the disk capacity occupied during deep hibernation. The 15 GiB free disk allowance does not apply during deep hibernation.
Deep hibernation disk usage = memory size + disk size
Fee = deep hibernation disk usage × disk unit price × duration
Destroyed state
After a sandbox is destroyed, no additional FC Agent Sandbox instance charges are incurred. Deep hibernation is not the same as destruction, and disk charges still apply during deep hibernation.
Snapshot fee
When the Snapshot feature is used, charges are calculated based on the Snapshot billing rules.
Snapshot storage usage = memory size + disk size
Fee = Snapshot storage usage × disk unit price × duration
Template pre-warming fees
Custom templates can be pre-warmed by calling API operations (Template Cache) to reduce the cold start time when a sandbox instance is created for the first time. Starting from 00:00 (UTC+8) on November 15, 2026, pre-warming fees are charged for custom templates. By default, no pre-warming fees are charged for official templates.
Pre-warming fee = Size of the pre-warmed data (GiB) × Disk unit price × Duration (hours). Disk unit price: USD 0.00031896/GiB/hour in the Chinese mainland, or USD 0.00025308/GiB/hour in China (Hong Kong) and regions outside China.
Pre-warmed data is evicted based on the least recently used (LRU) policy. After the data is evicted, no further fees are incurred.
Pay-as-you-go unit prices (international site)
The following pay-as-you-go unit prices apply to the international site and can be used for cost estimation. Actual bill amounts are subject to the cost and billing statements.
|
Subscription Plan |
vCPU Unit Price (USD/vCPU/hour) |
Memory Unit Price (USD/GiB/hour) |
Disk Unit Price (USD/GiB/hour) |
|
Eco |
0.00936 |
0.004608 |
0.00031896 |
|
Std |
0.01224 |
0.006012 |
0.00031896 |
|
Pro |
0.01872 |
0.009360 |
0.00031896 |
Disk unit price: 0.00031896 USD/GiB/hour in regions in mainland China, and 0.00025308 USD/GiB/hour in regions outside mainland China. Availability in regions outside mainland China is subject to official release announcements.
Billing examples (international site)
Eco active for 1 hour
Create an Eco sandbox with 2 vCPUs, 4 GiB of memory, and 15 GiB of disk. Keep it active for 1 hour, and then destroy it.
|
Billable Item |
Calculation |
Fee |
|
vCPU |
2 × 0.00936 × 1 |
USD 0.01872 |
|
Memory |
4 × 0.004608 × 1 |
USD 0.018432 |
|
Disk |
Within the 15 GiB free disk allowance |
USD 0 |
|
Total |
USD 0.037152 |
Std active for 1 hour, then deep hibernation for 1 hour
Create a Std sandbox with 2 vCPUs, 4 GiB of memory, and 30 GiB of disk. Keep it active for 1 hour, let it enter deep hibernation for 1 hour, and then destroy it.
|
Billable Item |
Calculation |
Fee |
|
vCPU (active) |
2 × 0.01224 × 1 |
USD 0.02448 |
|
Memory (active) |
4 × 0.006012 × 1 |
USD 0.024048 |
|
Disk (active) |
(30 - 15) × 0.00031896 × 1 |
USD 0.0047844 |
|
Disk (deep hibernation) |
(4 + 30) × 0.00031896 × 1 |
USD 0.01084464 |
|
Total |
USD 0.06415704 |
The disk capacity occupied during deep hibernation is 4 + 30 = 34 GiB.
Pro active, light hibernation, and deep hibernation for 1 hour each
Create a Pro sandbox with 2 vCPUs, 4 GiB of memory, and 30 GiB of disk. Keep it active for 1 hour, in light hibernation for 1 hour, and in deep hibernation for 1 hour. Then destroy it.
|
Billable Item |
Calculation |
Fee |
|
vCPU (active) |
2 × 0.01872 × 1 |
USD 0.03744 |
|
Memory (active) |
4 × 0.00936 × 1 |
USD 0.03744 |
|
Disk (active) |
(30 - 15) × 0.00031896 × 1 |
USD 0.0047844 |
|
Memory (light hibernation) |
4 × 0.00936 × 1 |
USD 0.03744 |
|
Disk (light hibernation) |
(30 - 15) × 0.00031896 × 1 |
USD 0.0047844 |
|
Disk (deep hibernation) |
(4 + 30) × 0.00031896 × 1 |
USD 0.01084464 |
|
Total |
USD 0.13273344 |
Overdue payments and resource release
-
Pay-as-you-go bills are typically settled once per hour. If your account balance is insufficient and an overdue payment occurs, the system sends an overdue payment notification.
-
After an overdue payment occurs, FC Agent Sandbox instances may be automatically stopped and no longer provide runtime capabilities.
-
The data retention period, release time, and recovery method of stopped sandboxes are subject to console notifications, cost and billing statements, or official release announcements.
As a best practice, destroy sandboxes that are no longer needed after tasks are complete, and set timeouts for production workloads to avoid unexpected charges caused by prolonged idle time.
FAQ
Will I still be charged after a sandbox is destroyed?
No additional FC Agent Sandbox instance charges are incurred after a sandbox is destroyed. Deep hibernation is not the same as destruction, and charges for the disk capacity occupied still apply during deep hibernation.
Is the free disk allowance shared across sandboxes?
No. Each sandbox independently includes a 15 GiB free disk allowance, which is available only in the active and light hibernation states.
How do I view usage and bills?
Usage details and bills of activated resources are available on the Alibaba Cloud cost and billing pages.