A
nanobrowser
89.5
14,334 stars · Apache-2.0
Workflow Automation
paperclip leads by 5.2 · narrow
A
89.5
14,334 stars · Apache-2.0
B · leads
94.7
114,484 stars · MIT
nanobrowser versus paperclip is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 89.5 for nanobrowser and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to nanobrowser's 14,334, a gap of 100,150 (7.99×). Forks are 1,540 for nanobrowser and 18,987 for paperclip. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 74 versus 100.
Push history: nanobrowser was last pushed on 17 November 2026 (0 days ago), and paperclip was last pushed on 17 November 2026 (0 days ago). Open issues stand at 62 for nanobrowser (0.004 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 96 and 52; activity scores are 100 and 100.
nanobrowser 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. paperclip 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 nanobrowser and 96 for paperclip. This is a procurement signal, not legal advice.
In Workflow Automation, both nanobrowser (14,334 stars) and paperclip (114,484 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: nanobrowser is open source, paperclip is open source.
The lead is split. nanobrowser is furthest ahead on issue health (96 to 52), while paperclip is furthest ahead on fork community (100 to 74). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against nanobrowser at 89.5, a 5.2 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 | nanobrowser | paperclip |
|---|---|---|
| GitHub stars | 14,334 | 114,484 |
| Forks | 1,540 | 18,987 |
| Open issues | 62 | 6,806 |
| Adoption | 82 | 100 |
| Activity | 100 | 100 |
| Community | 74 | 100 |
| Issue health | 96 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.5 | 94.7 |
Open-source AI agent for web automation. Use your real, logged-in browser to automate daily tasks.
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 14,334 for nanobrowser. The gap is 100,150 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nanobrowser and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
nanobrowser 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. paperclip 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.
paperclip scores 94.7 and nanobrowser scores 89.5. This page calls that a narrow lead for paperclip.