Skip to content
DevUtils Online

Workflow Automation

BrowserOS vs paperclip

paperclip leads by 11.7 · clear

B · leads

paperclip

94.7

114,484 stars · MIT

BrowserOS versus paperclip is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. BrowserOS is written mainly in Rust; paperclip is written mainly in TypeScript. The composite score is 83.0 for BrowserOS and 94.7 for paperclip.

paperclip has 114,484 GitHub stars to BrowserOS's 14,379, a gap of 100,105 (7.96×). Forks are 1,552 for BrowserOS and 18,987 for paperclip. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 75 versus 100.

Push history: BrowserOS 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 162 for BrowserOS (0.011 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.

BrowserOS is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for BrowserOS and 96 for paperclip. This is a procurement signal, not legal advice.

In Workflow Automation, both BrowserOS (14,379 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: BrowserOS is open source, paperclip is open source.

The lead is split. BrowserOS is furthest ahead on issue health (84 to 52), while paperclip is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.

paperclip finishes ahead at 94.7 against BrowserOS at 83.0, a 11.7 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

BrowserOS versus paperclip metrics
Signal BrowserOS paperclip
GitHub stars 14,379 114,484
Forks 1,552 18,987
Open issues 162 6,806
Adoption 82 100
Activity 100 100
Community 75 100
Issue health 84 52
License 52 96
Self-hosting 100 100
Composite 83.0 94.7

Questions this page answers

Which has more GitHub stars, BrowserOS or paperclip?

paperclip has more GitHub stars: 114,484 versus 14,379 for BrowserOS. The gap is 100,105 stars.

Which was updated more recently, BrowserOS or paperclip?

Both were last pushed on 17 November 2026.

Can I self-host both BrowserOS and paperclip?

Yes. This catalog marks both BrowserOS and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, BrowserOS or paperclip?

BrowserOS is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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.

Who wins the BrowserOS vs paperclip score?

paperclip scores 94.7 and BrowserOS scores 83.0. This page calls that a clear lead for paperclip.

Related comparisons