A
bruno
91.4
48,427 stars · MIT
Workflow Automation
paperclip leads by 3.3 · narrow
A
91.4
48,427 stars · MIT
B · leads
94.7
114,484 stars · MIT
bruno versus paperclip is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bruno is written mainly in JavaScript; paperclip is written mainly in TypeScript. The composite score is 91.4 for bruno and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to bruno's 48,427, a gap of 66,057 (2.36×). Forks are 3,115 for bruno and 18,987 for paperclip. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 82 versus 100.
Push history: bruno 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 2,002 for bruno (0.041 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
Both bruno and paperclip are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 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: bruno is open source, paperclip is open source.
The lead is split. bruno is furthest ahead on issue health (70 to 52), while paperclip is furthest ahead on fork community (100 to 82). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against bruno at 91.4, a 3.3 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 | bruno | paperclip |
|---|---|---|
| GitHub stars | 48,427 | 114,484 |
| Forks | 3,115 | 18,987 |
| Open issues | 2,002 | 6,806 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 70 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.4 | 94.7 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 48,427 for bruno. The gap is 66,057 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both bruno and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
bruno 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. 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 bruno scores 91.4. This page calls that a narrow lead for paperclip.