Deploy and Host Agent Blueprint on Railway

Agent Blueprint is 53 skills that take a coding agent from an idea to a reviewed pull request. This template runs them as a hosted agent built on Eve. You send it a request, it works on your GitHub repository in a Daytona sandbox, and it opens a draft pull request.

About Hosting Agent Blueprint

The template deploys two services: the agent, built from eve/Dockerfile, and Postgres, which keeps the agent's runs so a run survives a redeploy. Before you deploy, create a GitHub App for the one repository the agent works on, a Daytona API key and a Vercel AI Gateway API key. The build needs the Daytona key because it prepares the sandbox snapshot. After the deploy, generate a domain for the agent service and connect a channel: Slack, Linear, Telegram or an MCP client.

Common Use Cases

Delegate a Linear issue and get a draft pull request back
Start a run from Claude Code or Claude.ai over MCP and let it work on the server
Send a feature request from Slack or Telegram

Dependencies for Agent Blueprint Hosting

A GitHub App with read and write access to Contents and Pull requests
A Daytona account and API key
A Vercel AI Gateway API key on a team with credits

Deployment Dependencies

Why Deploy Agent Blueprint on Railway?

The agent and its Postgres run in one project. The template sets the health check, the database bootstrap before each deploy and a 60-second draining time, so a step that is running during a redeploy is released and retried.