Sign up

Hosting for agent-built apps

Built by agents. Owned by you.

Your coding agent deploys the whole app to live URLs. You keep the ones worth keeping.

No signup needed to deploy. Create an account to keep it.

web-k3f9.agentserve.sh
unclaimed
expires in59:58
how it works ↓

How it works

Your agent deploys the app. AgentServe keeps it running. You claim what you want to keep.

~/todo-app

    
    
  






  

    

      
One deploy. The whole app.

        
Put your API, frontend and workers in one agentserve.yaml. AgentServe wires their URLs into each other, starts them in the right order, and puts the whole stack live with one command.

      

        
agentserve.yamlexample / todo-app


name: todo-app
ttl: 1h

services:
  api:
    path: ./backend
    runtime: python-3.12
    start: uvicorn main:app --host 127.0.0.1 --port $PORT
    health: /healthz

  web:
    path: ./frontend
    runtime: static
    build: npm run build
    output: dist
    env:
      VITE_API_URL: ${api.url}
    depends_on: [api]

        

          
URLs wired before build
${api.url} resolves before the frontend builds, so the app receives its real API address.

          
Ordered startup
depends_on brings up the API before the frontend. Health checks catch failures before the stack is marked live.

          
Safe redeploys
New code builds while the current version serves. If the new deploy fails, the previous version returns.

          
Persistent data
Service data stored in $DATA_DIR survives redeploys, expiry, and claiming.

        

      

    

  


  

    
See what works. Fix what doesn’t.

      
Every project has a clear status, service-level detail, and a direct route to the log that matters. Claim it when you want control.

      

        
Anonymous deploys
Start a temporary stack without creating an account or managing credentials first.

        
Claim codes
Take ownership of a stack with its URLs and data intact, even after it expires.

        
Clear project status
See which service is serving, which one failed, and open the relevant build or runtime log.

        
Python, Node, and static services
Put a backend and frontend into the same deploy with predictable URLs.

        
Events and webhooks
Receive signed lifecycle events so an agent can respond to failures or expiry.

        
Owner controls
Review deploy history, restart a live service, revoke the agent token, or delete the project.

      

    

  


  

    
Temporary by default. Yours when claimed.

      
This version runs on a single server. The limits below describe the current implementation.

      
RuleBefore claimAfter claim

      
Lifetime1 hourNo TTL

      
Expired snapshotKept for 7 daysRestored on claim

      
Services per stackUp to 4Up to 4

      
Project dataStored in $DATA_DIRPreserved across redeploys

      
RuntimesPython, Node, staticPython, Node, static

    

  


  

    
Try it yourself. Then let your agent run it.

      
Install the CLI and deploy a FastAPI and React app with two commands. Everything your agent needs ships alongside it: the CLI, an MCP server, and a skill file it can read.

      

        
Quick startterminal


uv tool install agentserve
agentserve deploy ./todo-app --ttl 1h

        
Agent instructions
Give your agent the AgentServe skill for the deploy commands and API contract.

          
MCP tools
Register uvx --from 'agentserve[mcp]' agentserve-mcp with your agent to expose deploy, status, logs, extend, and destroy tools.

          
Claim what it creates
Your agent returns a claim URL when it deploys. Open it to keep the stack in your account.

      

    

  


  

    
Works with the agent you already use.

      
Each guide covers setup and the first deploy, from a fresh terminal to a claim link.

      
Claude CodeMCP, CLI + skillCursorMCP or CLICodexMCP or CLIWindsurfMCP or CLIAny MCP clientMCPYour own agentHTTP

    

  


  

    
From the build log.

      
Notes on how AgentServe works and why it works that way. All posts →

      
LaunchIntroducing AgentServeAgents can build a working app in an afternoon. Then they have nowhere to put it. AgentServe gives them somewhere, and lets a human decide what to keep.October 9, 2026 · 5 min readProductDeploy first, claim laterWho owns an app an agent built? Our answer is "nobody, for an hour". Here is how anonymous deploys, the clock, claim codes and token revocation fit together.October 9, 2026 · 6 min readEngineeringBuild, then swap: how redeploys workAgents redeploy constantly and break things often. Here is how AgentServe keeps the old version serving while the new one builds, rolls back when it doesn't come up, and keeps your data out of the blast radius.October 9, 2026 · 6 min read

    

  


  
Good to know.

    
Do I need an account to deploy?
No. Anonymous deploys get a temporary lifetime and a claim code. An account is needed to keep the stack without a TTL.

    
What happens when the hour runs out?
Services stop. The snapshot is retained for seven days, and claiming it during that window restores the stack at the same URLs.

    
What if a redeploy fails?
The current version stays available. The dashboard and logs show the failed build so your agent can fix it.

    
Which runtimes work today?
Python, Node, and static sites. Managed databases, containers, and custom domains are not implemented in this version.

    
Can I revoke my agent's access?
Yes. Once the stack is yours, the dashboard lets you revoke the original agent token.

  


  

    
Give the next idea somewhere to run.

    

      
$ uv tool install agentserve && agentserve deploy

      Create your account
    

    
Have a claim code? Claim your deploy →