A · leads
paperclip
94.7
114,484 stars · MIT
Workflow Automation
paperclip leads by 9.4 · clear
A · leads
94.7
114,484 stars · MIT
B
85.3
11,990 stars · Apache-2.0
paperclip versus robotframework is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. paperclip is written mainly in TypeScript; robotframework is written mainly in Python. The composite score is 94.7 for paperclip and 85.3 for robotframework.
paperclip has 114,484 GitHub stars to robotframework's 11,990, a gap of 102,494 (9.55×). Forks are 18,987 for paperclip and 2,589 for robotframework. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 80.
Push history: paperclip was last pushed on 17 November 2026 (0 days ago), and robotframework was last pushed on 11 November 2026 (6 days ago). Open issues stand at 6,806 for paperclip (0.059 per star) and 322 for robotframework (0.027 per star). Issue-health scores are 52 and 70; activity scores are 100 and 92.
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. robotframework 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. License scores in this pair are 96 for paperclip and 96 for robotframework. This is a procurement signal, not legal advice.
In Workflow Automation, both paperclip (114,484 stars) and robotframework (11,990 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: paperclip is open source, robotframework is open source.
The lead is split. paperclip is furthest ahead on fork community (100 to 80), while robotframework is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
paperclip finishes ahead at 94.7 against robotframework at 85.3, a 9.4 point clear 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 | paperclip | robotframework |
|---|---|---|
| GitHub stars | 114,484 | 11,990 |
| Forks | 18,987 | 2,589 |
| Open issues | 6,806 | 322 |
| Adoption | 100 | 81 |
| Activity | 100 | 92 |
| Community | 100 | 80 |
| Issue health | 52 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 85.3 |
The open-source app everyone uses to manage agents at work
Generic automation framework for acceptance testing and RPA
paperclip has more GitHub stars: 114,484 versus 11,990 for robotframework. The gap is 102,494 stars.
paperclip was pushed more recently: 17 November 2026 versus 11 November 2026 for robotframework. That is 6 days apart.
Yes. This catalog marks both paperclip and robotframework as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. robotframework 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
paperclip scores 94.7 and robotframework scores 85.3. This page calls that a clear lead for paperclip.