Sandboxes from a custom image start in half a second
Once an image is ready, a sandbox of the default size created from it starts from a started copy of the image: 481 ms from create to running at the median, from 3.7 s. See fast starts.
A new console
Home shows what runs now, with live CPU and memory and what just happened across every product. New, or ⌘K, finds any page or resource and starts anything, showing the command that does it. A sandbox's page opens a terminal in the browser and has Pause, Wake, Snapshot, Fork and Stop; Images and Volumes have their own pages; Usage & billing says how long your credit lasts and charts daily spend by product. See your account.
A 100-hour free trial
The free trial is now 100 hours of sandbox time, from 50, still with no card. Accounts already on the trial get the extra hours too; hours already used still count. See included usage.
Sandboxes up to 16 vCPUs and 64 GiB
A paid sandbox can now be as large as 16 vCPUs and 64 GiB of memory, at the same per-unit rates; a trial sandbox stays at 2 vCPU and 4 GiB. See pricing.
Faster network for paid sandboxes
A paid sandbox moves up to 500 Mbit/s, 200 Mbit/s sustained after its first 10 GiB, and 500 GiB a day. See the sandbox environment.
Outbound UDP to any port
Paid sandboxes send UDP to any public address and port: HTTP/3 and QUIC, DNS to a resolver you choose, time sync, game and media servers, WireGuard and other VPN clients. Private addresses are refused, a sandbox sends at most 50,000 datagrams a second, and a flow that gets no answer after 256 datagrams is closed. Trial sandboxes send TCP only. See networking.
50 sandboxes at once for a new paid account, then 100
A paid account runs up to 50 at once until 7 days after its first top-up clears or $50 of paid use has settled, whichever comes first, then 100. A paid account now runs 100 from its first top-up. See pricing.
Rules on a secret
On a paid account, a secret can name the methods and paths it goes to, such as GET /repos/acme/*; a request no rule allows goes out without it. See security.
Your own upstream proxy
A paid account can send its sandboxes' traffic, or only the hosts it names, through its own HTTP or HTTPS proxy, with one of its secrets as the proxy's password. Runtime's own checks still come first, and a proxy that fails refuses the connection rather than going direct. See networking.
Custom images get sudo, adduser and useradd
Every image Runtime builds, from a public image too, gives the sandbox user passwordless sudo, and the base image now carries adduser and useradd. A command in a sandbox from an image starts in the image's last WORKDIR (inside /workspace). Build logs number only the steps they log.
Close your account yourself
An owner closes the account at Close account or with POST /v1/account:close; runtime account close arrived in withruntime 0.7.0. See teams.
Usage per run
GET /v1/usage now gives each resource's name, start time, size and billed running time. In withruntime 0.7.0, runtime usage --csv exports one row per resource to the microdollar.