A machine that runs your coding agents
Close the lid. It keeps building.
Hand a task to an agent — or to three of them at once, each on its own branch — and walk away. Nothing stops. Come back to finished work and pick the one that won.
The shape of it
-
01
A machine, not a container
Yours, with a name and a disk that stays written to. About three minutes from claim to first run, toolchain already on it.
-
02
The work outlives the connection
Agents run on the box, so closing the lid closes nothing. What was running is still running.
-
03
It stands down when you do
An idle box sleeps and wakes with your files exactly where you left them. Nobody pays for a machine to sit warm overnight.
-
04
Keys stay out of your dotfiles
Secrets are sealed on the server and granted to a box — global, per workspace, or per machine. Revoke one and the box loses it on the next read.
The desktop side already exists and is free: Asylum races several coding agents at the same task, each in its own worktree, and lets you merge whichever one won. Take it now — Devpipe is what it reaches for when your laptop is not enough.
And when the agent says it is done, you can look: a port on the box opens in your own browser — privately, or as a link that expires — and a terminal on it can be watched, or handed over, by someone who has no account here at all.
Or run the whole thing yourself
Devpipe is Apache-2.0. DigitalOcean is the production backend we run; local Docker implements the same machine lifecycle for development. No crippled edition, no feature held back.
-
01
A checked first launch
A setup token claims the owner safely. Then the provider token, a domain, credential encryption, an SSH key and a spending cap are checked rather than taken on trust.
-
02
One owner, admins under them
An admin invites people, suspends an abuser and reads the audit log. An admin never sees a credential — which is the whole reason the role exists.
-
03
A cap, because the bill is yours
Droplets and volumes both, accumulated over the provider's own month. Past it nothing new starts and what is running goes to sleep with its files intact.
What it takes to run one — production DigitalOcean, local Docker, safe deployment, and an honest list of what the hosted instance does that you would have to.
Claim your username
Names are first come, and yours becomes the address your machines answer on. We will write once, when there is something to log into.