A · level
airflow
90.8
47,513 stars · Apache-2.0
Workflow Automation
Too close to call · 90.8 to 91.0
A · level
90.8
47,513 stars · Apache-2.0
B · level
91.0
210,804 stars · Sustainable Use License
airflow versus n8n is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. airflow is written mainly in Python; n8n is written mainly in TypeScript. The composite score is 90.8 for airflow and 91.0 for n8n.
n8n has 210,804 GitHub stars to airflow's 47,513, a gap of 163,291 (4.44×). Forks are 18,381 for airflow and 61,571 for n8n. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 89 versus 100.
Push history: airflow was last pushed on 17 November 2026 (0 days ago), and n8n was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,931 for airflow (0.041 per star) and 1,266 for n8n (0.006 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
airflow 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. 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 96 for airflow and 38 for n8n. This is a procurement signal, not legal advice.
In Workflow Automation, both airflow (47,513 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: airflow is open source, n8n is freemium.
The lead is split. airflow is furthest ahead on license flexibility (96 to 38), while n8n is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
Composite score: airflow 90.8, n8n 91.0. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | airflow | n8n |
|---|---|---|
| GitHub stars | 47,513 | 210,804 |
| Forks | 18,381 | 61,571 |
| Open issues | 1,931 | 1,266 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 89 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 38 |
| Self-hosting | 100 | 100 |
| Composite | 90.8 | 91.0 |
Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
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 47,513 for airflow. The gap is 163,291 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both airflow and n8n as self-hostable. Confirm each project's deploy docs before you plan a migration.
airflow 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. 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.
Neither tool clears a one-point margin. airflow scores 90.8 and n8n scores 91.0.