Deploy and Host Hermes Agent on Railway

Deploy your own single-owner Hermes Agent with a persistent workspace and web dashboard. This community distribution adds mandatory username/password and authenticator-app two-factor authentication. It retains Hermes tools, messaging integrations, memories, and native agent delegation; its custom model-orchestration feature has been removed.

Dependencies for Hermes Agent

Deployment Dependencies

Supply your own three values in the deployment form:

HERMES_DASHBOARD_TOTP_AUTH_USERNAME: your dashboard username (1–128 characters).
HERMES_DASHBOARD_TOTP_AUTH_PASSWORD: a unique password of at least 12 characters (maximum 1,024).
OPENROUTER_API_KEY: your OpenRouter API key. Model usage is billed to your OpenRouter account.

About Hosting Hermes Agent

The template builds the public source repository, creates one service and a persistent volume mounted at /opt/data, and exposes the dashboard through HTTPS on port 9119. It uses one replica, an always-on service, and the /api/status health check. Railway hosting is billed to your Railway account.

First login

Wait for the deployment to finish, then open the service's generated domain. Sign in with the username and password you supplied. Scan the setup QR code using Google Authenticator or another TOTP authenticator, enter its six-digit code, and save the one-time recovery codes in your password manager.

The initial model is openai/gpt-5.4-mini through OpenRouter. Choose another supported provider/model in the dashboard and add its API key in Railway if desired. Add messaging tokens only for the integrations you use.

Why Deploy Hermes Agent on Railway

The template contains common application code and deployment settings. Your credentials are supplied at deployment time. Signing material, the internal gateway key, authenticator enrollment, sessions, memories, and workspace files are generated or stored privately on your own volume. No example credentials or enrolled authenticator are included.

Keep one replica and retain /opt/data across upgrades. Back up the private volume, including its generated signing secret. Never share a volume between different owners. See the deployment guide for password hashes, custom domains, backup/recovery, and provider settings.

Common Use Cases

A private personal assistant with persistent memories and workspace files.
Agent tool use and native task delegation through a protected dashboard.
Optional messaging integrations using your own bot credentials.

This is a community distribution under the upstream MIT license, not an official Nous Research or Railway release.