Can you self-host Hermes Agent?

Who should self-host Hermes Agent?

Before you install: pick your hosting environment

Option 1: Install Hermes Agent locally (the quick test)

Prerequisites

The one-line installer

Run the diagnostic tool

Set up a model provider

When local install makes sense - and when it doesn't

Option 2: Self-host Hermes Agent on a VPS

Step 1: Choose and provision a VPS

Step 2: Initial server hardening

Step 3: Install Hermes

Step 4: Configure your LLM provider

Step 5: Connect the messaging gateway

Step 6: Run Hermes as a systemd service (always-on agent)

What about Docker?

Environment variables: your control panel

The real maintenance burden

Self-Hosting vs Managed Hosting

Common beginner mistakes (and how to avoid them)

Recommended beginner path

Conclusion

How do I self-host Hermes Agent?

Can I install Hermes Agent on Windows?

Do I need Docker to install Hermes Agent?

Can I host Hermes Agent on a VPS?

How do I make Hermes Agent always-on?

How do I back up Hermes Agent?

What does it cost to self-host Hermes Agent?

Should beginners self-host Hermes Agent? Yes - you can self-host Hermes Agent on Linux, macOS, WSL2, Android via Termux, or a VPS. The official installer is a one-line command that handles Python 3.11, Node.js, ripgrep, ffmpeg, and the global hermes CLI setup automatically. On a VPS with a non-root user and basic firewall, the whole install takes under five minutes. For testing, your own laptop is fine. For a genuine always-on assistant, a VPS or managed infrastructure is the practical next step. The important question is not just "Can I install Hermes Agent?" - it's whether you want to maintain the server yourself or simply start using the agent. That's what this guide will help you decide. If you're completely new to Hermes and want to understand what it does before installing, start with our beginner explainer: What is Hermes Agent? Self-hosting is a good fit if you: Self-hosting may not be the best path if you: If that second list sounds more like your situation, self-hosting Hermes Agent without the setup pain is a pragmatic alternative. You still get the persistent agent with memory and skills - just without the infrastructure chores. There are three common paths. Each serves a different goal. Start local to learn. Move to a VPS when you're ready for 24/7 uptime. Choose managed hosting when you realise you'd rather use the agent than maintain it. This is where every beginner should start. You'll verify that Hermes works before committing to a server. The only hard prerequisite is Git. The official installer provisions Python 3.11 (via uv), Node.js v22, ripgrep, and ffmpeg automatically. Hermes supports Linux, macOS, WSL2, and Android/Termux. Native Windows is not supported - use WSL2 on Windows machines. Open your terminal and run: When it finishes, reload your shell: Check that the install succeeded: You should see something like Hermes Agent v0.9.0, along with Python and project path details. Before having your first conversation, run hermes doctor. It checks that the model connection, memory system, and tools are all healthy. Look for green checkmarks. If anything shows red, fix it before moving on. Hermes doesn't ship with a built-in model - you need to connect it to one. Run: This opens an interactive wizard. You can choose OpenRouter (200+ models with a single key), Anthropic, OpenAI, Google Gemini, xAI Grok, or Ollama for local models, or any OpenAI-compatible endpoint. Hermes requires a model with at least 64,000 tokens of context; most hosted models meet this easily. After selecting a provider and entering your API key, start chatting: That's it. You've completed a basic Hermes Agent install guide on your local machine. A local install is perfect for testing, learning commands, and trying different providers. It becomes a limitation when your laptop is turned off, your internet changes, you want remote access via Telegram or Slack, or you need scheduled tasks to run reliably. Hermes is most useful when it can stay alive - that's why most people move to a VPS next. A cloud VPS gives you an always-on home for your agent. The setup is straightforward: spin up a VM, create a non-root user, install Hermes, pick a provider, configure the messaging gateway, and wrap everything in a systemd service. Pick a provider - DigitalOcean, Linode, Vultr, Hetzner, or Hostinger all work well. Use Ubuntu 22.04 or 24.04 LTS. The minimum spec is 2 GB RAM and 10 GB disk. For a smoother experience with the web dashboard and multiple gateway sessions, go with 4 GB RAM and 20 GB+ disk. SSH into your server as root and create a dedicated user for Hermes: Copy your SSH key so you can log in as the hermes user, then switch to that account: Set up a firewall that allows only SSH inbound: The Hermes gateway makes outbound connections to messaging APIs, so no inbound ports beyond SSH need to be open. Run the same one-line installer, this time on your VPS: Lock down the environment file and add your API key: Add your key (for example, with OpenRouter): Save and exit. Then set the default model: If you get a response, the provider is configured. This completes your basic Hermes Agent VPS setup. The gateway lets you talk to Hermes from Telegram, Discord, Slack, or any of 16 supported platforms. To add Telegram: The TELEGRAM_ALLOWED_USERS variable is critical - without it, anyone who finds your bot can send it commands. Start the gateway to verify it works: Send a test message from Telegram. You should see the message in your terminal and receive a response. Press Ctrl+C to stop once you've confirmed it works. Running hermes gateway in a terminal session means it stops when you disconnect. A systemd user service keeps it alive after logout and restarts it automatically after crashes or reboots. Hermes has a built-in command for this: This creates the service file and enables lingering, which keeps user services running after SSH logout. Start the service: Look for Active: active (running). If it shows failed, check the logs: You now have an always-on agent that survives reboots and SSH disconnects. The official beginner path is the one-line installer. Docker is available, and some users prefer it for the container-level isolation - Hostinger, for example, offers a Docker template that deploys Hermes with one click from their VPS catalogue. Community-maintained Docker images also exist and can be useful if your broader stack already runs on Docker. But for a beginner's first setup, the installer is simpler and the one the official docs recommend. Don't add Docker complexity unless it solves a real problem you already have. Your ~/.hermes/.env file is the single source of truth for secrets. The ~/.hermes/config.yaml holds structured settings like provider routing, MCP servers, and toolset configuration. Never put API keys in config.yaml - keys stay in .env, and .env should have chmod 600 permissions. Key variables worth setting early: Keep approval mode on ask for any VPS deployment. It prompts you before the agent runs potentially dangerous commands. Telegram and Slack show native approval buttons, so you don't even need to type a response. Installing Hermes is quick. Keeping it healthy for months is the real job - and it's the part most tutorials skip. Self-hosting gives you full sovereignty. Your data, your server, your rules. A VPS costs a few dollars a month, and you learn a lot about how the agent works under the hood. The hidden cost is time - hours spent on updates, backups, gateway debugging, security patches, and troubleshooting when something breaks. If you enjoy that work, it's a rewarding hobby. If you'd rather focus on using the agent for your actual projects, the VPS vs managed hosting for Hermes Agent decision tips toward managed hosting. With Managed Hermes Agent Hosting, the setup, updates, backups, gateway configuration, and monitoring are handled for you. You still get a persistent agent with memory, skills, and your choice of model - just without the system administration. For most non-technical users and teams, it's the more practical path. If you're ready to skip the server work, you can deploy Hermes Agent on managed infrastructure and start using it today, with memory, skills, and 24/7 availability included. You can absolutely self-host Hermes Agent, and the official one-line installer makes the first setup faster than most open-source AI tools. But installation is only the beginning. Keeping an always-on agent running reliably requires ongoing attention to updates, backups, security, and monitoring. If you're technical and enjoy the process, self-hosting on a VPS is a great learning experience and gives you full control. If you'd rather spend your time using the agent - building workflows, automating tasks, and letting it learn how you work - Managed Hermes Agent Hosting removes the infrastructure burden so the agent simply stays alive and keeps getting better. Run the official one-line installer: curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash. After installation, configure your model provider with hermes model, run hermes doctor to verify the setup, and start chatting with hermes. Native Windows is not supported. Windows users should install WSL2 first, then run the installer inside the WSL2 terminal. No. The official beginner path uses a one-line installer that handles all dependencies. Docker is optional and available for users who prefer container-level isolation, but it's not the default method. Yes. A VPS running Ubuntu with at least 2 GB RAM is the most common way to keep Hermes running as an always-on assistant. You'll manage updates, backups, and security yourself. Use hermes gateway install to create a systemd user service, then enable it with systemctl --user enable --now hermes-gateway. This keeps the agent running after SSH logout and restarts it automatically on crash or reboot. Since v0.9.0, Hermes includes a hermes backup command that creates a timestamped snapshot of your entire ~/.hermes/ directory. Schedule it with cron and rsync the backups off-server. The software is free and open-source (MIT license). You pay for the VPS (roughly $5-12/month) and LLM API usage, which varies by model and volume. Local models via Ollama can eliminate API costs but require a GPU for good performance. Yes - for testing and learning, the one-line installer makes it beginner-friendly. For always-on use, team workflows, or business reliance, managed hosting is usually the easier and safer path. Templates let you quickly answer FAQs or store snippets for re-use. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse