A
artillery
73.1
9,121 stars · MPL-2.0
Workflow Automation
n8n leads by 17.9 · decisive
A
73.1
9,121 stars · MPL-2.0
B · leads
91.0
210,804 stars · Sustainable Use License
artillery versus n8n 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 73.1 for artillery and 91.0 for n8n.
n8n has 210,804 GitHub stars to artillery's 9,121, a gap of 201,683 (23.11×). Forks are 576 for artillery and 61,571 for n8n. On the log scale used inside this pair, adoption is 74 versus 100, and the fork community is 58 versus 100.
Push history: artillery was last pushed on 20 October 2026 (28 days ago), and n8n was last pushed on 17 November 2026 (0 days ago). Open issues stand at 491 for artillery (0.054 per star) and 1,266 for n8n (0.006 per star). Issue-health scores are 52 and 84; 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. n8n is listed as Sustainable Use License, which this catalog treats as source-available terms, not a standard OSI open-source license. The grant often limits competing hosted services or some commercial uses. License scores in this pair are 78 for artillery and 38 for n8n. This is a procurement signal, not legal advice.
In Workflow Automation, both artillery (9,121 stars) and n8n (210,804 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, n8n is freemium.
The lead is split. artillery is furthest ahead on license flexibility (78 to 38), while n8n is furthest ahead on fork community (100 to 58). Choose the dimension a rollout cannot compromise on.
n8n finishes ahead at 91.0 against artillery at 73.1, a 17.9 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 | n8n |
|---|---|---|
| GitHub stars | 9,121 | 210,804 |
| Forks | 576 | 61,571 |
| Open issues | 491 | 1,266 |
| Adoption | 74 | 100 |
| Activity | 78 | 100 |
| Community | 58 | 100 |
| Issue health | 52 | 84 |
| License | 78 | 38 |
| Self-hosting | 100 | 100 |
| Composite | 73.1 | 91.0 |
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.
n8n is a workflow automation product with a node canvas, self-hosting, and a paid cloud. Its code is source-available under a sustainable-use license, not an OSI open-source license.
n8n has more GitHub stars: 210,804 versus 9,121 for artillery. The gap is 201,683 stars.
n8n 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 n8n 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. n8n is listed as Sustainable Use License, which this catalog treats as source-available terms, not a standard OSI open-source license. The grant often limits competing hosted services or some commercial uses. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
n8n scores 91.0 and artillery scores 73.1. This page calls that a decisive lead for n8n.