Paperclip vs Hermes vs OpenClaw: Full 2026 Comparison

Do not index

A few months ago, someone on r/AI_Agents asked a question a lot of people are quietly Googling:

"Is there a good breakdown of Paperclip vs Hermes vs OpenClaw vs gbrain/gstack, or combination? I'm a bit confused which service is best for what, how to think about token usage for the different use cases... I'm also confused if the best setup is via VMs/Docker etc."

The top reply was "Following this discussion." Weeks later someone else asked, "Did you ever find an answer or any articles?" Nobody had written one.

So here it is. Full disclosure first: we run Agent37, a managed hosting service for OpenClaw and Hermes. We make money when you decide that babysitting a VPS is not how you want to spend your weekend. That bias is on the table, and the comparison below is straight anyway, because a dishonest comparison would be useless to you and embarrassing for us.

The one-paragraph answer

These four things are not competitors. They are different layers of the same stack, and the confusion comes from all of them being labeled "AI agent stuff."

Paperclip is a management layer. It organizes a team of agents into an org chart with budgets and tickets.

Hermes is the agent itself: an autonomous personal assistant by Nous Research that builds memory and skills over time.

OpenClaw is a gateway plus assistant: it connects WhatsApp, Telegram, Discord, Slack, iMessage and 20+ other chat apps to an AI agent.

gstack is a skill pack for coding agents like Claude Code, and gbrain is a memory layer that any of these agents can plug into.

You can run one, two, or all four. Which ones you need depends on your use case, so let's get specific.

What each tool actually is

Paperclip: the org chart for your agents

Paperclip frames itself as "the app people use to manage AI agents for work." You act as a board of directors. Agents get roles, reporting lines, job descriptions, and goals that trace back to a mission. Work flows through structured tickets with audit trails, and agents wake up on schedules or mentions via a heartbeat system.

Two things make it distinctive. First, it is unopinionated about runtimes: it orchestrates Claude Code, Codex, Gemini, Cursor, or custom agents rather than replacing them. Second, cost control is built in. Every agent gets a monthly budget, you get a warning at 80 percent, and the agent auto-pauses at 100 percent.

It is MIT licensed and self-hosted. npx paperclipai onboard --yes gets you running locally on Node with an embedded Postgres.

Honest trade-off: Paperclip is only as good as the agents underneath it. If you have one agent doing one job, an org chart is overhead, not leverage.

Hermes: the agent that grows with you

Hermes Agent is an open-source (MIT) autonomous agent from Nous Research, released in early 2026. Its pitch is the closed learning loop: it curates its own memory, writes new skills as readable Markdown files based on what it observes, and improves those skills during use. Cross-session recall runs on FTS5 plus LLM summarization, so it genuinely stops asking you the same questions twice.

It ships with 60+ built-in tools, MCP support, scheduled automations, and a gateway that reaches 20+ messaging platforms. For deployment it supports six terminal backends: local, Docker, SSH, Daytona, Singularity, and Modal. It runs fine on a $5 VPS. Model-wise it works with Nous Portal, OpenRouter, OpenAI, or any custom endpoint.

Honest trade-off: the learning loop spends tokens on summarization and skill writing that a stateless bot would not. You are paying a memory tax early for compounding returns later. And as a younger project, its ecosystem is smaller than OpenClaw's.

OpenClaw: the gateway with the massive ecosystem

OpenClaw (formerly Clawdbot, then Moltbot) is the most popular project in this list by a wide margin, with hundreds of thousands of GitHub stars. It is a self-hosted gateway that connects chat apps to AI agents: WhatsApp, Telegram, Slack, Discord, Signal, iMessage, Teams, Matrix and many more via channel plugins.

It is model-agnostic (Anthropic, OpenAI, Gemini, DeepSeek, or a local Ollama instance for zero-cost inference) and has strong operational visibility: /status shows your session model, context usage, last response tokens, and estimated cost. The plugin and skills ecosystem is enormous.

Honest trade-off: OpenClaw expects to run always-on with real API keys on a machine you must secure yourself, and a whole genre of Reddit posts exists about people feeling uneasy handing it credentials. It is a powerful tool that assumes an operator. That is exactly the gap managed hosting (including ours) exists to fill.

gbrain and gstack: memory and skills, not agents

gstack is Garry Tan's packaged Claude Code setup: 23 opinionated skills that act as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA inside your coding agent. It works across Claude Code, Codex CLI, Cursor, and several other runtimes. It is not an agent; it is a set of workflows your coding agent follows.

gbrain is the memory layer: vector search (pgvector) plus BM25 plus a self-wiring knowledge graph, exposed as 30+ MCP tools. It runs locally on PGLite or on Supabase/Postgres for multi-machine setups. Notably, Tan describes gbrain as the production memory backbone for his own OpenClaw and Hermes deployments, feeding agents that run dozens of cron jobs.

Honest trade-off: both assume you live in a coding agent already. If your use case is "text my assistant on WhatsApp," gstack is irrelevant and gbrain is optional.

Side-by-side comparison

	Paperclip	Hermes	OpenClaw	gbrain/gstack
