Runtime changelog, 6 October 2026
What shipped in Runtime Cloud on 6 October 2026: a browser says when its sandbox is small for heavy apps; usage included every month, for every account, and jobs run on it; volume backups cost $0.02 per decimal GB per 30-day month; and leaving a block deletes the sandbox it made.
A browser says when its sandbox is small for heavy apps
browser:start now answers the sandbox's memoryMiB and, under 2 GiB, a hint: heavy apps such as Google Sheets, YouTube and StackBlitz need 2 GiB. Of 100 visits to ten heavy pages, 56 crashed for memory at 1 GiB, 20 at 1.5 GiB and none at 2 GiB. 1 GiB still suits light pages and scraping, and the browser starts at any size. runtime sandbox browser start prints the hint.
Usage included every month, for every account, and jobs run on it
Every account now gets 400 GiB-hours of machine memory, 100 vCPU-hours of active CPU, 10 GB of saved copies (snapshots, images, backups) and 5 GB of volumes each calendar month, enough for 100 hours of a 2 vCPU, 4 GB sandbox, with no card. It renews on the 1st (UTC), is used before credit and is never charged. New accounts get it in place of free hours; an account given free hours before 6 October keeps what is left of them, and has the included usage as well. GET /v1/usage lists each product's share under allowances, and trial gains offer and renewsAt. A scheduled job's runs spend it first, then credit, as a sandbox does; a run it cannot take, on an account without credit, waits with blockedReason credits. An account holds up to 1,000 jobs and 1,000 secrets for jobs, where it held 50 and 200. Credit, bought or given, now opens every paid feature but three: a kept top-up is needed only for ports beyond 80 and 443, public previews, and private networks and Tailscale. Without credit, an account runs at most 16 vCPU and 32 GiB at once across its sandboxes and image builds, beside 2 vCPU and 4 GiB each and eight at once; past it, a create, wake or build is refused with 409 no_credit_total_limit, whose message says what runs now. Seven codes are renamed, in the API, MCP, CLI and every SDK: trial_busy is now no_credit_running_limit, trial_capacity no_credit_capacity_full, invalid_trial no_credit_size_limit, trial_domain_limit no_credit_domain_limit, trial_build_limit no_credit_build_limit, trial_exhausted included_usage_used_up and trial_unavailable included_usage_unavailable; code that compares with an old name should compare with both until it updates. See included usage and what a job costs.
Volume backups cost $0.02 per decimal GB per 30-day month
They cost $0.012, which is below what keeping each backup in two places costs us: one copy beside the servers and one with a second provider. A backup made from now costs the new rate. One you already have keeps $0.012 until 7 November 2026, then costs the new rate too; a backup on the included usage stays free. Nothing else changes, and nothing is charged twice: a backup's hour that runs across the date is charged each part at its own rate. GET /v1/usage shows each backup's rate now under rates. See pricing.
Leaving a block deletes the sandbox it made
From the next release of the TypeScript and Python SDKs, the end of an await using or with block deletes a sandbox that Sandbox.create() made there, where it used to stop it and keep its disk, which bills. Create it with keep: true (Python keep=True) to stop it instead, as before. A sandbox the block got with get(), or one getOrCreate() found already there, is still only stopped. The drop-ins keep each rival's own block exit: withruntime/e2b (Python) kills, withruntime/vercel stops in TypeScript and deletes in Python.