A · leads
n8n
91.0
210,804 stars · Sustainable Use License
Workflow Automation
n8n leads by 27.5 · decisive
A · leads
91.0
210,804 stars · Sustainable Use License
B
63.5
1,415 stars · BSD-3-Clause
n8n versus utask is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. n8n is written mainly in TypeScript; utask is written mainly in Go. The composite score is 91.0 for n8n and 63.5 for utask.
n8n has 210,804 GitHub stars to utask's 1,415, a gap of 209,389 (148.98×). Forks are 61,571 for n8n and 105 for utask. On the log scale used inside this pair, adoption is 100 versus 59, and the fork community is 100 versus 42.
Push history: n8n was last pushed on 17 November 2026 (0 days ago), and utask was last pushed on 29 July 2026 (111 days ago). Open issues stand at 1,266 for n8n (0.006 per star) and 85 for utask (0.060 per star). Issue-health scores are 84 and 52; activity scores are 100 and 58.
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. utask is listed as BSD-3-Clause, 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 38 for n8n and 96 for utask. This is a procurement signal, not legal advice.
In Workflow Automation, both n8n (210,804 stars) and utask (1,415 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 is freemium, utask is open source.
The lead is split. n8n is furthest ahead on fork community (100 to 42), while utask is furthest ahead on license flexibility (96 to 38). Choose the dimension a rollout cannot compromise on.
n8n finishes ahead at 91.0 against utask at 63.5, a 27.5 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 | utask |
|---|---|---|
| GitHub stars | 210,804 | 1,415 |
| Forks | 61,571 | 105 |
| Open issues | 1,266 | 85 |
| Adoption | 100 | 59 |
| Activity | 100 | 58 |
| Community | 100 | 42 |
| Issue health | 84 | 52 |
| License | 38 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.0 | 63.5 |
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.
µTask is an automation engine that models and executes business processes declared in yaml. ✏️📋
n8n has more GitHub stars: 210,804 versus 1,415 for utask. The gap is 209,389 stars.
n8n was pushed more recently: 17 November 2026 versus 29 July 2026 for utask. That is 111 days apart.
Yes. This catalog marks both n8n and utask as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. utask is listed as BSD-3-Clause, 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.
n8n scores 91.0 and utask scores 63.5. This page calls that a decisive lead for n8n.