A · leads
browser-use
99.0
121,292 stars · MIT
AI Agents
browser-use leads by 5.0 · narrow
A · leads
99.0
121,292 stars · MIT
B
94.0
127,431 stars · MIT
browser-use versus orca 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; orca is written mainly in TypeScript. The composite score is 99.0 for browser-use and 94.0 for orca.
orca has 127,431 GitHub stars to browser-use's 121,292, a gap of 6,139 (1.05×). Forks are 13,561 for browser-use and 8,082 for orca. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 95.
Push history: browser-use was last pushed on 17 November 2026 (0 days ago), and orca was last pushed on 17 November 2026 (0 days ago). Open issues stand at 596 for browser-use (0.005 per star) and 8,552 for orca (0.067 per star). Issue-health scores are 96 and 52; activity scores are 100 and 100.
Both browser-use and orca 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 orca (127,431 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, orca is open source.
The lead is split. browser-use is furthest ahead on issue health (96 to 52), while orca is furthest ahead on adoption (100 to 100). Choose the dimension a rollout cannot compromise on.
browser-use finishes ahead at 99.0 against orca at 94.0, a 5.0 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 | orca |
|---|---|---|
| GitHub stars | 121,292 | 127,431 |
| Forks | 13,561 | 8,082 |
| Open issues | 596 | 8,552 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 95 |
| Issue health | 96 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.0 | 94.0 |
Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.
Orca lets you run a fleet of coding agents (e.g. Claude Code, Codex) with your own subscription. Available on desktop, mobile and remote runtime.
orca has more GitHub stars: 127,431 versus 121,292 for browser-use. The gap is 6,139 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both browser-use and orca 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. orca 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.0 and orca scores 94.0. This page calls that a narrow lead for browser-use.