A · level
deer-flow
92.8
85,441 stars · MIT
AI Agents
Too close to call · 92.8 to 92.9
A · level
92.8
85,441 stars · MIT
B · level
92.9
264,096 stars · MIT
deer-flow 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 92.8 for deer-flow and 92.9 for hermes-agent.
hermes-agent has 264,096 GitHub stars to deer-flow's 85,441, a gap of 178,655 (3.09×). Forks are 12,046 for deer-flow and 59,569 for hermes-agent. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 86 versus 100.
Push history: deer-flow 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,117 for deer-flow (0.013 per star) and 53,403 for hermes-agent (0.202 per star). Issue-health scores are 84 and 34; activity scores are 100 and 100.
Both deer-flow 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 deer-flow (85,441 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: deer-flow is open source, hermes-agent is open source.
The lead is split. deer-flow is furthest ahead on issue health (84 to 34), while hermes-agent is furthest ahead on fork community (100 to 86). Choose the dimension a rollout cannot compromise on.
Composite score: deer-flow 92.8, hermes-agent 92.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | deer-flow | hermes-agent |
|---|---|---|
| GitHub stars | 85,441 | 264,096 |
| Forks | 12,046 | 59,569 |
| Open issues | 1,117 | 53,403 |
| Adoption | 91 | 100 |
| Activity | 100 | 100 |
| Community | 86 | 100 |
| Issue health | 84 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.8 | 92.9 |
An open-source long-horizon SuperAgent harness that researches, codes, and creates. With the help of sandboxes, memories, tools, skill, subagents and message gateway, it handles different levels of tasks that could take minutes to hours.
The agent that grows with you
hermes-agent has more GitHub stars: 264,096 versus 85,441 for deer-flow. The gap is 178,655 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both deer-flow and hermes-agent as self-hostable. Confirm each project's deploy docs before you plan a migration.
deer-flow 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.
Neither tool clears a one-point margin. deer-flow scores 92.8 and hermes-agent scores 92.9.