A
firecrawl
93.3
202,516 stars · AGPL-3.0
AI Agents
gemini-cli leads by 2.9 · narrow
A
93.3
202,516 stars · AGPL-3.0
B · leads
96.2
108,897 stars · Apache-2.0
firecrawl 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. Both projects are written mainly in TypeScript. The composite score is 93.3 for firecrawl and 96.2 for gemini-cli.
firecrawl has 202,516 GitHub stars to gemini-cli's 108,897, a gap of 93,619 (1.86×). Forks are 10,604 for firecrawl and 14,956 for gemini-cli. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 96 versus 100.
Push history: firecrawl 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 810 for firecrawl (0.004 per star) and 739 for gemini-cli (0.007 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
firecrawl is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for firecrawl and 96 for gemini-cli. This is a procurement signal, not legal advice.
In AI Agents, both firecrawl (202,516 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: firecrawl is open source, gemini-cli is open source.
The lead is split. firecrawl is furthest ahead on issue health (96 to 84), while gemini-cli is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
gemini-cli finishes ahead at 96.2 against firecrawl at 93.3, a 2.9 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 | firecrawl | gemini-cli |
|---|---|---|
| GitHub stars | 202,516 | 108,897 |
| Forks | 10,604 | 14,956 |
| Open issues | 810 | 739 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 96 | 100 |
| Issue health | 96 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.3 | 96.2 |
Supercharge your AI agents with data from the web and beyond. Building the library for superintelligence. 🔥
An open-source AI agent that brings the power of Gemini directly into your terminal.
firecrawl has more GitHub stars: 202,516 versus 108,897 for gemini-cli. The gap is 93,619 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both firecrawl and gemini-cli as self-hostable. Confirm each project's deploy docs before you plan a migration.
firecrawl is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 96.2 and firecrawl scores 93.3. This page calls that a narrow lead for gemini-cli.