A
Activepieces
92.6
25,581 stars · MIT
Workflow Automation
airflow leads by 3.9 · narrow
A
92.6
25,581 stars · MIT
B · leads
96.5
47,513 stars · Apache-2.0
Activepieces versus airflow is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Activepieces is written mainly in TypeScript; airflow is written mainly in Python. The composite score is 92.6 for Activepieces and 96.5 for airflow.
airflow has 47,513 GitHub stars to Activepieces's 25,581, a gap of 21,932 (1.86×). Forks are 4,476 for Activepieces and 18,381 for airflow. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 86 versus 100.
Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and airflow was last pushed on 17 November 2026 (0 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 1,931 for airflow (0.041 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.
Activepieces is listed as MIT, 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. 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. License scores in this pair are 96 for Activepieces and 96 for airflow. This is a procurement signal, not legal advice.
In Workflow Automation, both Activepieces (25,581 stars) and airflow (47,513 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: Activepieces is open source, airflow is open source.
airflow is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 14 points (86 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
airflow finishes ahead at 96.5 against Activepieces at 92.6, a 3.9 point narrow 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 | Activepieces | airflow |
|---|---|---|
| GitHub stars | 25,581 | 47,513 |
| Forks | 4,476 | 18,381 |
| Open issues | 961 | 1,931 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 86 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 96.5 |
Activepieces is a TypeScript workflow tool positioned as a self-hosted automation builder. It focuses on connecting business apps with a visual builder and an MIT-licensed core.
Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
airflow has more GitHub stars: 47,513 versus 25,581 for Activepieces. The gap is 21,932 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Activepieces and airflow as self-hostable. Confirm each project's deploy docs before you plan a migration.
Activepieces is listed as MIT, 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
airflow scores 96.5 and Activepieces scores 92.6. This page calls that a narrow lead for airflow.