Hermes Agent Always-On (Telegram, Discord, Slack)

Deploys Hermes Agent v0.21.7 from Nous Research as an always-on assistant reachable on Telegram, Discord, Slack or in the browser with Hermes WebUI. Memory, skills and schedules persist on a volume, and a headless Chromium handles web tasks.

What you get

  • The official nousresearch/hermes-agent image pinned by tag and digest, running the gateway, the official dashboard and Hermes WebUI v0.52.113 in one service
  • A Railway volume at /opt/data for config, sessions, memory and skills
  • A small Caddy proxy service that gives the WebUI its own HTTPS address
  • Generated passwords for the dashboard (user admin) and for the WebUI; the WebUI never starts without one
  • Bundled headless Chromium, cron jobs, and pairing or allowlists to restrict who can message the bot

Good for

  • A personal research and productivity assistant reached from chat apps or a browser tab
  • Scheduled jobs such as daily briefings, website monitoring and recurring reports sent to a chat
  • Web tasks that need a real browser, like reading dynamic pages or checking a deploy
  • A team helper in a Slack or Discord channel limited to approved members

Services in this template

  • Hermes WebUI · from baranberkay96/hermes-agent-railway
  • Hermes · from baranberkay96/hermes-agent-railway

Questions people ask

How do I log in?

For the dashboard, open the Hermes service URL and sign in as admin with HERMES_DASHBOARD_BASIC_AUTH_PASSWORD from the Hermes service Variables tab. For web chat, open the Hermes WebUI service URL and use HERMES_WEBUI_PASSWORD, which is also on the Hermes service. The WebUI needs about a minute after each deploy. You need an LLM provider key; the template asks for an OpenRouter key, and other providers can be added later.

What drives the cost?

Two services run: Hermes, which holds the agent, dashboard, WebUI and Chromium, and the small proxy. Hermes is the main user of memory and CPU, and model usage is billed by your LLM provider. Pick a default model that fits your budget, since the stock default is a premium model.

Is data kept across redeploys, and how do I scale?

Yes, state lives on the volume. Hermes is a single-writer process, so keep one replica and scale vertically. Never point two gateways at one data directory.

How do I upgrade?

Images are pinned in services/hermes/Dockerfile and services/webui-proxy/Dockerfile. Upgrade Hermes Agent and Hermes WebUI together, to versions released close to each other. If the release notes say so, run hermes config migrate through railway ssh. Do not run hermes update inside the container.

What are the security and licence notes?

Both interfaces can read and change API keys and run tools, and the WebUI includes a web terminal, so keep both passwords private. Hermes Agent and Hermes WebUI are MIT licensed. This is a community template, not affiliated with Nous Research or the WebUI maintainers.

Full template README

Deploy and Host Hermes Agent with Railway

Run Hermes Agent, the open-source self-improving agent from Nous Research, as an always-on assistant on Railway. Talk to it on Telegram, Discord or Slack, or chat in the browser and on your phone with Hermes WebUI. Memory, skills and schedules persist on a volume, a headless Chromium handles web tasks, and the official dashboard is included.

About Hosting Hermes Agent

Hermes Agent runs as a long-lived gateway: it holds outbound connections to your chat platforms, calls the LLM provider you configure, uses tools (terminal, files, web, browser) and stores what it learns in its home directory. Hosting it yourself means a machine that never sleeps, durable storage for its SQLite state and memories, and safe ways to administer and talk to it. This community template runs the official nousresearch/hermes-agent image pinned to a release, mounts a Railway volume as HERMES_HOME, and runs three things side by side: the gateway, the official web dashboard, and Hermes WebUI, a community chat interface that shares the same memory, skills and sessions. Both web interfaces are protected by generated passwords.

Common Use Cases

  • A personal research and productivity assistant you reach from Telegram, Discord, Slack or a browser tab on your phone
  • Long working sessions in the browser: chat with streaming replies, browse sessions, edit files in the agent's workspace
  • Scheduled jobs: daily briefings, website monitoring, feed summaries and recurring reports delivered to a chat
  • Web tasks that need a real browser: reading dynamic pages, filling forms, checking a deploy
  • A team helper in a Slack or Discord channel, restricted to approved members via pairing or allowlists

