A · leads
hermes-agent
92.9
264,096 stars · MIT
AI Agents
hermes-agent leads by 1.1 · narrow
A · leads
92.9
264,096 stars · MIT
B
91.8
69,113 stars · Apache-2.0
hermes-agent versus mem0 is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 92.9 for hermes-agent and 91.8 for mem0.
hermes-agent has 264,096 GitHub stars to mem0's 69,113, a gap of 194,983 (3.82×). Forks are 59,569 for hermes-agent and 8,226 for mem0. On the log scale used inside this pair, adoption is 100 versus 89, and the fork community is 100 versus 82.
Push history: hermes-agent was last pushed on 17 November 2026 (0 days ago), and mem0 was last pushed on 17 November 2026 (0 days ago). Open issues stand at 53,403 for hermes-agent (0.202 per star) and 963 for mem0 (0.014 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
hermes-agent is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. mem0 is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for hermes-agent and 96 for mem0. This is a procurement signal, not legal advice.
In AI Agents, both hermes-agent (264,096 stars) and mem0 (69,113 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: hermes-agent is open source, mem0 is open source.
The lead is split. hermes-agent is furthest ahead on fork community (100 to 82), while mem0 is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
hermes-agent finishes ahead at 92.9 against mem0 at 91.8, a 1.1 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | hermes-agent | mem0 |
|---|---|---|
| GitHub stars | 264,096 | 69,113 |
| Forks | 59,569 | 8,226 |
| Open issues | 53,403 | 963 |
| Adoption | 100 | 89 |
| Activity | 100 | 100 |
| Community | 100 | 82 |
| Issue health | 34 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 91.8 |
The agent that grows with you
The Memory Layer for AI Agents - Drop-in memory infrastructure for AI agents and apps. Context that persists. Built for production.
hermes-agent has more GitHub stars: 264,096 versus 69,113 for mem0. The gap is 194,983 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both hermes-agent and mem0 as self-hostable. Confirm each project's deploy docs before you plan a migration.
hermes-agent is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. mem0 is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
hermes-agent scores 92.9 and mem0 scores 91.8. This page calls that a narrow lead for hermes-agent.