A
CrewAI
95.6
61,027 stars · MIT
AI Agents
ruflo leads by 2.3 · narrow
A
95.6
61,027 stars · MIT
B · leads
97.9
81,931 stars · MIT
CrewAI versus ruflo is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. CrewAI is written mainly in Python; ruflo is written mainly in TypeScript. The composite score is 95.6 for CrewAI and 97.9 for ruflo.
ruflo has 81,931 GitHub stars to CrewAI's 61,027, a gap of 20,904 (1.34×). Forks are 9,211 for CrewAI and 9,668 for ruflo. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 100 versus 100.
Push history: CrewAI was last pushed on 17 November 2026 (0 days ago), and ruflo was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,276 for CrewAI (0.021 per star) and 614 for ruflo (0.007 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
Both CrewAI and ruflo 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 ruflo (81,931 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, ruflo is open source.
ruflo 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).
ruflo finishes ahead at 97.9 against CrewAI at 95.6, a 2.3 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 | ruflo |
|---|---|---|
| GitHub stars | 61,027 | 81,931 |
| Forks | 9,211 | 9,668 |
| Open issues | 1,276 | 614 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.6 | 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.
🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
ruflo has more GitHub stars: 81,931 versus 61,027 for CrewAI. The gap is 20,904 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both CrewAI and ruflo 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. ruflo 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.
ruflo scores 97.9 and CrewAI scores 95.6. This page calls that a narrow lead for ruflo.