Deploy agentmesh

Deploy and Host Agent Mesh on Railway

Agent Mesh is a private network for AI agents. Its all-in-one server combines a control plane, libp2p router, enrollment and policy APIs, and a browser console. Deploy it on Railway to give agents a simple HTTPS endpoint for identity-aware service discovery, secure routing, and operator management without assembling multiple infrastructure services.

About Hosting Agent Mesh on Railway

Railway runs the pinned upstream GHCR image as one HTTP service. Railway provides the public HTTPS domain, environment-variable management, automated restarts, and a one-click deployment experience while Agent Mesh supplies its control plane, embedded router, SQLite store, and web console.

Tech Stack

• Go all-in-one agentmesh-one binary
• Embedded Agent Mesh control plane and policy APIs
• libp2p router with WebSocket transport
• SQLite local state store
• Embedded browser console
• GitHub Container Registry image
• Railway HTTPS service domain

Why Deploy Agent Mesh on Railway

Railway makes the all-in-one server reachable over HTTPS with minimal configuration. The template pins the tested upstream image, supplies safe generated credentials, routes traffic explicitly to port 8080, and exposes the web console and mesh API from the same public endpoint.

Common Use Cases

• Prototype a private network for AI agents
• Enroll nodes and manage mesh policies from a browser
• Discover and route calls to agent services
• Test MCP, A2A, and OpenAI-compatible mesh integrations
• Demonstrate zero-trust identity and service discovery

Deployment Notes

Set PORT=8080; Railway routes the generated domain to the service's port 8080. Set AGENTMESH_EXTERNAL_URL from the Railway public domain so advertised mesh addresses use HTTPS. AGENTMESH_ADMIN_TOKEN protects the operator console/API and AGENTMESH_TOKEN is the node enrollment token; Railway generates both values with template secrets. No start-command override is required. The upstream image runs as a non-root user, so this template intentionally does not attach a Railway volume: Railway volume mounts are root-owned on first attach and would prevent SQLite from opening. Local SQLite, router identity, signing keys, and generated state are therefore ephemeral across a replacement deployment; use an external persistence design for production durability.

Dependencies for Agent Mesh on Railway

Agent Mesh is a single-service deployment with no database, cache, or worker dependency. The embedded router and control plane share the all-in-one process and communicate internally; external clients use the public HTTPS domain.

Deployment Dependencies