Every Hermes Agent guide on this site so far — deploying it on Oracle Cloud’s free tier, wiring up Discord — assumes you’re running your own server. Hermes Cloud is Nous Research’s answer for when you’d rather not.
What Hermes Cloud Actually Is
Hermes Cloud runs a dedicated, always-on Hermes Agent instance for you, each with its own workspace and dashboard. Setup is reduced to picking a model and a server size in Nous Portal — no SSH, no installer, no systemd unit to write. Nous Research’s own announcement put the whole flow at “two clicks and 60 seconds” from empty account to a live agent.
Billing is hourly, drawn from your Nous Portal credit balance, and the instance scales to zero when idle — you’re not paying for a server sitting there doing nothing between conversations, which is a meaningfully different cost model from a VPS you’re renting whether you use it or not.
For teams, Hermes Cloud extends past a single instance: you can spin up separate agents per person or project, with granular access controls and billing consolidated under one org account rather than everyone managing their own.
Nous Portal Is the Account That Ties It Together
Hermes Cloud isn’t a separate product with its own login — it lives inside Nous Portal, the account layer that also covers:
- Model access — a catalog of 300+ models across providers, reachable through one OAuth login instead of separate API keys per provider.
- The Tool Gateway — web search (Firecrawl-backed), image generation, text-to-speech, and browser automation, each opt-in individually rather than all-or-nothing, billed through the same account.
- Unified billing — one subscription and one invoice, instead of five different dashboards and top-up balances across providers.
If you’ve already run hermes setup --portal on a self-hosted instance (as covered in the Oracle Cloud deployment guide), you’re already using the same Nous Portal account — Hermes Cloud is just the option to run the agent itself on Nous Research’s infrastructure instead of your own.
New accounts also get a one-time credit grant usable specifically for Tool Gateway calls — not model inference — meant to let you try tool-using workflows (a web search, a page scrape) before committing spend to a paid plan.
Hermes Cloud vs. Self-Hosting: Which One to Pick
| Hermes Cloud | Self-hosted (e.g. Oracle Cloud free tier) | |
|---|---|---|
| Setup | Pick a model + server size in Nous Portal | Provision a VPS, run the installer, configure the gateway yourself |
| Cost | Hourly, drawn from Nous Portal credit; scales to zero idle | Can be $0/month on a free-tier instance, plus your time |
| Server management | None — Nous Research runs it | You patch, monitor, and keep the gateway alive yourself |
| Where your data lives | Nous Research’s infrastructure | A server you control |
| Team features | Per-person/project agents, granular access controls, unified org billing | You build this yourself if you need it |
| Best for | Not wanting to think about infrastructure at all | Free-tier cost, full control over the box it runs on |
Neither is strictly better — it’s the same tradeoff as managed vs. self-hosted anything. If the appeal of Hermes in the first place is running your own AI agent on your own infrastructure, self-hosting keeps that intact. If what you actually want is the agent without any of the server-admin part, Hermes Cloud removes that entirely, at the cost of paying for compute time and running on someone else’s servers.
Related Articles
- Connecting Hermes Agent to GitHub: Auth Setup and Gotchas
- What is Hermes Agent? Nous Research’s Self-Improving AI Agent
- How to Deploy Hermes Agent on Oracle Cloud’s Free Tier
- Connecting Hermes Agent to Discord: Complete Setup Guide
- Hermes Agent vs OpenClaw
- Hermes Agent on a 1GB VPS: Fixing the Common Gotchas
