Moving off Runloop

Runloop is winding down, with transition support ending on 13 November 2026. boxd keeps what Runloop devboxes did and adds memory: a machine wakes on a request with your processes still running.

Checked Oct 30, 2026Every claim sourcedRunloop ends 13 November 2026
“Runloop is winding down its services. Transition support for existing customers continues through November 13, 2026 at 11:59 PM PT.” Runloop docs
At a glance: boxd compared with Runloop
At a glanceboxdRunloop
Where boxd is ahead
Sleeps with processes keptYes, standby and hibernateNo; disk only
Starts from a snapshot, app runningYes · app answers in 1.19 sDisk only
Coding agents installedClaude Code, Codex, OpenCodeMounted via Agents API
SSHNative, own port per machineCLI tunnel
vCPU-hour$0.047, CPU used$0.108 + $250/mo Pro
Where Runloop is ahead
Largest, self-serve8 vCPU · 32 GiB16 vCPU · 64 GiB (custom)

Move to boxd when

  • You need a new home for devboxes before 13 November
  • You want suspend to keep memory, not only disk
  • You want agents installed rather than mounted

Sources for every Runloop cell are in the full table below · This page as Markdown, for agents

On this page · 2 min

Where boxd stands out

Memory survives a suspend

Runloop's suspend and snapshots keep the disk. boxd keeps memory too, so a woken machine has your processes running: the app answered an HTTPS request in 156 ms.

A new machine, app already up, in 1.19 s

Snapshot a machine with your stack running and every machine you create from it starts with that stack running: 1.19 s median from the create command to the app's first response. No boot script, no warm-up.

Claude Code, Codex and OpenCode are already there

Every machine boots with all three installed, plus headless Chrome, a desktop you can open in the browser, Docker and the boxd CLI. Your API keys stay outside the machine: the guest holds a placeholder and our proxy swaps in the real value.

No plan fee

Runloop's suspend and resume sat on its $250 a month Pro plan. boxd has no plan fee: $0.047 per vCPU-hour of CPU used, RAM on what's in use, and a hibernated machine pays only for disk.

Timings are medians of ten runs on our production cluster, from a client in the same datacenter. How we measured

What a devbox becomes

Most of what you built on Runloop has a direct counterpart. Move before 13 November 2026.

Runloopboxd
DevboxMachine
Blueprint (from a Dockerfile)Snapshot of a machine you set up once
Snapshot (disk)Snapshot or checkpoint (memory and disk)
Suspend / resumeStandby / hibernate, processes kept
wake_on_http tunnelEvery machine wakes on HTTPS or SSH
Tunnel URL per portHTTPS URL per port, custom domains
rli devbox sshssh my-machine.boxd
Agents API mountsClaude Code, Codex, OpenCode installed
Agent GatewaySecrets proxy (placeholder in the guest)

Side by side

Checked Oct 30, 2026. Each ↗ goes to where Runloop says it. boxd's column is from our code and our own measurements.

boxd compared with Runloop
FeatureboxdRunloop
The machine
Full VM, own kernelYes, every machineYes, microVM↗
Default size2 vCPU · 8 GiB · 100 GBNot published
Largest, self-serve8 vCPU · 32 GiB16 vCPU · 64 GiB (custom)↗
Root, systemd, DockerYes, plus nested virtualizationDocker via dedicated blueprints↗
CPU test (runs/s)12.6 (our run)8.93↗
Ready when you are
Sleeps with processes keptYes, standby and hibernateNo; disk only↗
Wakes on a requestYes, HTTPS or SSH · app answers in 156 msYes, wake_on_http↗
Starts from a snapshot, app runningYes · app answers in 1.19 sDisk only↗
Session limitNone1 h default, configurable↗
Built for agents
Coding agents installedClaude Code, Codex, OpenCodeMounted via Agents API↗
SSHNative, own port per machineCLI tunnel↗
HTTPS URL per portYes, plus custom domainsYes↗
Raw TCP inboundYes, 3 ports per machineNot published↗
Secrets kept outYes, swapped in at the proxyAgent Gateways↗
Price
vCPU-hour$0.047, CPU used$0.108 + $250/mo Pro↗
RAM GiB-hour$0.014, memory in use$0.0252↗
While asleepHibernated: disk onlySuspended: storage only↗
Also worth knowing
GPUsNoNot published
RegionsFrankfurt (US waitlist)Not published
SOC 2SOC 2 in progressNot published
SAML SSONoNot published
Egress allowlistYesNot published
Self-hostYes, free to 16 vCPUsDeploy to your VPC

What Runloop did that boxd doesn't

arm64. Runloop offered arm64 devboxes. boxd is x86-64 only.

Hostname egress rules. Runloop could lock a devbox to an allowlist of hostnames.

Deploy to your VPC. Runloop deployed into AWS, GCP or Azure accounts. boxd self-hosts on Google Cloud or AWS.

Questions

Is Runloop shutting down?
Runloop's own docs say it is winding down its services, with transition support for existing customers through 13 November 2026 at 11:59 PM PT.
How do I move a devbox to boxd?
Create a machine, run your blueprint's setup steps on it (the Dockerfile's RUN lines are a good start), start your services, and save it as a snapshot. Every machine created from that snapshot starts with them running. If your team needs help moving before the deadline, talk to us.