A
keep
69.1
12,531 stars · license n/a
Workflow Automation
n8n leads by 21.9 · decisive
A
69.1
12,531 stars · license n/a
B · leads
91.0
210,804 stars · Sustainable Use License
keep versus n8n is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. keep is written mainly in Python; n8n is written mainly in TypeScript. The composite score is 69.1 for keep and 91.0 for n8n.
n8n has 210,804 GitHub stars to keep's 12,531, a gap of 198,273 (16.82×). Forks are 1,555 for keep and 61,571 for n8n. On the log scale used inside this pair, adoption is 77 versus 100, and the fork community is 67 versus 100.
Push history: keep was last pushed on 16 November 2026 (1 day ago), and n8n was last pushed on 17 November 2026 (0 days ago). Open issues stand at 708 for keep (0.056 per star) and 1,266 for n8n (0.006 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
keep 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 keep and 38 for n8n. This is a procurement signal, not legal advice.
Only n8n is marked self-hostable here (210,804 stars, deploy score 100). keep is not (12,531 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: keep is unpriced in this catalog, n8n is freemium.
n8n is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is self-hosting at 65 points (35 vs 100), and the tightest is recent activity at 0 points (100 vs 100).
n8n finishes ahead at 91.0 against keep at 69.1, a 21.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 | keep | n8n |
|---|---|---|
| GitHub stars | 12,531 | 210,804 |
| Forks | 1,555 | 61,571 |
| Open issues | 708 | 1,266 |
| Adoption | 77 | 100 |
| Activity | 100 | 100 |
| Community | 67 | 100 |
| Issue health | 52 | 84 |
| License | 30 | 38 |
| Self-hosting | 35 | 100 |
| Composite | 69.1 | 91.0 |
The open-source AIOps and alert management platform
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 12,531 for keep. The gap is 198,273 stars.
n8n was pushed more recently: 17 November 2026 versus 16 November 2026 for keep. That is 1 days apart.
Only n8n is marked self-hostable. keep is not.
keep 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 keep scores 69.1. This page calls that a decisive lead for n8n.