A
artillery
75.4
9,121 stars · MPL-2.0
Workflow Automation
paperclip leads by 19.3 · decisive
A
75.4
9,121 stars · MPL-2.0
B · leads
94.7
114,484 stars · MIT
artillery 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 75.4 for artillery and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to artillery's 9,121, a gap of 105,363 (12.55×). Forks are 576 for artillery and 18,987 for paperclip. On the log scale used inside this pair, adoption is 78 versus 100, and the fork community is 64 versus 100.
Push history: artillery was last pushed on 20 October 2026 (28 days ago), and paperclip was last pushed on 17 November 2026 (0 days ago). Open issues stand at 491 for artillery (0.054 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 52 and 52; activity scores are 78 and 100.
artillery is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. 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 78 for artillery and 96 for paperclip. This is a procurement signal, not legal advice.
In Workflow Automation, both artillery (9,121 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: artillery is open source, paperclip is open source.
paperclip is ahead on every scored dimension that is not level. Level dimensions: issue health, self-hosting. The widest gap is fork community at 36 points (64 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
paperclip finishes ahead at 94.7 against artillery at 75.4, a 19.3 point decisive 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 | artillery | paperclip |
|---|---|---|
| GitHub stars | 9,121 | 114,484 |
| Forks | 576 | 18,987 |
| Open issues | 491 | 6,806 |
| Adoption | 78 | 100 |
| Activity | 78 | 100 |
| Community | 64 | 100 |
| Issue health | 52 | 52 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 75.4 | 94.7 |
The complete load testing platform. Everything you need for production-grade load tests. Serverless & distributed. Load test with Playwright. Load test HTTP APIs, GraphQL, WebSocket, and more. Use any Node.js module.
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 9,121 for artillery. The gap is 105,363 stars.
paperclip was pushed more recently: 17 November 2026 versus 20 October 2026 for artillery. That is 28 days apart.
Yes. This catalog marks both artillery and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
artillery is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. 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 artillery scores 75.4. This page calls that a decisive lead for paperclip.