Skip to main content
Compute billing stops on its own. Disk billing does not. These are the controls that close that second loop.

Which half of the bill each control closes

Two lifecycle controls decide how long each half of the bill runs, and their defaults pull in opposite directions: So by default you stop paying for compute automatically, and you pay for disk forever. Setting auto_delete closes that second loop.

Cap a box’s lifetime

auto_delete must be larger than auto_stop when both are non-zero. This example gives a box 15 idle minutes to be reused, then deletes it an hour after it stops:
See Lifecycle on Cloud for the full semantics of these fields, including how auto_resume brings a stopped box back.
From the CLI you can set only half of this. boxlite create accepts --auto-stop, and takes a friendlier duration than the SDK — 30s, 15m, 2h, 7d rather than raw seconds:
--auto-delete is refused on a box made this way, because boxlite create makes a detached box:
To close the disk half of the bill, set auto_delete from an SDK, as above.

Keep the data, drop the disk

auto_delete is uncomfortable when the box holds something you need later. That is what volumes are for, and it happens to be the cheapest arrangement available:
  • A managed volume is not part of a box’s metered resources. Mounting one adds nothing to the box’s hourly price.
  • A stopped box is billed for its disk for as long as it exists.
So when you want to keep results but not keep paying, write them to a volume and let the box go. See Volumes.

Next steps

Pricing

Rates, what the standard sizes cost, and how the hours are counted.