The office
Groxbot
Self-hostable Grok Bot for teams. Named AI teammates in a messaging UI, shared knowledge, each with a cloud computer.
Best forA company that wants AI adoption visible in one office
Compare
Four names show up in every “which agent?” thread. They are not the same layer.
Hermes and OpenClaw are personal agents on your machine. Paperclip is an org chart for agents. Groxbot is the office: multiplayer teammates, a shared knowledge base, and a self-improving organization — while Hermes still leads the solo self-evolving agent loop.
The office
Self-hostable Grok Bot for teams. Named AI teammates in a messaging UI, shared knowledge, each with a cloud computer.
Best forA company that wants AI adoption visible in one office
Personal
Nous Research’s autonomous agent. Persistent memory and skills that grow on one operator’s machine or VPS.
Best forOne person who wants an agent that learns them over time
Personal
Self-hosted gateway plus assistant. Wide chat-app reach (WhatsApp, Telegram, Slack, Discord, and more) and a large skills ecosystem.
Best forOne person who wants to text an agent from every channel
Orchestration
Multi-agent management layer: roles, tickets, budgets. Not an agent itself — it sits on top of workers like Hermes or OpenClaw.
Best forOperators already running several agents who need governance
Multiplayer and a shared knowledge base are where the office wins. Green checks and crosses — no fog.
| Groxbot | Hermes | OpenClaw | Paperclip | |
|---|---|---|---|---|
| MultiplayerWhole team in one office | Agents as employees — not a team chat | |||
| Shared knowledge baseOrg memory from threads | Personal memory only | Personal sessions / skills | ||
| Open source | Fair-code (self-host free for your org) | |||
| Mobile app | Web + Mac now; App Store soon | |||
| Use any model | Whatever each worker uses | |||
| Bring your own key | Via worker agents | |||
| Built-in computer | Your VPS / backends | Your machine or VPS | ||
| Company messaging UI | ||||
| Chat channel gatewayWhatsApp, Telegram, … | Office + integrations; not a personal gateway | Gateway support | ||
| Self-evolving agentAgent improves its own skills | Office skills from work — not a solo learning loop | Install / community skills | ||
| Self-improving organizationTeam knowledge compounds | Budgets and tickets — not shared know-how | |||
| Agent org chart / budgets | ||||
| Self-host |
Pick by the job, not by stars. These layers can compose — they do not all replace each other.
The office
You want named teammates the whole team can sit with — multiplayer, shared knowledge, each bot with a computer.
Personal
You want one personal agent that remembers you and writes its own skills over time.
Personal
You want the widest messaging reach and a big community skill ecosystem on a personal gateway.
Orchestration
You already run several agents and need roles, tickets, and hard budgets — not another chat UI.
Every pairwise vs, plus the full four-way.
Compare
Hermes is a personal agent that learns you. Groxbot is the office the whole team sits in.
Compare
OpenClaw is a personal gateway across chat apps. Groxbot is multiplayer teammates with a shared knowledge base.
Compare
Paperclip orchestrates agents with org charts and budgets. Groxbot is where people hire and message teammates.
Compare
Both are personal. Hermes leans learning loop; OpenClaw leans channel reach. Neither is a team office.
Same motion — named teammates you message — but Groxbot is multiplayer and fair-code so you can self-host. xAI Grok Bot is a closed, hosted product. Do not present Groxbot as xAI Grok Bot.
Yes. Guest runtimes are opt-in per bot and off by default. They dial out to Groxbot. Default teammates use hosted models or a workspace BYOK key.
Hermes and OpenClaw are personal agents on your machine. Groxbot is multiplayer: named teammates, each with a computer, a shared knowledge base, and a messaging UI the whole company can sit in. Guest runtimes are opt-in and off by default.
Paperclip orchestrates a fleet of agents with org charts and budgets. Groxbot is the place people work: hire a Bot, message it, grant tools when it hits a wall. You do not need a workflow builder or a separate management layer to start.
Personal agents keep memory on one machine. Orchestrators track tickets and budgets. Groxbot is built so the whole team shares threads and office knowledge — that is the gap.
Multiplayer + shared knowledge
Name, optional job, how it should work. Open the thread. The first message is a real task.
Request an invite