Deploy without touching a terminal.
Self-hosting Hermes requires provisioning a VPS, installing Docker, configuring Caddy or Nginx, managing environment variables, and maintaining everything when it breaks. Most developers spend a full weekend on it.
Hermes OS takes all of that away. The entire infrastructure layer — server provisioning, container runtime, networking, SSL, monitoring — is handled before you sign in.
What self-hosting actually requires
To run Hermes Agent on your own VPS, you need a server running Linux (Ubuntu 22.04 or 24.04 is recommended), Docker and Docker Compose installed and configured, a domain name with DNS pointed at the server, a reverse proxy (Caddy or Nginx) configured for SSL termination, and environment variables correctly set across a ~30-variable `.env` file.
You also need a backup strategy for the persistent memory volume, monitoring so you know when the container crashes, and a restart policy so the agent comes back up after reboots. None of this is extraordinarily difficult if you know Linux, but it is a full afternoon of work minimum, and it is ongoing — each major Hermes update potentially requires migration steps, dependency updates, or config changes.
When it breaks at midnight because the Docker daemon failed or the SSL certificate did not auto-renew, you are the one who fixes it.
What Hermes OS handles instead
Server provisioning is automatic. When you sign up, a dedicated compute instance is allocated in your chosen region within 90 seconds. The Hermes Agent container, configured and tested for stability, is already running. You do not select an OS, configure SSH keys, or install anything.
Networking and SSL are handled. Your agent's web interface is accessible over HTTPS at your Hermes OS subdomain immediately. Bringing a custom domain takes two DNS records and about 15 minutes — no Nginx config files.
Monitoring runs in the background. If the agent process crashes, the container restarts automatically. If the host has a hardware issue, your instance migrates. You get notified and do not have to respond at 2am.
Updates are managed. When Nous Research ships a new Hermes Agent version, we test it, stage it, and apply your update during your configured maintenance window. Your memory and configuration migrate forward automatically.
The sign-up to running agent flow
Create an account and choose a plan. Infrastructure provisions automatically during signup — you will see a status indicator as your instance comes up, typically 60-90 seconds.
Go to the Keys section and paste your AI provider API key (Anthropic, OpenAI, or an OpenRouter key). This is the only credential you need to configure.
Optionally set up your agent's system prompt to tell it who you are and what you want it to do. This can be done at any time — the agent runs with sensible defaults immediately.
That is the full setup. The agent is live and accessible from the dashboard. Scheduled tasks, integrations, and additional configuration happen in the UI without touching a config file.
For users who do want terminal access
If you want to inspect the container, add custom tools, or configure something not exposed in the UI, the dashboard exposes log viewing, the agent's tool directory, and a container shell — without managing your own SSH keys or sshd.
This is opt-in. You do not need it to use the platform, and enabling it does not change anything about the standard managed behavior. It is there for users who want the managed hosting baseline but also want escape hatches to the infrastructure.
- No VPS to provision or maintain
- No Docker, Compose, or container management
- No Nginx, Caddy, or reverse proxy configuration
- No SSL certificate management
- Automatic container restarts and health monitoring
- Updates applied without breaking your configuration
- From signup to running agent in under 5 minutes
- Dashboard escape hatches: log viewer, tool directory, container shell
Do I need any technical knowledge to use Hermes OS?
Basic familiarity with AI tools is enough. You do not need Docker, Linux, or networking knowledge. The sign-up flow walks you through everything.
What if I want to customize the underlying container config?
Advanced users can access container configuration, the agent's tool directory, and a container shell through the dashboard. You are not locked out — we just do not require it.
Is Hermes OS just a VPS with a UI wrapper?
No. Hermes OS is purpose-built managed infrastructure for Hermes agents: pre-configured container runtime, pre-installed browser automation, automatic memory backup, managed updates, and a dashboard purpose-built for Hermes. A generic VPS does none of this for you.
What region is my server in?
At signup you choose from US East, US West, EU Central, and EU West. Agent latency to AI provider APIs is optimized based on region choice.
What happens if Hermes releases an update that breaks my configuration?
We test all Hermes updates before rolling them out and document breaking changes. If an update conflicts with your configuration, you are notified before it applies and given a window to review.