Skip to content
DevUtils Online

Workflow Automation

AutoHotkey vs n8n

n8n leads by 8.3 · clear

B · leads

n8n

91.0

210,804 stars · Sustainable Use License

AutoHotkey versus n8n is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. AutoHotkey is written mainly in C++; n8n is written mainly in TypeScript. The composite score is 82.7 for AutoHotkey and 91.0 for n8n.

n8n has 210,804 GitHub stars to AutoHotkey's 13,492, a gap of 197,312 (15.62×). Forks are 1,206 for AutoHotkey and 61,571 for n8n. On the log scale used inside this pair, adoption is 78 versus 100, and the fork community is 64 versus 100.

Push history: AutoHotkey was last pushed on 13 November 2026 (3 days ago), and n8n was last pushed on 17 November 2026 (0 days ago). Open issues stand at 13 for AutoHotkey (0.001 per star) and 1,266 for n8n (0.006 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.

AutoHotkey is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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 64 for AutoHotkey and 38 for n8n. This is a procurement signal, not legal advice.

In Workflow Automation, both AutoHotkey (13,492 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: AutoHotkey is open source, n8n is freemium.

The lead is split. AutoHotkey is furthest ahead on license flexibility (64 to 38), while n8n is furthest ahead on fork community (100 to 64). Choose the dimension a rollout cannot compromise on.

n8n finishes ahead at 91.0 against AutoHotkey at 82.7, a 8.3 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

AutoHotkey versus n8n metrics
Signal AutoHotkey n8n
GitHub stars 13,492 210,804
Forks 1,206 61,571
Open issues 13 1,266
Adoption 78 100
Activity 100 100
Community 64 100
Issue health 96 84
License 64 38
Self-hosting 100 100
Composite 82.7 91.0

n8n

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, AutoHotkey or n8n?

n8n has more GitHub stars: 210,804 versus 13,492 for AutoHotkey. The gap is 197,312 stars.

Which was updated more recently, AutoHotkey or n8n?

n8n was pushed more recently: 17 November 2026 versus 13 November 2026 for AutoHotkey. That is 3 days apart.

Can I self-host both AutoHotkey and n8n?

Yes. This catalog marks both AutoHotkey and n8n as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, AutoHotkey or n8n?

AutoHotkey is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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.

Who wins the AutoHotkey vs n8n score?

n8n scores 91.0 and AutoHotkey scores 82.7. This page calls that a clear lead for n8n.

Related comparisons