A
artillery
76.5
9,121 stars · MPL-2.0
Workflow Automation
puppeteer leads by 22.6 · decisive
A
76.5
9,121 stars · MPL-2.0
B · leads
99.1
95,849 stars · Apache-2.0
artillery versus puppeteer 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 76.5 for artillery and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to artillery's 9,121, a gap of 86,728 (10.51×). Forks are 576 for artillery and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 69 versus 100.
Push history: artillery was last pushed on 20 October 2026 (28 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 491 for artillery (0.054 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 52 and 96; 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. puppeteer 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 78 for artillery and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both artillery (9,121 stars) and puppeteer (95,849 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, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: self-hosting. The widest gap is issue health at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against artillery at 76.5, a 22.6 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 | puppeteer |
|---|---|---|
| GitHub stars | 9,121 | 95,849 |
| Forks | 576 | 9,607 |
| Open issues | 491 | 201 |
| Adoption | 80 | 100 |
| Activity | 78 | 100 |
| Community | 69 | 100 |
| Issue health | 52 | 96 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 76.5 | 99.1 |
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.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 9,121 for artillery. The gap is 86,728 stars.
puppeteer 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 puppeteer 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. puppeteer 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.
puppeteer scores 99.1 and artillery scores 76.5. This page calls that a decisive lead for puppeteer.