Skip to main content
A budget caps what one machine spends. Budgets are in US dollars; prices and costs are shown in Voyager credits. A machine has no budget unless you give it one.

A budget, and a ceiling

lease, resume and run take these flags. lease and status show the budget and what the machine has spent so far:
Ten minutes before a machine reaches its budget or its ceiling, its jobs carry a notice saying so. Save or copy off what matters then.

While a machine finishes

Voyager checks spend about once a minute, so a machine stops within about one check (a few cents) of its budget, a little before it rather than after. Once a machine reaches its budget (with a ceiling above it):
  • Jobs already running keep going. File transfers and snapshots still work, so you can pull results.
  • A new command is refused with 402 BUDGET_EXCEEDED and details.stage finishing. The message says what was spent and the command to raise the budget.
  • With nothing left running, the machine pauses at once. Otherwise it pauses when its last job ends, or at the ceiling, whichever comes first.
A paused machine keeps its disk. Resume it with a larger budget to go on: voyager cloud resume <machine> --budget 40.

Raise a budget

This works while the machine runs, and also while it finishes its jobs at the old budget: new commands start again. A budget only goes up, never below what the machine has spent or its current cap.

In the API

The lease body (POST /v1/machines) and POST /v1/machines/{id}/resume take budget_usd, budget_ceiling_usd and no_budget. Raise a running machine’s budget with POST /v1/machines/{id}/budget and {"budget_usd": 40, "budget_ceiling_usd": 60}. A machine’s billing shows: While it finishes, its jobs carry a BUDGET_REACHED notice.

Farms and estimates

  • A farm takes one budget for all its machines: see Farm a frame range.
  • To know what a Blender render will cost before you start, estimate it from a few sample frames: see Estimate a render.