A · leads
n8n
91.0
210,804 stars · Sustainable Use License
Workflow Automation
n8n leads by 7.1 · clear
A · leads
91.0
210,804 stars · Sustainable Use License
B
83.9
10,907 stars · Apache-2.0
n8n versus robotgo 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; robotgo is written mainly in Go. The composite score is 91.0 for n8n and 83.9 for robotgo.
n8n has 210,804 GitHub stars to robotgo's 10,907, a gap of 199,897 (19.33×). Forks are 61,571 for n8n and 968 for robotgo. On the log scale used inside this pair, adoption is 100 versus 76, and the fork community is 100 versus 62.
Push history: n8n was last pushed on 17 November 2026 (0 days ago), and robotgo was last pushed on 13 November 2026 (4 days ago). Open issues stand at 1,266 for n8n (0.006 per star) and 4 for robotgo (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.
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. robotgo 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 38 for n8n and 96 for robotgo. This is a procurement signal, not legal advice.
In Workflow Automation, both n8n (210,804 stars) and robotgo (10,907 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, robotgo is open source.
The lead is split. n8n is furthest ahead on fork community (100 to 62), while robotgo is furthest ahead on license flexibility (96 to 38). Choose the dimension a rollout cannot compromise on.
n8n finishes ahead at 91.0 against robotgo at 83.9, a 7.1 point clear 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 | robotgo |
|---|---|---|
| GitHub stars | 210,804 | 10,907 |
| Forks | 61,571 | 968 |
| Open issues | 1,266 | 4 |
| Adoption | 100 | 76 |
| Activity | 100 | 92 |
| Community | 100 | 62 |
| Issue health | 84 | 96 |
| License | 38 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.0 | 83.9 |
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.
RobotGo, Go Native cross-platform RPA, GUI automation, Auto test and Computer use @vcaesar
n8n has more GitHub stars: 210,804 versus 10,907 for robotgo. The gap is 199,897 stars.
n8n was pushed more recently: 17 November 2026 versus 13 November 2026 for robotgo. That is 4 days apart.
Yes. This catalog marks both n8n and robotgo 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. robotgo 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.
n8n scores 91.0 and robotgo scores 83.9. This page calls that a clear lead for n8n.