A · leads
browser-use
99.1
121,292 stars · MIT
AI Agents
browser-use leads by 2.8 · narrow
A · leads
99.1
121,292 stars · MIT
B
96.3
81,931 stars · MIT
browser-use versus ruflo 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; ruflo is written mainly in TypeScript. The composite score is 99.1 for browser-use and 96.3 for ruflo.
browser-use has 121,292 GitHub stars to ruflo's 81,931, a gap of 39,361 (1.48×). Forks are 13,561 for browser-use and 9,668 for ruflo. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 96.
Push history: browser-use was last pushed on 17 November 2026 (0 days ago), and ruflo was last pushed on 17 November 2026 (0 days ago). Open issues stand at 596 for browser-use (0.005 per star) and 614 for ruflo (0.007 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both browser-use and ruflo 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 ruflo (81,931 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, ruflo 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 12 points (96 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
browser-use finishes ahead at 99.1 against ruflo at 96.3, a 2.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 | browser-use | ruflo |
|---|---|---|
| GitHub stars | 121,292 | 81,931 |
| Forks | 13,561 | 9,668 |
| Open issues | 596 | 614 |
| Adoption | 100 | 97 |
| Activity | 100 | 100 |
| Community | 100 | 96 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 96.3 |
Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.
🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
browser-use has more GitHub stars: 121,292 versus 81,931 for ruflo. The gap is 39,361 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both browser-use and ruflo 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. ruflo 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 ruflo scores 96.3. This page calls that a narrow lead for browser-use.