A
browser-use
97.6
121,292 stars · MIT
AI Agents
Open WebUI leads by 1.5 · narrow
A
97.6
121,292 stars · MIT
B · leads
99.1
158,922 stars · MIT
browser-use versus Open WebUI 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; Open WebUI is written mainly in Svelte. The composite score is 97.6 for browser-use and 99.1 for Open WebUI.
Open WebUI has 158,922 GitHub stars to browser-use's 121,292, a gap of 37,630 (1.31×). Forks are 13,561 for browser-use and 23,097 for Open WebUI. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 95 versus 100.
Push history: browser-use was last pushed on 17 November 2026 (0 days ago), and Open WebUI was last pushed on 17 November 2026 (0 days ago). Open issues stand at 596 for browser-use (0.005 per star) and 208 for Open WebUI (0.001 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
Both browser-use and Open WebUI 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 Open WebUI (158,922 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, Open WebUI is open source.
Open WebUI is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 5 points (95 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Open WebUI finishes ahead at 99.1 against browser-use at 97.6, a 1.5 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 | Open WebUI |
|---|---|---|
| GitHub stars | 121,292 | 158,922 |
| Forks | 13,561 | 23,097 |
| Open issues | 596 | 208 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.6 | 99.1 |
Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.
Open WebUI is a self-hosted chat interface for local and remote language models, including Ollama. It adds users, documents, and tools around the model endpoint.
Open WebUI has more GitHub stars: 158,922 versus 121,292 for browser-use. The gap is 37,630 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both browser-use and Open WebUI 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. Open WebUI 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.
Open WebUI scores 99.1 and browser-use scores 97.6. This page calls that a narrow lead for Open WebUI.