head to head · open source
Browser Use vs local-deep-research
Browser Use has 119,857 GitHub stars, 13,358 forks, 421 open issues and last shipped yesterday. local-deep-research has 9,483 stars, 899 forks, 889 open issues and last shipped yesterday. Browser Use leads on adoption by 1,164% (119,857 vs 9,483 stars). Browser Use is written in Python under MIT; local-deep-research is written in Python under MIT. Browser Use has attracted 11% as many forks as stars, local-deep-research 9%. local-deep-research was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| Browser Use | local-deep-research | |
|---|---|---|
| GitHub stars | ★ 120K | ★ 9.5K |
| License | MIT | MIT |
| Written in | Python | Python |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 13K | ⑂ 899 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Browser Use if
- You weight community size — 120K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick local-deep-research if
- You want the local-deep-research feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Python
- You evaluated both and local-deep-research fits your workflow better
About Browser Use
Navigate the web like a human does. Find an available slot, pick a date and time, handle the CAPTCHA, and book a driving test. Explore more demos and prompts ↗ Which Browser Use do I need? Path 1: Fully Hosted Cloud: Scale up with a fully hosted agent and browser. Path 2: CLI: Automate your own browser tasks. Path 3: Python Library: Run the open source Browser Use agent locally from your own code. Quickstart Path 1: Fully Hosted Cloud Scale browser automation with our hosted agent, stealth browsers, and infrastructure for profiles, recordings, and data policies. Get started with the API ↗ New Google, GitHub, or…
read the full Browser Use overview →
About local-deep-research
Local Deep Research AI powered research assistant for deep, agentic research Performs deep, agentic research using multiple LLMs and search engines with proper citations 🧪 First open source project — fully local on a single RTX 3090 (Qwen3.6 27B) — to report 95% SimpleQA (n=500) and 77% xbench DeepSearch (n=100) on local hardware. See the r/LocalLLaMA announcement and the benchmark dataset. ▶️ Watch Review by The Art Of The Terminal 🚀 What is Local Deep Research? AI research assistant you control. Run locally for privacy, use any LLM and build your own searchable knowledge base. You own your data and see…
read the full local-deep-research overview →
More in Data & Analytics
Related comparisons
More Data Extraction & Web Scraping projects
Compare either of these against the rest of the Data Extraction & Web Scraping field.
Frequently asked questions
Is Browser Use or local-deep-research more popular?
Browser Use has 119,857 GitHub stars and local-deep-research has 9,483. Browser Use has the larger community by that measure.
Are Browser Use and local-deep-research free?
Both are open source. Browser Use is licensed under MIT and local-deep-research under MIT. Neither carries a licence fee.
What is the difference between Browser Use and local-deep-research?
Browser Use is written in Python and local-deep-research in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Browser Use or local-deep-research?
Choose Browser Use if you want the larger community (119,857 stars) or its MIT licence terms. Choose local-deep-research if its feature set, stack or MIT licence fits better. Both are self-hostable.