Skip to content
Warp

Support > Plans and billing

Compute usage

Warp-hosted compute charges depend on the sandbox's rate and metered lifetime, including setup, execution, and idle time.

Open in ChatGPT ↗
Ask ChatGPT about this page
Open in Claude ↗
Ask Claude about this page
Copied!

Compute usage pays for the sandbox used by an agent on Warp-hosted compute. Its cost is the sandbox’s rate multiplied by its metered lifetime, not its CPU utilization or billable agent hours. Find the rates by operating system and shape in Usage and billing.

When compute charges apply

Section titled “When compute charges apply”

Cloud runs on Warp-hosted compute incur compute charges, whether started from the Warp app, an integration, the CLI, or the Warp Platform API.

Local runs, CI jobs on your own runners, and self-hosted workers do not incur Warp-hosted compute charges. Platform charges can still apply.

Compute metering

Section titled “Compute metering”

For a newly created sandbox, compute is metered from creation to destruction. This includes setup, command execution, and idle time while the sandbox remains running. If a run receives a prewarmed sandbox, that run’s metering starts when the sandbox is assigned to it.

Elapsed time is charged proportionally, including partial minutes; it isn’t rounded up to whole minutes or hours. Compute can continue after the agent stops responding if the sandbox stays available. Compute charges are recorded when the sandbox is finalized.

For example, if a sandbox exists for 10 minutes and the agent has 6 billable minutes, compute uses the 10-minute lifetime. Platform usage uses the 6 billable agent minutes. See the example cloud run for the combined charge.

Section titled “Related pages”