A machine that runs your coding agents
Close the lid. It keeps building.
Start an agent in a persistent environment on a machine you own and
walk away. Nothing stops. Reconnect to the same session
with dp attach — from anywhere, on any laptop, days later.
The shape of it
-
01
One machine, many environments
A box you already have, holding a project each: its own workspace, its own ports, its own processes, toolchain already on it. About a second to make one, not three minutes and a volume to reconcile.
-
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
Sleep an environment and its workspace is untouched; wake it and your files are exactly where you left them. Nothing is paid for twice, because it was one machine to begin with.
-
04
Keys stay out of your dotfiles
Secrets live on the machine, mode 0600, and are lent to an environment at the moment a session starts. A key rotated this morning reaches a container made last week. Remove one and the next session never sees it.
Everything is a path — dp attach box/api — so what you read
off the tree is what you type back. dp reaches your machine
over ssh and nothing else listens: no certificate to arrange, no token to
paste around, and this site is not in the path.
And when the agent says it is done, you can look:
dp forward box/api 3000 brings its dev server to
localhost:3000 on the machine you are sitting at.
Or run the whole thing yourself
Devpipe is Apache-2.0, and running it yourself is the ordinary way to run it — one binary, a container runtime, and a box you can ssh into. No crippled edition, no feature held back, and nothing here that a hosted account unlocks.
-
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
Machines and workspaces are accumulated over the provider's own month. Past the cap nothing new starts and what is running goes to sleep with its files intact.
What it takes to run one: production DigitalOcean, Runpod, 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.