A
CrewAI
94.1
61,027 stars · MIT
AI Agents
gemini-cli leads by 3.8 · narrow
A
94.1
61,027 stars · MIT
B · leads
97.9
108,897 stars · Apache-2.0
CrewAI versus gemini-cli 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; gemini-cli is written mainly in TypeScript. The composite score is 94.1 for CrewAI and 97.9 for gemini-cli.
gemini-cli has 108,897 GitHub stars to CrewAI's 61,027, a gap of 47,870 (1.78×). Forks are 9,211 for CrewAI and 14,956 for gemini-cli. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 95 versus 100.
Push history: CrewAI was last pushed on 17 November 2026 (0 days ago), and gemini-cli was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,276 for CrewAI (0.021 per star) and 739 for gemini-cli (0.007 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. gemini-cli 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 gemini-cli. This is a procurement signal, not legal advice.
In AI Agents, both CrewAI (61,027 stars) and gemini-cli (108,897 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, gemini-cli is open source.
gemini-cli 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).
gemini-cli finishes ahead at 97.9 against CrewAI at 94.1, a 3.8 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 | gemini-cli |
|---|---|---|
| GitHub stars | 61,027 | 108,897 |
| Forks | 9,211 | 14,956 |
| Open issues | 1,276 | 739 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.1 | 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.
An open-source AI agent that brings the power of Gemini directly into your terminal.
gemini-cli has more GitHub stars: 108,897 versus 61,027 for CrewAI. The gap is 47,870 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both CrewAI and gemini-cli 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. gemini-cli 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.
gemini-cli scores 97.9 and CrewAI scores 94.1. This page calls that a narrow lead for gemini-cli.