A
n8n-as-code
75.1
1,663 stars · MIT
Workflow Automation
puppeteer leads by 24.0 · decisive
A
75.1
1,663 stars · MIT
B · leads
99.1
95,849 stars · Apache-2.0
n8n-as-code 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 75.1 for n8n-as-code and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to n8n-as-code's 1,663, a gap of 94,186 (57.64×). Forks are 190 for n8n-as-code and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 65 versus 100, and the fork community is 57 versus 100.
Push history: n8n-as-code was last pushed on 01 November 2026 (16 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 20 for n8n-as-code (0.012 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 84 and 96; activity scores are 78 and 100.
n8n-as-code 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. 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 96 for n8n-as-code and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both n8n-as-code (1,663 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: n8n-as-code is open source, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is fork community at 43 points (57 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against n8n-as-code at 75.1, a 24.0 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 | n8n-as-code | puppeteer |
|---|---|---|
| GitHub stars | 1,663 | 95,849 |
| Forks | 190 | 9,607 |
| Open issues | 20 | 201 |
| Adoption | 65 | 100 |
| Activity | 78 | 100 |
| Community | 57 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 75.1 | 99.1 |
Give your AI agent n8n superpowers. 537 nodes with full schemas, 7,700+ templates, Git-like sync, and TypeScript workflows.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 1,663 for n8n-as-code. The gap is 94,186 stars.
puppeteer was pushed more recently: 17 November 2026 versus 01 November 2026 for n8n-as-code. That is 16 days apart.
Yes. This catalog marks both n8n-as-code and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
n8n-as-code 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. 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 n8n-as-code scores 75.1. This page calls that a decisive lead for puppeteer.