A
archify
97.4
97,376 stars · Apache-2.0
AI Agents
browser-use leads by 1.7 · narrow
A
97.4
97,376 stars · Apache-2.0
B · leads
99.1
121,292 stars · MIT
archify versus browser-use is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. archify is written mainly in JavaScript; browser-use is written mainly in Python. The composite score is 97.4 for archify and 99.1 for browser-use.
browser-use has 121,292 GitHub stars to archify's 97,376, a gap of 23,916 (1.25×). Forks are 6,647 for archify and 13,561 for browser-use. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 92 versus 100.
Push history: archify was last pushed on 17 November 2026 (0 days ago), and browser-use was last pushed on 17 November 2026 (0 days ago). Open issues stand at 368 for archify (0.004 per star) and 596 for browser-use (0.005 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
archify 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. 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. License scores in this pair are 96 for archify and 96 for browser-use. This is a procurement signal, not legal advice.
In AI Agents, both archify (97,376 stars) and browser-use (121,292 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: archify is open source, browser-use is open source.
browser-use 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 8 points (92 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
browser-use finishes ahead at 99.1 against archify at 97.4, a 1.7 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 | archify | browser-use |
|---|---|---|
| GitHub stars | 97,376 | 121,292 |
| Forks | 6,647 | 13,561 |
| Open issues | 368 | 596 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 92 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 99.1 |
Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.
browser-use has more GitHub stars: 121,292 versus 97,376 for archify. The gap is 23,916 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both archify and browser-use as self-hostable. Confirm each project's deploy docs before you plan a migration.
archify 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
browser-use scores 99.1 and archify scores 97.4. This page calls that a narrow lead for browser-use.