How it works
What a computer is, where it runs, and what stopping does.
A computer is a small virtual machine
Each computer is its own virtual machine with its own Linux kernel. It isn't a container sharing a kernel with other people. Nobody else's programs can see yours, and yours can't see theirs.
Inside, you're user with sudo, in /home/user, on Debian 13. Git, curl, Python 3.12 with uv and pytest, Node.js 24, a headless browser, and the Claude Code and Codex agents are installed. Everything else, you install.
Where it runs
On our own servers in Delhi, India. Requests reach them through a small server in Delhi that handles HTTPS.
- In India, typing in a computer feels instant: about 15 to 40 ms per keystroke.
- Elsewhere it's slower, because every keystroke travels to India and back. From Europe expect about 150 ms, from the US about 250 ms. Agents barely notice; people typing by hand will.
Starting is fast because nothing boots
New computers start from a saved, already-booted machine, so there's no boot to wait for. That's why it takes under a second on our side. Your network adds its own delay on top.
Stopping saves everything
When a computer stops, we save its disk and its memory. That includes programs that were running. When you start it again, they carry on from the same moment.
Computers stop when you run workpaper stop, after an hour of running (see limits), or after an hour of doing nothing. Either way you lose nothing.
Forking copies a computer
workpaper fork my-agent my-agent-2 makes a second, independent computer from the current state of the first, running programs and all. It's useful for trying something risky without touching the original. You need an account to fork.
What we can and can't see
We don't look inside your computers. Like any hosting company, the people who run the hardware technically could, so don't keep secrets on a computer that you wouldn't put on a rented server. We don't sell or share your data.