Hermes Business and Hermes Enterprise Turn a Solo Agent Into a Team Platform
Every Hermes user has lived the anti-groove of the solo setup: your own API key, your own subscription, your own usage limits, your own little memory store living on your laptop. It works, until a second pair of hands shows up. Then someone is on your account, or you are forwarding keys around a Slack channel, and nobody knows who burned what.
On September 14, Nous Research moved to solve exactly that, announcing on X that "Hermes Agent is open for business" and opening two new tiers built on Nous Portal. If you run Hermes as an open-source side project and have thought about letting a team touch it, this is the change you have been waiting for.
Hermes Business: one wallet, many agents. Business is a team tier of Nous Portal, the unified gateway that already sits behind a single OAuth login for 248 models plus a hosted Tool Gateway for search, images, browser, and external services. Where you once wrangled separate keys per developer, Business gives the whole team one central credit balance. Owners and admins invite members by email and set per-member spending caps from a Team page, and every member sees real usage in the portal.
Two details matter here. First, agents run inside the messaging channels your team already lives in — Telegram, Discord, Slack, WhatsApp — all under one account, with no per-user billing to reconcile. Second, those per-member caps are quiet insurance against the runaway loop: one member's stuck agent can churn through its own cap, not the whole team's balance. That is the difference between a bad afternoon and an invoice no one wants to explain.
Skills: the part that compounds. The most interesting piece is the shared skill library. Any skill a member builds is published to a team library and becomes available to every agent, and the library stays with the organization when an employee walks out the door. Nous frames skills as a knowledge layer that compounds into proprietary internal tooling and IP. Read the fine print and it is worth an honest caveat: what is shared is skills, not individual conversation histories or personal memories. Your teammate's hard-won workflow becomes a team asset; their private context does not come along. For most orgs that is the right boundary, and knowing it up front saves a surprise.
Hermes Enterprise: your stack, your data. For buyers who need more than pooled billing, Enterprise is the self-hosted edition. It runs on infrastructure the customer controls — on-prem or their own cloud — with contract billing, SSO, SLAs, and white-glove onboarding. Because Hermes is model-agnostic, you pair it with open-weight models on your own GPUs or privately hosted models. It is the freedom to self-host you already had, wrapped in a data boundary and a support contract. Nous says it is already deployed at some of the world's largest companies, though it names no customers.
What stays open. Hermes Agent itself remains open source and self-hostable, free to run with any provider. Business and Enterprise are the paid, managed paths on top — and the timing is strategic: the company is reportedly in funding talks at a $1.5 billion valuation, and a team and enterprise product gives that thesis somewhere to land.
For a cost-conscious indie lead, the read is simple: pooled credits and per-member caps solve a real mess, and an org-owned skill library is a genuinely novel draw. Just remember what is shared and what is not — then decide if the convenience is worth the subscription.
(If you found this useful, you might also like the notes on self-hosted AI agents over at Tama.)