Dependencies for Hermes Agent Hosting

  • An LLM provider key (the template asks for an OpenRouter key; Anthropic, OpenAI and many others can be added later)
  • Optional: a bot token for Telegram, Discord or Slack, at deploy time or later in the dashboard (the WebUI works without one)
  • A Railway volume for /opt/data (included)

Deployment Dependencies

Implementation Details

Service Image Purpose
Hermes nousresearch/hermes-agent v0.21.7 + Hermes WebUI v0.52.113 Gateway (agent, cron, kanban), official dashboard on the public URL (port 9119), Hermes WebUI on private port 8787, bundled headless Chromium, volume at /opt/data
Hermes WebUI caddy:2.11.7-alpine Small reverse proxy that gives the WebUI its own HTTPS address and forwards to the Hermes service over the private network

Hermes WebUI runs inside the Hermes service because it drives the agent in-process and reads the same home directory (config, sessions, memory, skills); a Railway volume can only be attached to one service. Chats started in the WebUI use the same model, keys, tools and browser as your Telegram bot, and bot conversations show up in the WebUI sidebar.

First login

  1. Dashboard: open the Hermes service URL and sign in as admin with the password in HERMES_DASHBOARD_BASIC_AUTH_PASSWORD (Railway → Hermes → Variables). Choose your default model; the stock default is a premium model, so pick one that fits your budget.
  2. Web chat: open the Hermes WebUI service URL (https://{your-webui-domain}) and enter the password from HERMES_WEBUI_PASSWORD, which is also on the Hermes service's Variables tab. On a phone, use "Add to Home Screen" for an app-like shortcut.
  3. Messaging: DM your bot. Unknown users receive a pairing code, which you approve on the dashboard's Pairing page. Set TELEGRAM_ALLOWED_USERS (or the Discord/Slack equivalent) to skip pairing for known IDs.
  4. Add more platforms on Channels, more providers on API Keys, scheduled jobs on Cron.

The WebUI needs about a minute after a deploy; until then its URL shows a short "not reachable yet" notice. To turn it off, set HERMES_WEBUI=0 on the Hermes service. Deployments created before the WebUI was added keep it off until HERMES_WEBUI=1 and a HERMES_WEBUI_PASSWORD are set and the proxy service is added.

Scaling: Hermes is a single-writer process. Keep one replica and scale vertically (Railway gives the service more RAM/CPU automatically up to your plan limit). The proxy needs no scaling. For separate personas, use Hermes profiles inside the same service rather than extra replicas. Never point two gateways at one data directory.

Pinning and upgrades: all images are pinned by tag and digest in services/hermes/Dockerfile and services/webui-proxy/Dockerfile. Hermes WebUI and Hermes Agent are developed separately and should be upgraded together to versions released close to each other. After an upgrade, run hermes config migrate via railway ssh if the release notes say so. Do not run hermes update inside the container.

Security notes: both interfaces can read and change API keys and run tools, and the WebUI includes a web terminal, so keep both passwords private. The WebUI never starts without a password. For an internet-facing dashboard, upstream recommends Nous Portal OAuth: run hermes dashboard register via railway ssh and set HERMES_DASHBOARD_OAUTH_CLIENT_ID. The OpenAI-compatible API server is disabled by default.

Why Deploy Hermes Agent on Railway?

An agent that learns over time is only useful if it is always reachable and never loses its memory. Railway runs Hermes around the clock with a persistent volume, private networking between services, automatic restarts, logs and SSH access, without maintaining a VPS. You pay only for the resources the agent actually uses.

Guides for this template

View Hermes Agent Always-On (Telegram, Discord, Slack) on railway.com

Similar templates

TemplateCategoryDeploymentsDeploys
9Router
Self-hosted AI router for Claude, Gemini, Cursor & OpenAI tools.
AI/ML9,734
flowise-railway
Flowise - low-code LLM apps builder
AI/ML8,512
LibreChat
Open-source ChatGPT clone: multi-model, agents, search, multi-user auth
AI/ML6,762
Hermes Agent by Nous Research
Template for Hermes Agent by Nous Research
AI/ML6,413
OpenClaw
[Homebrew support] The AI that actually does things
AI/ML5,167
Hermes Agent
Self Host Hermes Agent. Autonomous AI agent w/ self-improving, tools & more
AI/ML4,092