A · leads
browser-use
98.3
121,292 stars · MIT
AI Agents
browser-use leads by 20.7 · decisive
A · leads
98.3
121,292 stars · MIT
B
77.6
55,573 stars · Apache-2.0
browser-use versus Flowise is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. browser-use is written mainly in Python; Flowise is written mainly in TypeScript. The composite score is 98.3 for browser-use and 77.6 for Flowise.
browser-use has 121,292 GitHub stars to Flowise's 55,573, a gap of 65,719 (2.18×). Forks are 13,561 for browser-use and 25,096 for Flowise. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 94 versus 100.
Push history: browser-use 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 596 for browser-use (0.005 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.
browser-use 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. 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 96 for browser-use and 96 for Flowise. This is a procurement signal, not legal advice.
In AI Agents, both browser-use (121,292 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: browser-use is open source, Flowise is open source.
The lead is split. browser-use is furthest ahead on recent activity (100 to 18), while Flowise is furthest ahead on fork community (100 to 94). Choose the dimension a rollout cannot compromise on.
browser-use finishes ahead at 98.3 against Flowise at 77.6, a 20.7 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 | browser-use | Flowise |
|---|---|---|
| GitHub stars | 121,292 | 55,573 |
| Forks | 13,561 | 25,096 |
| Open issues | 596 | 1,033 |
| Adoption | 100 | 93 |
| Activity | 100 | 18 |
| Community | 94 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 98.3 | 77.6 |
Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.
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.
browser-use has more GitHub stars: 121,292 versus 55,573 for Flowise. The gap is 65,719 stars.
browser-use was pushed more recently: 17 November 2026 versus 13 August 2026 for Flowise. That is 96 days apart.
Yes. This catalog marks both browser-use and Flowise as self-hostable. Confirm each project's deploy docs before you plan a migration.
browser-use 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. 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.
browser-use scores 98.3 and Flowise scores 77.6. This page calls that a decisive lead for browser-use.