A · level
browser-use
97.4
121,292 stars · MIT
AI Agents
Too close to call · 97.4 to 97.9
A · level
97.4
121,292 stars · MIT
B · level
97.9
161,357 stars · Apache-2.0
browser-use versus Dify 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 97.4 for browser-use and 97.9 for Dify.
Dify has 161,357 GitHub stars to browser-use's 121,292, a gap of 40,065 (1.33×). Forks are 13,561 for browser-use and 25,515 for Dify. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 94 versus 100.
Push history: browser-use was last pushed on 17 November 2026 (0 days ago), and Dify was last pushed on 17 November 2026 (0 days ago). Open issues stand at 596 for browser-use (0.005 per star) and 1,422 for Dify (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
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. Dify 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 Dify. This is a procurement signal, not legal advice.
In AI Agents, both browser-use (121,292 stars) and Dify (161,357 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, Dify is open source.
The lead is split. browser-use is furthest ahead on issue health (96 to 84), while Dify is furthest ahead on fork community (100 to 94). Choose the dimension a rollout cannot compromise on.
Composite score: browser-use 97.4, Dify 97.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | Dify |
|---|---|---|
| GitHub stars | 121,292 | 161,357 |
| Forks | 13,561 | 25,515 |
| Open issues | 596 | 1,422 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 94 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 97.9 |
Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.
Dify is a platform for building LLM apps: prompts, RAG pipelines, agents, and observability. It is aimed at teams that want that stack on their own machines.
Dify has more GitHub stars: 161,357 versus 121,292 for browser-use. The gap is 40,065 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both browser-use and Dify 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. Dify 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.
Neither tool clears a one-point margin. browser-use scores 97.4 and Dify scores 97.9.