Hermes Agent on Railway

What Hermes Agent on Railway does

The template starts Hermes Agent in a Railway service and puts an authentication proxy in front of the Hermes dashboard on port 9119. Login uses a cookie-based page rather than basic auth, with the username defaulting to admin and a DASHBOARD_PASSWORD variable that must be set or the deploy fails. From the dashboard you manage config, API keys, sessions, logs, analytics, cron jobs and skills.

The messaging gateway for Telegram, Discord and Slack runs alongside the dashboard. A floating widget injected into the dashboard shows whether the gateway is running and restarts it after configuration changes, without a redeploy. By default the container pulls the latest Hermes release on every restart, and setting AUTO_UPDATE to false pins the version. Attaching a Railway volume at /root/.hermes keeps sessions, memories, keys, config, logs and cron jobs across redeploys.

Key features

• Cookie-based login proxy in front of the Hermes web dashboard
• Dashboard control of config, API keys, sessions, logs, analytics, cron jobs and skills
• Telegram, Discord and Slack gateway with a status and restart widget
• Automatic Hermes updates on restart, switchable off with AUTO_UPDATE=false
• Persistent storage through a Railway volume mounted at /root/.hermes

When to use it

• Running an always-on Hermes Agent without managing a server
• Configuring a Telegram or Discord bot from the browser instead of over SSH
• Giving a small team a hosted Hermes dashboard behind a password

Who it is for: Hermes Agent users who want a hosted instance on Railway and prefer to configure it from a browser.

How it fits with Hermes Agent

Built specifically to host Hermes Agent, wrapping its web dashboard and messaging gateway in a Railway deployment.

Requirements: A Railway account and a DASHBOARD_PASSWORD value; an LLM provider key such as OpenRouter added on the dashboard's API Keys page; a Railway volume at /root/.hermes to keep data

Note: The Deploy on Railway link in the README contains TEMPLATE_ID and REFERRAL_CODE placeholders, so the button may not point to a working template.

FAQ