A
CrewAI
93.3
61,027 stars · MIT
AI Agents
graphify leads by 4.6 · narrow
A
93.3
61,027 stars · MIT
B · leads
97.9
149,362 stars · Apache-2.0
CrewAI versus graphify 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 93.3 for CrewAI and 97.9 for graphify.
graphify has 149,362 GitHub stars to CrewAI's 61,027, a gap of 88,335 (2.45×). Forks are 9,211 for CrewAI and 14,362 for graphify. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 95 versus 100.
Push history: CrewAI was last pushed on 17 November 2026 (0 days ago), and graphify was last pushed on 16 November 2026 (1 day ago). Open issues stand at 1,276 for CrewAI (0.021 per star) and 1,670 for graphify (0.011 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
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. 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. License scores in this pair are 96 for CrewAI and 96 for graphify. This is a procurement signal, not legal advice.
In AI Agents, both CrewAI (61,027 stars) and graphify (149,362 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, graphify is open source.
graphify is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 14 points (70 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
graphify finishes ahead at 97.9 against CrewAI at 93.3, a 4.6 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 | graphify |
|---|---|---|
| GitHub stars | 61,027 | 149,362 |
| Forks | 9,211 | 14,362 |
| Open issues | 1,276 | 1,670 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.3 | 97.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.
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.
graphify has more GitHub stars: 149,362 versus 61,027 for CrewAI. The gap is 88,335 stars.
CrewAI was pushed more recently: 17 November 2026 versus 16 November 2026 for graphify. That is 1 days apart.
Yes. This catalog marks both CrewAI and graphify 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
graphify scores 97.9 and CrewAI scores 93.3. This page calls that a narrow lead for graphify.