Devpipe
Web + CLI beta

A machine that runs your coding agents

Close the lid. It keeps building.

Start an agent in a persistent remote terminal and walk away. Nothing stops. Reconnect to the same session from the browser or with devpipe attach.

devpipe-api ~/work/devpipe claude 00:00:00 

        


        

          
You closed the tab

          
The session is still going · 0s

        


        

      

    


    

      
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 browser is the workspace. When you want the terminal directly,
        install the small CLI, sign in once, and run
        devpipe attach <box>. It wakes a sleeping machine,
        reconnects to the persistent session, and leaves the agent running when
        you detach.
      


      

        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, Runpod, and local
        Docker implement the same durable machine lifecycle. 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
    
            
    
              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.