sizes then lists only the sizes you may boot).
Limits
An ended sandbox (deleted, or failed to start) stays in
status for at least
30 days after it ends; then its record is removed. list shows every sandbox
that has not ended, however old, and list --all the newest ended ones too
(100 entries in all). Its charges stay in your billing history.
The numbers in a limit_reached message are your account’s own; list shows
the sandboxes that count. A refused start is reported by the CLI as:
upgrade_required, does not count against the start rate.
Prices
See sandbox pricing for every size and its hourly rate, the Linux formula, and worked examples.darkbloom-sandbox-cli sizes reads the
live list and is the price you pay.
Billing
- Per second while it runs: from the moment the sandbox is ready until its VM is gone (a stop takes seconds), at its size’s price, with a one-minute minimum per charge (each boot, and each fresh hour it moves to; the service never opens a charge just for a boot’s last minutes). Starting up and stopped sandboxes are free.
-
A hold per hour. Before each boot starts, Darkbloom holds an hour at its
size’s price from your balance, and settles it to the seconds the boot ran. A
boot that runs longer moves on to a fresh hour before each hour ends (one
more hour held, the last one settled), so every second is billed and nothing
is charged twice. If your balance cannot hold the first hour, the sandbox
does not start (
unfunded); if it cannot hold a later hour, the sandbox stops (a persistent one keeps its workspace). Add credits on the console’s Billing page. -
What you were charged. A sandbox’s cost shows two amounts: the estimate
at its size’s price, and what Darkbloom charged your balance (
cost.chargedin the API; Charged on the console’s sandbox page). The charge counts each hour once it is settled, so it trails the estimate while the sandbox runs. A sandbox on a Mac your own account provides is not charged. -
What it costs so far.
statusshows the sandbox’s price and both amounts on one line: -
When it stops.
statusshows when the service will stop a running sandbox (its idle limit and its maximum) and when it will delete a stopped one;listshows the same for each. -
Darkbloom’s own billing problems are not yours: if Darkbloom cannot
charge for more than 10 minutes, a running sandbox stops (
billing_lapsed) with its workspace kept, persistent or not, and you resume it later. The CLI saysa problem on Darkbloom's side, not the account's.

