Two-step sign-in
Turn on a code from an authenticator app after every sign-in, whichever way you sign in, under Settings → Two-step sign-in. Owners can require it of everyone in the account. See two-step sign-in.
Faster wakes, snapshots and stops
A paused sandbox runs its next command 588 ms after the call that wakes it at the median, down from 980 ms; a snapshot of a running sandbox is ready in 3.49 s, down from 6.54 s; a preview visit to a paused sandbox answers in 0.47 s, down from 0.77 s; and a stop answers the moment the sandbox is frozen. See speed.
An uptime promise, paid automatically
Paid accounts are promised 99% API uptime every calendar month, measured by the outside check on the status page. A month below it gives every paid account 10% of that month's charges back as service credit in the first week of the next month, with no claim to file. The terms now give 30 days' emailed notice before we end an account without cause, and the liability floor is $1,000 instead of $100. See the Uptime Promise.
Idle sandboxes pause themselves
A new sandbox pauses after 60 seconds with nothing happening in it, used or not (a persistent one only if you set an idle time), and pays only paused storage until the next request wakes it. A command or terminal still running, an open preview, port, SSH or tunnel connection, network traffic or CPU use keeps it awake. idlePauseSeconds now goes as low as 10 seconds, and 0 still turns it off. Sandboxes made before today keep their settings. See pause when idle.
Account-wide keys
An owner or admin can make a key that sees and uses every sandbox, snapshot, image and volume in the account, whichever key made it, as a Blaxel workspace key does: choose Everything in the account at API keys, switch an existing key from its row, or approve runtime keys create --account-wide. getOrCreate with a name another key holds then returns that sandbox. Keys made without it are unchanged. See keys in a team.
Switch from Blaxel in one import
Code written for Blaxel's sandbox SDK runs on Runtime after changing @blaxel/core to withruntime/blaxel (withruntime 0.8.0), or in Python blaxel.core to withruntime.blaxel (0.8.1). Processes, files, previews, snapshots, forks and the code interpreter carry over, and standby becomes a pause that keeps memory and processes until the next call wakes it. A switch from Blaxel now earns the switching credit: run runtime switch --from blaxel before your first top-up, and that top-up is matched, up to $100. See Runtime vs Blaxel.
Start a sandbox from the browser
A new account's Home offers Start a sandbox beside the agent prompt. It opens the sandbox with a shell running in the page, runs on the free hours, and pauses after an idle minute. It acts as an agent named Console, one for each member, shown on the API keys page like any other. See Get started.