Reference

Billing

Prepaid credits, drawn down by the second for CPU, memory and storage, and by the byte for data sent out.

Nanite runs on prepaid credits. One credit is one US dollar. An owner or admin buys credits on the Billing page of the console, and usage draws them down as it happens. There are no seats, plans or minimums.

Rates

Meter Rate Per second What counts
CPU $0.072 per vCPU hour $0.00002 per CPU second CPU time your code uses. An idle core costs nothing.
Memory $0.0432 per GB hour $0.000012 per GB second Memory in use while the sandbox runs.
Storage $0.15 per GB month $0.000205 per GB hour The disk and its checkpoints, counting only blocks that were written.
Network $0.15 per GB out by the byte Data the sandbox sends to the internet. Data coming in is free.

A GB here is 230 bytes. A month is 730 hours. Network counts the bytes your code sends, not the headers the network adds.

CPU and memory are billed only while a sandbox is running. A warm or cold sandbox costs only its storage.

An example month

One agent sandbox that works two hours a day and sleeps the rest, using half a vCPU and 1 GB of memory while it works, with 2 GB written to its disk and 1 GB sent out:

Line Cost
CPU: 0.5 vCPU, 2 h a day, 30 days $2.16
Memory: 1 GB, 2 h a day, 30 days $2.59
Storage: 2 GB for the month $0.30
Network: 1 GB sent out $0.15
Total $5.20

When credits run out

A workspace needs at least 0.01 credits to start or wake a sandbox. Below that:

  • creating or waking a sandbox answers 402 insufficient_credits, with your balance in millionths of a credit,
  • running sandboxes are stopped, and their disks and checkpoints are kept,
  • stopping, getting, listing and deleting still work.

Buy credits and sandboxes can run again on the next request.

Seeing usage

The console shows usage for every sandbox, second by second, and what each one cost this month.