A
LoopForge
68.6
2,919 stars · license n/a
Workflow Automation
n8n leads by 22.4 · decisive
A
68.6
2,919 stars · license n/a
B · leads
91.0
210,804 stars · Sustainable Use License
LoopForge versus n8n is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. LoopForge is written mainly in Go; n8n is written mainly in TypeScript. The composite score is 68.6 for LoopForge and 91.0 for n8n.
n8n has 210,804 GitHub stars to LoopForge's 2,919, a gap of 207,885 (72.22×). Forks are 423 for LoopForge and 61,571 for n8n. On the log scale used inside this pair, adoption is 65 versus 100, and the fork community is 55 versus 100.
Push history: LoopForge 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 176 for LoopForge (0.060 per star) and 1,266 for n8n (0.006 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for LoopForge and 38 for n8n. This is a procurement signal, not legal advice.
In Workflow Automation, both LoopForge (2,919 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: LoopForge is unpriced in this catalog, n8n is freemium.
n8n is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is fork community at 45 points (55 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
n8n finishes ahead at 91.0 against LoopForge at 68.6, a 22.4 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 | LoopForge | n8n |
|---|---|---|
| GitHub stars | 2,919 | 210,804 |
| Forks | 423 | 61,571 |
| Open issues | 176 | 1,266 |
| Adoption | 65 | 100 |
| Activity | 100 | 100 |
| Community | 55 | 100 |
| Issue health | 52 | 84 |
| License | 30 | 38 |
| Self-hosting | 100 | 100 |
| Composite | 68.6 | 91.0 |
Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.
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 2,919 for LoopForge. The gap is 207,885 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both LoopForge and n8n as self-hostable. Confirm each project's deploy docs before you plan a migration.
LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 LoopForge scores 68.6. This page calls that a decisive lead for n8n.