Deploy and Host Hermes Web UI on Railway

About Hosting Hermes Web UI on Railway

Hermes Web UI provides a browser interface for Hermes Agent. On Railway, it can run from a pinned GHCR image with public HTTPS routing, environment-based configuration, and persistent volume-backed state.

Tech Stack

• Python 3.12 container image
• Hermes Web UI (server.py + vanilla JavaScript frontend)
• Railway runtime, networking, and persistent volumes
• GitHub Container Registry image: ghcr.io/nesquena/hermes-webui:0.38.5

Why Deploy Hermes Web UI on Railway

• Image-based deployment with no source build pipeline required
• Public HTTPS endpoint with simple service networking
• Persistent storage for sessions and Hermes home data
• Built-in secret management for password-protected access

Common Use Cases

• Hosting a personal or team Hermes browser console
• Accessing Hermes sessions remotely through a secure web UI
• Keeping long-lived workspace/session state across redeploys
• Pairing the UI with existing Hermes agent and model configurations

Deployment Notes

• The HTTP service listens on container port 8787 and sets PORT=8787.
• Persistent storage is mounted at /data with HERMES_WEBUI_STATE_DIR=/data.
• HERMES_WEBUI_PASSWORD should be set for authenticated access (auto-generated in template).
• For full agent capabilities, provide Hermes agent files/config under HERMES_HOME and set HERMES_WEBUI_AGENT_DIR if needed.

Dependencies for Hermes Web UI on Railway

This deployment uses a single HTTP service and does not require a database service.

Deployment Dependencies