Skip to content

POSTEngineering log

All posts
pricingsandbox0-cloudpersistent-sandboxesai-agents

AI Sandbox Pricing: Compute, Storage, and Paused Time

Written by
Sandbox0 Team
Published
Updated

An agent can finish today's work without being finished with its workspace. The repository, installed dependencies, generated files, and intermediate results may all be useful when the next task arrives.

Updated November 6, 2026: Sandbox0 Cloud charges for running compute and retained incremental storage. Storage costs $0.02 per GiB-month, prorated over 730 hours. Shared base images and platform recovery retention are excluded. Pausing stops compute charges; retained data continues to accrue storage charges.

There is no paused sandbox count limit on Sandbox0 Cloud. Retained storage remains billable, and active capacity and available credit still govern resume.

For the execution and persistence model behind this bill, start with the AI sandbox guide.

What You Pay For#

Compute costs $0.015 per GiB-hour, billed by the second using the sandbox's effective memory limit and running time. The hourly rate makes the price easy to compare; it does not impose a one-hour minimum. CPU is included in that rate, with CPU limits still applying.

ResourceCurrent price
Running compute$0.015 per GiB-hour, billed by the second
Incremental RootFS and retained memory checkpoint data$0.02 per GiB-month, prorated over 730 hours
Snapshot and fork references to the same dataCounted once within a team
Shared base images and platform recovery retentionExcluded
Paused sandboxesStorage only; no compute charge
Network ingressFree
Network egressFree for now
Object-store GET and PUT requestsFree

Running time includes time when the sandbox is idle or waiting for input. Billing follows the effective memory limit, rather than the amount of memory a process happens to use. Pause the sandbox when you want compute charges to stop. They begin accruing again when it resumes running.

With optional memory burst, a 4 GiB sandbox can authorize a temporary 6 GiB limit. Compute is billed at 6 GiB while that limit is in effect and returns to 4 GiB after safe shrink; enabling the allowance alone does not bill the entire session at 6 GiB.

The pricing page lists the current rates and billing boundaries.

A Workspace You Can Come Back To#

Consider a sandbox configured with 4 GiB of memory. It runs for a total of 10 hours, across one session or several, and retains 20 GiB of persistent incremental data for one 730-hour storage month. You pause it between tasks.

Its compute charge is:

text
4 GiB × 10 running hours × $0.015/GiB-hour = $0.60

The 20 GiB of retained incremental data adds $0.40 for one storage month. Paused time adds no compute charge. Network traffic and object-store requests add $0.00 at the current rates. The example total is $1.00, with no monthly plan fee added. The shared base image is excluded from these 20 GiB.

You can keep the workspace ready for the next task without paying for the compute time it spends paused. Retained storage remains billable. When you resume it, the next running interval adds to your compute usage.

Paused Retention and Active Capacity#

Sandbox0 Cloud does not limit how many paused sandbox identities a team can retain. Paused sandboxes do not occupy active sandbox capacity or incur compute charges; their retained incremental data still contributes to storage usage.

Resuming a sandbox is subject to active capacity, available compute credit, and runtime availability. An idle sandbox that remains running continues to accrue compute charges. Configure pause and retention policies for your application; remove sandboxes when their retained data is no longer needed.

The pricing page lists current rates and quotas. Check your team's effective active capacity in the Dashboard.

Built for Work That Continues Later#

An agent's useful lifetime often extends beyond a single run. It may return to a project tomorrow, wait for a person to review a change, or reuse an environment prepared for a particular customer.

Running time contributes compute charges; retained incremental RootFS and memory checkpoint data contribute storage charges. The earlier free-storage pricebook remains part of billing history. Usage from before the change retains its historical rates.

Start building, or visit the pricing page to plan your workload.

See also