Hermes Agent
Deploy Hermes

Deploy Hermes the way you want, or use the managed cloud hosting that is live now.

This page focuses on four clear paths: official local install, official Docker install, managed VPS deployment, and managed cloud hosting. The first two are self-serve today, managed cloud is live now, and managed VPS is still collecting demand.

If you want a deeper breakdown of the tradeoffs between local, Docker, VPS, and elastic cloud setups, read the Hermes Agent deployment options comparison guide.

Open managed hostingCompare with OpenClaw
Self-serve install

Use the official commands when you want to install Hermes yourself.

Local script install

Best when you want the fastest path from zero to a real Hermes session.

  • Uses the official installer from the upstream Hermes project.
  • Best for Linux, macOS, or WSL2.
  • Lowest friction path for first-time evaluation.
Commands
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
source ~/.bashrc   # or source ~/.zshrc
hermes setup
hermes

Docker install

Best when you want a cleaner runtime boundary and a repeatable containerized setup.

  • Uses the official Hermes image on Docker Hub.
  • Keeps state mounted at ~/.hermes.
  • Good bridge between local validation and longer-lived infra.
Commands
docker pull nousresearch/hermes-agent:latest
mkdir -p ~/.hermes
docker run -it --rm -v ~/.hermes:/opt/data nousresearch/hermes-agent setup
docker run -it --rm -v ~/.hermes:/opt/data nousresearch/hermes-agent
Managed paths

If you want less infrastructure work, start with the managed cloud path that is already live.

Managed VPS deployment

We deploy Hermes onto a VPS for you, while keeping the runtime shape closer to self-hosted infrastructure.

  • Good if you want Hermes online continuously.
  • Fits teams that still want a server boundary and operational ownership.
  • We are collecting demand before opening this path publicly.
Waiting list

Join the waiting list and we will log your interest for this deployment path.

Managed hosting

Create a cloud Hermes runtime plus WebUI after signing in, then start using it directly in your browser.

  • Managed cloud hosting is live and is the recommended way to start.
  • Each account can create one isolated workspace for now.
  • The WebUI is public but protected by a dedicated password.
  • Best for teams that want Hermes running now without maintaining the infrastructure themselves.
Recommended path

Create a cloud Hermes runtime plus WebUI after signing in, then start using it directly in your browser.

Open managed hosting
Which one should you pick?

Choose by operating model, not by what sounds more advanced.

Use local first

Choose this when you want the fastest validation path and the least operational overhead.

Use Docker next

Choose this when you want cleaner reproducibility without jumping straight to VPS management.

Use managed VPS

Choose this when Hermes needs to stay online but you still want a server-shaped deployment.

Start with managed cloud

If you do not want to operate Hermes yourself, use managed cloud hosting now. This is the recommended path today.

Hermes deployment FAQ

Answers to the deployment questions visitors usually ask first: which install path to choose, what Docker changes, and what our two managed options mean.

If you are unsure, start with the lowest-friction path first and move up only when the runtime shape becomes a real need.