Rates
A box’s hourly price is the plain sum, with no tiers and no rounding:
What the standard sizes cost
The three sizes in the New Box dialog, plus the largest box your organization can request:
Two readings of that table matter.
Per invocation, boxes are almost free. A 30-second code-interpreter run on a Small box costs 5.55. Per-run cost is not where Cloud bills get large.
Per month left running, they are not. The gap between the last two columns is the whole cost story, and the next section is why it exists. Cost controls is how you close it.
To make a box cheaper, cut vCPU first: one vCPU-hour costs as much as 3.5 GiB-hours of memory or 280 GiB-hours of disk. Trimming disk is not worth the thought — it is 2–3% of a running box.
What each box state costs
A stopped box has given back its compute but still occupies its disk, and it is billed for that disk until the box is deleted.
One forgotten box is loose change. A hundred of them is 650 a month for nothing, and nothing clears them for you.
How the hours are counted
Compute and disk are charged over different intervals. The two clocks start together and stop at different moments:
Two of those moments are earlier than you might expect, and both are in your favor:
- Compute stops billing when the stop is requested, not when the box has finished shutting down. You do not pay vCPU or memory for the shutdown itself.
- Disk stops billing when deletion is requested, not when teardown completes.
Estimates and settlement
The New Box dialog quotes what your chosen size costs to run for one hour. Treat it as an estimate — your actual charge is settled from recorded usage, and the Usage tab is the authority on what you were charged. See Managing billing.Troubleshooting
Next steps
Cost controls
The two lifecycle controls that stop a finished box from charging you.
Wallet or a plan?
The usage level at which a subscription starts costing less.