Runtime changelog, 5 October 2026

What shipped in Runtime Cloud on 5 October 2026: a hundred sandboxes at once from the first top-up, and time limits up to 24 hours; scheduled jobs run on the free trial, and an account holds 1,000 of them; downloads as fast as the server's link, and TCP ports five times faster; a snapshot of a running sandbox, in one call, at any size; and what a sandbox serves is billed as outbound traffic, and persistence costs nothing extra.

A hundred sandboxes at once from the first top-up, and time limits up to 24 hours

A paid account runs 100 sandboxes at once as soon as its first top-up clears, where a new one ran 50 for its first week; only a disputed payment, a suspension or an abuse report holds an account to 50. Paused and stopped sandboxes no longer count toward it, and an account keeps up to 1,000 in all. A time limit goes up to 24 hours, where it stopped at one, and a sandbox it stops reads stopReason time_limit where it read lease_expired, in the API, events, webhooks and OpenTelemetry export: code that compares with lease_expired should compare with both. A sandbox's disk is at most 400 GiB, and a larger diskMiB is refused at once, naming the limit. See how many at once.

Scheduled jobs run on the free trial, and an account holds 1,000 of them

A job's runs spend the trial's hours first, then credit, as a sandbox does; a run the trial 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. See what a job costs.

Downloads as fast as the server's link, and TCP ports five times faster

A sandbox's downloads are no longer capped: each sandbox shares its server's link, and when several are busy a paid account gets four times a trial's share. Uploads stay limited, more strictly on the trial (50 Mbit/s); paid uploads are 500 Mbit/s, 200 Mbit/s after 10 GiB, 500 GiB a day. A public TCP port now moves traffic at those paid figures, where it was 100 Mbit/s, 20 Mbit/s after 2 GiB and 50 GiB a day. See sandbox environment.

A snapshot of a running sandbox, in one call, at any size

POST :snapshot and runtime_snapshot (action create) take a running sandbox: they pause it, capture it and wake it, as a fork does, and answer once the capture is over. A sandbox with volumes is still refused. A copy of a disk snapshot takes the vCPUs, memory and disk you ask for, with a disk at least the saved one; a memory snapshot's copy is still the snapshot's size, and asking for another size answers 400. Every sandbox can now pause, fork and be snapshotted, and every stop keeps the sandbox's files. See snapshots and forks.

What a sandbox serves is billed as outbound traffic, and persistence costs nothing extra

For sandboxes created from today, what a sandbox sends back through a preview, a custom domain or a TCP port counts toward the account's 100 GiB a month free, then $0.02 per GB, like what it sends over its own connections; what visitors send in stays free. While a sandbox made from today runs, its disk past the first 10 GiB is billed at $0.08 per decimal GB per 30-day month, as a paused disk is; a disk of 10 GiB or less never pays it. A persistent sandbox no longer pays $0.11 per GiB for a reserved disk all the time: its disk is billed as any sandbox's, and persistent means only "keep it running". See pricing.