A · leads
graphify
94.6
149,362 stars · Apache-2.0
AI Agents
graphify leads by 1.7 · narrow
A · leads
94.6
149,362 stars · Apache-2.0
B
92.9
264,096 stars · MIT
graphify 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 94.6 for graphify and 92.9 for hermes-agent.
hermes-agent has 264,096 GitHub stars to graphify's 149,362, a gap of 114,734 (1.77×). Forks are 14,362 for graphify and 59,569 for hermes-agent. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 87 versus 100.
Push history: graphify was last pushed on 16 November 2026 (1 day ago), and hermes-agent was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,670 for graphify (0.011 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.
graphify 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. 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. License scores in this pair are 96 for graphify and 96 for hermes-agent. This is a procurement signal, not legal advice.
In AI Agents, both graphify (149,362 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: graphify is open source, hermes-agent is open source.
The lead is split. graphify is furthest ahead on issue health (84 to 34), while hermes-agent is furthest ahead on fork community (100 to 87). Choose the dimension a rollout cannot compromise on.
graphify finishes ahead at 94.6 against hermes-agent at 92.9, a 1.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 | graphify | hermes-agent |
|---|---|---|
| GitHub stars | 149,362 | 264,096 |
| Forks | 14,362 | 59,569 |
| Open issues | 1,670 | 53,403 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 87 | 100 |
| Issue health | 84 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.6 | 92.9 |
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
The agent that grows with you
hermes-agent has more GitHub stars: 264,096 versus 149,362 for graphify. The gap is 114,734 stars.
hermes-agent was pushed more recently: 17 November 2026 versus 16 November 2026 for graphify. That is 1 days apart.
Yes. This catalog marks both graphify and hermes-agent as self-hostable. Confirm each project's deploy docs before you plan a migration.
graphify 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. 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.
graphify scores 94.6 and hermes-agent scores 92.9. This page calls that a narrow lead for graphify.