Skip to content
DevUtils Online

Workflow Automation

automa vs n8n

n8n leads by 30.7 · decisive

A

automa

60.3

21,723 stars · license n/a

B · leads

n8n

91.0

210,804 stars · Sustainable Use License

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

n8n has 210,804 GitHub stars to automa's 21,723, a gap of 189,081 (9.70×). Forks are 2,341 for automa and 61,571 for n8n. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 70 versus 100.

Push history: automa was last pushed on 02 March 2026 (260 days ago), and n8n was last pushed on 17 November 2026 (0 days ago). Open issues stand at 379 for automa (0.017 per star) and 1,266 for n8n (0.006 per star). Issue-health scores are 84 and 84; activity scores are 36 and 100.

automa 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 automa 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). automa is not (21,723 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: automa is unpriced in this catalog, n8n is freemium.

n8n is ahead on every scored dimension that is not level. Level dimensions: issue health. The widest gap is self-hosting at 65 points (35 vs 100), and the tightest is issue health at 0 points (84 vs 84).

n8n finishes ahead at 91.0 against automa at 60.3, a 30.7 point decisive 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.

automa versus n8n metrics
Signal automa n8n
GitHub stars 21,723 210,804
Forks 2,341 61,571
Open issues 379 1,266
Adoption 82 100
Activity 36 100
Community 70 100
Issue health 84 84
License 30 38
Self-hosting 35 100
Composite 60.3 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, automa or n8n?

n8n has more GitHub stars: 210,804 versus 21,723 for automa. The gap is 189,081 stars.

Which was updated more recently, automa or n8n?

n8n was pushed more recently: 17 November 2026 versus 02 March 2026 for automa. That is 260 days apart.

Can I self-host both automa and n8n?

Only n8n is marked self-hostable. automa is not.

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

automa 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.

Who wins the automa vs n8n score?

n8n scores 91.0 and automa scores 60.3. This page calls that a decisive lead for n8n.

Related comparisons