Skip to content
Spinbox is experimental: APIs change and data may be lost. Status lists what is built and what proves it.

spin-stack · workspaces you own

Workspaces for people. A sandbox for agents, as a side effect.

Every workspace is a virtual machine of its own, in your own AWS account, built from parts Linux and QEMU already have. Be root and break anything: a snapshot brings it back, running processes and all, a diff shows what changed, and the network stays closed until you open it. Built for people to work in, which is what makes it a good place for an agent too.

A workspace's disk, as layersThe image at the bottom, a snapshot called clean, a snapshot called after holding the three files that changed, and on top the layer the running workspace writes. A bracket marks the diff between clean and after.image · ubuntusnapshot · cleansnapshot · after · keptrunning · writes herediffrestore

$ spin snapshot diff demo <after-id> --from <clean-id> --under /etc

  • A/etc/greeting
  • M/etc/hosts
  • D/etc/issue

A separate machine reads the two and lists every file added, modified or removed.

  1. How we know →
  2. How we know →
  3. How we know →
  4. How we know →
demo — spin
$ spin workspace create --name demo --wait
$ spin snapshot create demo --description clean --with-memory --wait
$ spin exec demo -- sh -c 'echo hello > /etc/greeting; rm /etc/issue; echo "# edited" >> /etc/hosts'
$ spin snapshot create demo --description after --wait
$ spin snapshot diff demo <after-id> --from <clean-id> --under /etc
A  /etc/greeting
M  /etc/hosts
D  /etc/issue
$ spin workspace restore demo <clean-id> --with-memory
$ spin workspace delete demo
$ spin workspace create --name demo --wait
$ spin snapshot create demo --description clean --with-memory --wait

$ spin exec demo -- sh -c 'echo hello > /etc/greeting; rm /etc/issue; echo "# edited" >> /etc/hosts'
$ spin snapshot create demo --description after --wait

$ spin snapshot diff demo <after-id> --from <clean-id> --under /etc
A  /etc/greeting
M  /etc/hosts
D  /etc/issue

$ spin workspace restore demo <clean-id> --with-memory
$ spin workspace delete demo
Where the boundary is: people and agents reach the proxy; the control plane, the runners, the buckets and the keys are the module's, in your account and your region.
Where the boundary is: people and agents reach the proxy; the control plane, the runners, the buckets and the keys are the module's, in your account and your region. Its source.
96features builteach with a test or a command that proves it
83with an end-to-end testby tests against a real runner
17known limitswhat it does not do, each on the status page
2not built yeteach an item of the roadmap

96 features built, each with a test or a command that proves it, 83 of them with an end-to-end test, 2 not built yet and 17 limits, on the status page. An installation runs release v20261027.01; the reference is generated from spin v20261114.01 (51f7e0dea).

  • AWS only. One OpenTofu module installs Spinbox in your account. There is no hosted version.
  • x86-64 only. Runners are x86-64 machines with nested virtualization.
  • Linux guests only. A workspace boots the kernel Spinbox provides.
  • No GPUs. A preset names the class of runner its workspaces run on, and no class hands a workspace a GPU.
  • One region, one control plane. An installation lives in one AWS region.

Each answer is a limit row of the status page. The rest are on Limitations.

Workspaces you own, from the first snapshot.

What it is for, what it costs to run, how to try it on one machine, and how to install it.

Installations run Spinbox v20261027.01; the reference is generated from spin v20261114.01 (51f7e0dea). This page as Markdown, for a model or a terminal.