Menu

Awake-time billing for agent sandboxes: what you pay for and what you don't
📰

Awake-time billing for agent sandboxes: what you pay for and what you don't

DEV Community: cloud·Sandscale·about 2 hours ago
#v4whp0QG
#devtocloud#devto#dev#vcpu#awake
Long article (1470 words) — no AI summary yet.
Reading 0:00
15s threshold

Originally published on sandscale.dev .

An agent run is mostly waiting. It calls a model, waits for tokens, runs a command for a few seconds, waits for the next tool call, and sometimes sits for an hour because a person has to approve something. If a sandbox bills for every second it exists, you pay for that waiting. Sandscale bills for the time the box is awake instead. This post explains what that means, how the numbers work, and where the model stops being cheaper than you might assume.

What "awake vCPU-hour" means

The unit is one vCPU running for one hour while the box is awake. A box that is paused, or idle between tool calls, does not count. For how metering works in detail, see pricing .

Sandscale's own example: a 2 vCPU agent box that is open for 10 hours and awake 10% of the time uses 2 awake vCPU-hours (2 vCPU × 1 awake hour).

So the formula is:

awake vCPU-hours = vCPU count × hours awake

Enter fullscreen mode

Exit fullscreen mode

What is free and what isn't

Free:

Paused time.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.