A · leads
firecrawl
92.7
202,516 stars · AGPL-3.0
AI Agents
firecrawl leads by 16.4 · decisive
A · leads
92.7
202,516 stars · AGPL-3.0
B
76.3
55,573 stars · Apache-2.0
firecrawl versus Flowise 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 92.7 for firecrawl and 76.3 for Flowise.
firecrawl has 202,516 GitHub stars to Flowise's 55,573, a gap of 146,943 (3.64×). Forks are 10,604 for firecrawl and 25,096 for Flowise. On the log scale used inside this pair, adoption is 100 versus 89, and the fork community is 92 versus 100.
Push history: firecrawl was last pushed on 17 November 2026 (0 days ago), and Flowise was last pushed on 13 August 2026 (96 days ago). Open issues stand at 810 for firecrawl (0.004 per star) and 1,033 for Flowise (0.019 per star). Issue-health scores are 96 and 84; activity scores are 100 and 18. Flowise is archived on GitHub, so its activity score is capped.
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. Flowise 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 Flowise. This is a procurement signal, not legal advice.
In AI Agents, both firecrawl (202,516 stars) and Flowise (55,573 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, Flowise is open source.
The lead is split. firecrawl is furthest ahead on recent activity (100 to 18), while Flowise is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
firecrawl finishes ahead at 92.7 against Flowise at 76.3, a 16.4 point decisive 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 | Flowise |
|---|---|---|
| GitHub stars | 202,516 | 55,573 |
| Forks | 10,604 | 25,096 |
| Open issues | 810 | 1,033 |
| Adoption | 100 | 89 |
| Activity | 100 | 18 |
| Community | 92 | 100 |
| Issue health | 96 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.7 | 76.3 |
Supercharge your AI agents with data from the web and beyond. Building the library for superintelligence. 🔥
Flowise is a visual builder for LLM chains and agents on top of libraries such as LangChain. You design a flow in the browser and run it from a self-hosted Node service.
firecrawl has more GitHub stars: 202,516 versus 55,573 for Flowise. The gap is 146,943 stars.
firecrawl was pushed more recently: 17 November 2026 versus 13 August 2026 for Flowise. That is 96 days apart.
Yes. This catalog marks both firecrawl and Flowise 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. Flowise 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.
firecrawl scores 92.7 and Flowise scores 76.3. This page calls that a decisive lead for firecrawl.