Deploy and Host Agent Gateway on Railway

Agent Gateway is an open source agentic proxy for AI agents and MCP servers. It provides drop-in security, observability, and governance for agent-to-agent and agent-to-tool communication, supporting leading protocols including Model Context Protocol (MCP) and Agent2Agent (A2A).

About Hosting Agent Gateway

Agent Gateway is a Rust-based proxy that runs as a standalone binary. This template deploys it on Railway alongside Caddy as a reverse proxy, which routes MCP traffic and the admin UI through Railway's single public port. Configuration is persisted to a Railway volume so changes made via the built-in admin UI survive redeploys. The template starts with a blank slate — no listeners, routes, or backends are preconfigured.

Common Use Cases

Proxying and securing MCP servers for AI agents with built-in RBAC and observability
Routing agent-to-agent (A2A) traffic across multiple backends with session persistence
Transforming legacy REST/OpenAPI services into MCP-compatible tool endpoints

Dependencies for Agent Gateway Hosting

Railway Volume mounted at /data for config persistence.

Deployment Dependencies

Implementation Details

Caddy routes traffic on Railway's single public port:

:{$PORT}
handle / {
    reverse_proxy localhost:3000
}
handle {
    reverse_proxy localhost:15000
}

/ routes to the MCP endpoint on port 3000. All other paths (admin UI, API) route to port 15000. On first boot, the entrypoint seeds /data/config.yaml from the bundled default if the volume is empty.

Why Deploy Agent Gateway on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Agent Gateway on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.