A
loop-engineering
86.5
11,796 stars · MIT
Workflow Automation
n8n leads by 4.5 · narrow
A
86.5
11,796 stars · MIT
B · leads
91.0
210,804 stars · Sustainable Use License
loop-engineering 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 86.5 for loop-engineering and 91.0 for n8n.
n8n has 210,804 GitHub stars to loop-engineering's 11,796, a gap of 199,008 (17.87×). Forks are 1,583 for loop-engineering and 61,571 for n8n. On the log scale used inside this pair, adoption is 76 versus 100, and the fork community is 67 versus 100.
Push history: loop-engineering was last pushed on 17 November 2026 (0 days ago), and n8n was last pushed on 17 November 2026 (0 days ago). Open issues stand at 23 for loop-engineering (0.002 per star) and 1,266 for n8n (0.006 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
loop-engineering 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. 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 96 for loop-engineering and 38 for n8n. This is a procurement signal, not legal advice.
In Workflow Automation, both loop-engineering (11,796 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: loop-engineering is open source, n8n is freemium.
The lead is split. loop-engineering is furthest ahead on license flexibility (96 to 38), while n8n is furthest ahead on fork community (100 to 67). Choose the dimension a rollout cannot compromise on.
n8n finishes ahead at 91.0 against loop-engineering at 86.5, a 4.5 point narrow 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 | loop-engineering | n8n |
|---|---|---|
| GitHub stars | 11,796 | 210,804 |
| Forks | 1,583 | 61,571 |
| Open issues | 23 | 1,266 |
| Adoption | 76 | 100 |
| Activity | 100 | 100 |
| Community | 67 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 38 |
| Self-hosting | 100 | 100 |
| Composite | 86.5 | 91.0 |
Practical patterns, starters & CLI tools for loop engineering with AI coding agents. Design systems that prompt and orchestrate agents (inspired by Addy Osmani and Boris Cherny). Includes loop-audit, loop-init, loop-cost.
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 11,796 for loop-engineering. The gap is 199,008 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both loop-engineering and n8n as self-hostable. Confirm each project's deploy docs before you plan a migration.
loop-engineering 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. 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 loop-engineering scores 86.5. This page calls that a narrow lead for n8n.