A
CrewAI
90.2
61,027 stars · MIT
AI Agents
hermes-agent leads by 2.7 · narrow
A
90.2
61,027 stars · MIT
B · leads
92.9
264,096 stars · MIT
CrewAI versus hermes-agent 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 90.2 for CrewAI and 92.9 for hermes-agent.
hermes-agent has 264,096 GitHub stars to CrewAI's 61,027, a gap of 203,069 (4.33×). Forks are 9,211 for CrewAI and 59,569 for hermes-agent. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 83 versus 100.
Push history: CrewAI was last pushed on 17 November 2026 (0 days ago), and hermes-agent was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,276 for CrewAI (0.021 per star) and 53,403 for hermes-agent (0.202 per star). Issue-health scores are 70 and 34; activity scores are 100 and 100.
Both CrewAI and hermes-agent are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In AI Agents, both CrewAI (61,027 stars) and hermes-agent (264,096 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: CrewAI is open source, hermes-agent is open source.
The lead is split. CrewAI is furthest ahead on issue health (70 to 34), while hermes-agent is furthest ahead on fork community (100 to 83). Choose the dimension a rollout cannot compromise on.
hermes-agent finishes ahead at 92.9 against CrewAI at 90.2, a 2.7 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 | CrewAI | hermes-agent |
|---|---|---|
| GitHub stars | 61,027 | 264,096 |
| Forks | 9,211 | 59,569 |
| Open issues | 1,276 | 53,403 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 83 | 100 |
| Issue health | 70 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.2 | 92.9 |
CrewAI is a framework for multi-agent workflows where role-based agents delegate tasks. It is a code library first, used by teams building their own agent systems.
The agent that grows with you
hermes-agent has more GitHub stars: 264,096 versus 61,027 for CrewAI. The gap is 203,069 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both CrewAI and hermes-agent as self-hostable. Confirm each project's deploy docs before you plan a migration.
CrewAI 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
hermes-agent scores 92.9 and CrewAI scores 90.2. This page calls that a narrow lead for hermes-agent.