A · leads
browser-use
99.1
121,292 stars · MIT
AI Agents
browser-use leads by 5.2 · narrow
A · leads
99.1
121,292 stars · MIT
B
93.9
61,027 stars · MIT
browser-use versus CrewAI 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 Python. The composite score is 99.1 for browser-use and 93.9 for CrewAI.
browser-use has 121,292 GitHub stars to CrewAI's 61,027, a gap of 60,265 (1.99×). Forks are 13,561 for browser-use and 9,211 for CrewAI. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 96.
Push history: browser-use was last pushed on 17 November 2026 (0 days ago), and CrewAI was last pushed on 17 November 2026 (0 days ago). Open issues stand at 596 for browser-use (0.005 per star) and 1,276 for CrewAI (0.021 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
Both browser-use and CrewAI 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 browser-use (121,292 stars) and CrewAI (61,027 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, CrewAI is open source.
browser-use 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 26 points (96 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
browser-use finishes ahead at 99.1 against CrewAI at 93.9, a 5.2 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 | browser-use | CrewAI |
|---|---|---|
| GitHub stars | 121,292 | 61,027 |
| Forks | 13,561 | 9,211 |
| Open issues | 596 | 1,276 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 96 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 93.9 |
Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.
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.
browser-use has more GitHub stars: 121,292 versus 61,027 for CrewAI. The gap is 60,265 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both browser-use and CrewAI 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
browser-use scores 99.1 and CrewAI scores 93.9. This page calls that a narrow lead for browser-use.