What it is	Multi-agent orchestration	Autonomous personal agent	Chat-app gateway + assistant	Memory layer + coding skills
Best for	Managing a team of agents	One agent that learns you	Reaching agents from any chat app	Supercharging coding agents
Runs as	Local Node app	Always-on process, 6 backends	Always-on gateway	Library/MCP inside other agents
License	MIT	MIT	Open source	Open source
Token profile	Multiplies per agent, hard budgets	Memory tax, compounds	Per message + background jobs	Reduces coding-session waste
Ecosystem size	Small, growing	Medium	Very large	Medium

Hermes vs OpenClaw: the overlap that confuses everyone

This is the comparison people actually mean when they ask. Both connect to your chat apps. Both run always-on. Both do scheduled tasks. So which one?

Think of it this way: OpenClaw is a gateway that acquired an assistant. Hermes is an assistant that acquired a gateway.

Pick OpenClaw when integration breadth matters most: the widest channel support, the biggest plugin ecosystem, the most community answers when something breaks, and easy model swapping down to free local inference.

Pick Hermes when the agent's intelligence over time matters most: persistent memory, self-authored skills, and an architecture designed around one agent knowing you deeply rather than many channels fanning into a session.

Plenty of people run both. That is not indecision; it is layering, and gbrain existing specifically to serve OpenClaw and Hermes deployments tells you the community already treats them as complementary.

How to think about token usage per use case

The OP asked this directly, and it is the right question because architecture drives token burn more than model choice does.

Chat gateway use (OpenClaw): cost scales with messages. Each turn carries the system prompt plus session context, so long rambling sessions cost more per reply. Idle time is free until you add heartbeats and cron jobs, which quietly burn tokens around the clock. Use /status to watch context size, route casual chat to a cheap model, and reserve Claude or GPT-class models for hard tasks. Ollama drops inference cost to zero if you have the hardware.

Personal agent use (Hermes): expect overhead beyond raw chat, because memory curation, summarization, and skill writing all spend tokens. The payoff is that a skill written once runs cheaply forever after, so cost per task trends down over weeks while a stateless setup stays flat.

Multi-agent orgs (Paperclip): whatever one agent costs, multiply by headcount, plus heartbeat polling per agent. This is exactly why Paperclip ships hard per-agent budgets with auto-pause. Set them on day one.

Coding (gstack + gbrain): coding sessions burn tokens on exploration, with the agent grepping and re-reading files to build context. gbrain's semantic search returns ranked, relevant regions instead, which cuts that waste. gstack's structured workflows reduce expensive wandering. Here the tooling reduces net spend.

When combining them makes sense

The OP floated "Paperclip + Hermes for coding vs gstack + OpenClaw for recurring tasks." Close, but we would redraw the lines:

gstack + gbrain + Claude Code for coding. This is the natural stack; gstack was built for it.

OpenClaw or Hermes as your always-on personal layer, reachable from WhatsApp or Telegram, running your recurring jobs via cron or scheduled automations. You rarely need both on day one; start with one.

gbrain across everything once you run more than one agent, so your coding agent and your chat agent share one memory instead of two half-memories.

Paperclip on top only when you genuinely have multiple agents doing real delegated work and you need governance, tickets, and budget caps. Do not start here.

The layering rule: gateway (OpenClaw) or agent (Hermes) at the bottom, memory (gbrain) beside it, skills (gstack) inside your coding agent, orchestration (Paperclip) on top when scale demands it.

Docker, VPS, or managed: the setup question

Everything above except gstack wants to be always-on, which gives you three real options.

Your own machine or Docker at home: free and private, but your laptop sleeps, your IP changes, and your agent dies mid-task. Fine for evaluation, frustrating for daily reliance.

A $5 VPS: the classic route, and Hermes explicitly targets it. You get real uptime, but you inherit the ops: securing a public box that holds your actual API keys, unattended upgrades, restart hooks, and the 2am debugging when a channel pairing breaks. If you enjoy that work, genuinely, do this.

Managed hosting: someone else runs the container, keeps it patched, survives image updates, and gives you the dashboard. The trade-off is real too: you are trusting a provider with your instance, and if fully local privacy is the entire reason you chose a self-hosted agent, hosting it anywhere (including with us) changes that math. We would rather tell you that than have you find out annoyed.

Which should you pick?

You want an AI you can text from WhatsApp or Telegram that handles tasks and recurring jobs: OpenClaw.

You want one assistant that remembers everything and gets smarter every week: Hermes.

You want your coding agent to stop re-exploring your repo and follow real workflows: gstack, with gbrain.

You are running three or more agents and losing track of who is doing what and spending what: Paperclip.

You want the always-on agent without owning a server: managed hosting for OpenClaw or Hermes.

Skip the VPS weekend

If the OpenClaw or Hermes column won, the only question left is who runs the box. Agent37 deploys a hosted OpenClaw or Hermes instance in one click: always-on, kept alive through restarts and image updates, with channels, model providers, and networking managed from one dashboard. Plans start at $4/month, which is less than the VPS you would otherwise be patching.

Your agent should be working while you sleep, not the other way around. Deploy one at agent37.com and text it from your phone in minutes.

Paperclip vs Hermes vs OpenClaw (and Where gbrain/gstack Fits): The Breakdown Nobody Wrote