A · leads
browser-use
99.1
121,292 stars · MIT
AI Agents
browser-use leads by 3.6 · narrow
A · leads
99.1
121,292 stars · MIT
B
95.5
69,113 stars · Apache-2.0
browser-use versus mem0 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 95.5 for mem0.
browser-use has 121,292 GitHub stars to mem0's 69,113, a gap of 52,179 (1.75×). Forks are 13,561 for browser-use and 8,226 for mem0. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 95.
Push history: browser-use was last pushed on 17 November 2026 (0 days ago), and mem0 was last pushed on 17 November 2026 (0 days ago). Open issues stand at 596 for browser-use (0.005 per star) and 963 for mem0 (0.014 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. mem0 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 mem0. This is a procurement signal, not legal advice.
In AI Agents, both browser-use (121,292 stars) and mem0 (69,113 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, mem0 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 mem0 at 95.5, a 3.6 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 | mem0 |
|---|---|---|
| GitHub stars | 121,292 | 69,113 |
| Forks | 13,561 | 8,226 |
| Open issues | 596 | 963 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 95 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 95.5 |
Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.
The Memory Layer for AI Agents - Drop-in memory infrastructure for AI agents and apps. Context that persists. Built for production.
browser-use has more GitHub stars: 121,292 versus 69,113 for mem0. The gap is 52,179 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both browser-use and mem0 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. mem0 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.
browser-use scores 99.1 and mem0 scores 95.5. This page calls that a narrow lead for browser-use.