Last verified:
Hermes Agent shipped in February 2026 and is at 237K GitHub stars as of August 2026. Most of the hype is fair, the skill-writing loop genuinely does cut repeat-task cost, but the hosting advice floating around right now is terrible. Half the threads tell you a 5 dollar VPS is enough. Half tell you to spin up an H100. Both are right for different setups, and most people pick wrong.
Here is what I actually tested over three weeks of running Hermes with Telegram, Discord, and Slack gateways pointed at it.
What Hermes Actually Needs From a VPS
The agent process itself is light. Python 3.11, skill files on disk, an SQLite session index, the gateway daemons: maybe 300 to 500 MB resident memory total. The thing that decides your bill is whether you also host the model on the same box.
Two paths:
- Bring your own model. Hermes calls an OpenAI-compatible endpoint. The VPS only runs the orchestration. You can survive on 2 vCPU / 4 GB. Cost: 5 to 10 EUR a month.
- Self-host the LLM too. Now you need 16 GB RAM minimum for a 7B model, 32 GB for 13B, and you want a GPU unless you enjoy 20-second responses. Cost: 100 EUR a month and up.
Most people start with path 1 and only move to path 2 once they hit usage limits or want their conversations off external APIs entirely.
VPS Comparison for Hermes Agent
| Provider | Plan | vCPU | RAM | Disk | Monthly | Best fit |
|---|---|---|---|---|---|---|
| Hetzner Cloud | CX23 | 2 | 4 GB | 40 GB NVMe | 5.49 EUR net | BYO model, the default pick |
| Contabo | Cloud VPS 4 | 4 | 8 GB | 100 GB SSD | 5.50 EUR net | BYO model plus helper services |
| Hetzner Cloud | CX33 | 4 | 8 GB | 80 GB NVMe | 8.49 EUR net | Headroom on NVMe |
| Hetzner Cloud | CCX13 | 2 | 8 GB | 80 GB NVMe | 42.99 EUR net | Dedicated vCPU, only if you need it |
| Hetzner GPU | GEX44 | 14 | 64 GB | 2x 1.92 TB | 234 EUR + 114 setup | Self-host 13B model + agent |
Hetzner and Contabo both quote net prices, so add your local VAT.
Hetzner Cloud CX23: The default pick for BYO-model setups
At 5.49 EUR net for 2 vCPU and 4 GB, this is the honest default. A bring-your-own-model Hermes uses 300 to 500 MB, so you are buying headroom for the gateways and whatever else lives on the box, not for the agent. Latency to OpenAI and Anthropic from Falkenstein is under 80 ms, which the Hermes loop benefits from when it chains tool calls.
Pros that matter for Hermes:
- Cheapest credible plan that still leaves room for a second service
- API + Terraform makes redeploys after a bad skill commit painless
- EU jurisdiction if your messaging gateways carry user PII
Step up to the CX33 (4 vCPU / 8 GB, 8.49 EUR net) if you also enable voice-memo transcription, which pulls in ffmpeg and is the one Hermes feature that is genuinely CPU-hungry.
Skip the CCX13 unless you know why you want it. It is 42.99 EUR net for the same 8 GB as the CX33, and what you are paying for is dedicated vCPU. Hermes spends its time waiting on a remote model endpoint, so shared vCPU is not its bottleneck. Dedicated cores are worth it for local inference or a noisy multi-tenant workload, not for this.
Grab Hetzner here: Hetzner Cloud.
Contabo Cloud VPS 4: The best value on the table
At 5.50 EUR net for 4 vCPU and 8 GB RAM, nothing beats Contabo on specs per euro - it delivers twice the RAM of the CX23 for one cent more. Storage is SSD rather than NVMe, which Hermes does not care about, but provisioning takes hours rather than seconds. If you are the kind of person who spins servers up and down to test things, this will frustrate you. If you set it up once and leave it, the price is hard to argue with.
The thing nobody mentions: Contaboโs network egress can be slow when calling external model APIs at peak hours, which adds 100 to 300 ms to every Hermes turn. Annoying but not fatal.
Pros:
- Most RAM per euro of any plan here
- 4 vCPU is overkill for the agent alone, and exactly right once you add voice transcription or a second service
Get Contabo: Contabo VPS.
DigitalOcean: For US-based stacks
If your model endpoint, Slack workspace, and team are all US-east, DigitalOceanโs NYC3 region wins on latency. The 1-click marketplace is irrelevant for Hermes since there is no template, but the snapshot system is genuinely useful when you want to roll back a bad skill commit.
Honest negatives: DigitalOcean costs several times what Hetzner or Contabo do for the same RAM, and it restructured its droplet line-up in 2026, so check the current tier names and prices on their pricing page rather than trusting any table - including older versions of this one.
Set up DigitalOcean: DigitalOcean.
Hetzner GEX44: If you self-host the LLM
The moment you want Hermes plus a 13B model running on the same machine, you need GPU. The GEX44 with an RTX 4000 SFF Ada is the cheapest serious option in Europe at 234 EUR a month plus a 114 EUR setup fee. Its 20 GB of VRAM holds a 13B at 4-bit with room for the agent alongside it. A Llama 3.1 70B at 4-bit needs around 40 GB and will not fit โ that is the 96 GB GEX131 at 1,199 EUR a month.
This is overkill for 90% of Hermes users. Pick it only if you have a privacy mandate that rules out external API calls.
What I would actually pick
If you are starting today and just want Hermes running with your favorite messaging app:
- Cheapest that works: Hetzner CX23, 5.49 EUR net
- Best value: Contabo Cloud VPS 4, 5.50 EUR net for 8 GB
- Voice transcription or a second service: Hetzner CX33, 8.49 EUR net
- US team: DigitalOcean, current pricing on their site
- Privacy-first, self-host the model: Hetzner GEX44
For the full picture across all self-hosted tools, see the SelfHostVPS comparison. The Hermes Agent project moves fast, so I update this page when meaningful changes hit the main branch.
Frequently asked questions
What is the minimum VPS spec to run Hermes Agent comfortably?
If you point Hermes at a remote model endpoint (OpenAI-compatible, OpenRouter, Anthropic), 2 vCPU and 4 GB RAM is the realistic floor. The agent itself, the skill files, the FTS5 session index and the messaging gateways are not heavy. The moment you self-host the inference model on the same box, you need 16 GB RAM and a GPU. Do not try CPU inference for a daily-use agent, the latency kills the loop.
Does Hermes Agent need a GPU on the VPS?
Only if you also run the language model locally. Hermes itself is a Python 3.11 orchestration layer plus its skill-writing loop, which is bound by I/O and tokens-out from the model, not by local compute. A CPU-only Hetzner CCX or Contabo box is fine when the model lives elsewhere. Hetzner GPU servers or Genesis Cloud are the cheapest GPU paths in Europe.
Can I run Hermes Agent on a 5 dollar VPS like the docs claim?
Yes, but only in the bring-your-own-model setup. The project README says outright that you can run it on a 5 dollar VPS, because Hermes streams completions from a remote endpoint and the agent footprint is small. Add a Telegram and Slack gateway and you are at around 350 MB RAM resident. The 5 dollar tier breaks the moment you enable local inference, Whisper transcription, or vision tools.
Does Hermes need NVMe, or is SSD good enough?
SSD is good enough. Hermes writes a skill file after a complex task and appends to an SQLite FTS5 index, which is a light, bursty pattern measured in kilobytes, not the sustained throughput a database server needs. Contabo Cloud VPS 4 ships SSD rather than NVMe and runs Hermes fine. Pick NVMe when you also self-host the model and are loading multi-gigabyte weights from disk, where the sequential read speed is what you are actually paying for.