A · leads
airflow
96.5
47,513 stars · Apache-2.0
Workflow Automation
airflow leads by 3.8 · narrow
A · leads
96.5
47,513 stars · Apache-2.0
B
92.7
32,478 stars · Apache-2.0
airflow versus conductor 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; conductor is written mainly in Java. The composite score is 96.5 for airflow and 92.7 for conductor.
airflow has 47,513 GitHub stars to conductor's 32,478, a gap of 15,035 (1.46×). Forks are 18,381 for airflow and 1,074 for conductor. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 71.
Push history: airflow was last pushed on 17 November 2026 (0 days ago), and conductor was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,931 for airflow (0.041 per star) and 300 for conductor (0.009 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
Both airflow and conductor are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both airflow (47,513 stars) and conductor (32,478 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, conductor is open source.
The lead is split. airflow is furthest ahead on fork community (100 to 71), while conductor is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
airflow finishes ahead at 96.5 against conductor at 92.7, a 3.8 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 | airflow | conductor |
|---|---|---|
| GitHub stars | 47,513 | 32,478 |
| Forks | 18,381 | 1,074 |
| Open issues | 1,931 | 300 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 71 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 92.7 |
Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents
airflow has more GitHub stars: 47,513 versus 32,478 for conductor. The gap is 15,035 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both airflow and conductor 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. conductor 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 conductor scores 92.7. This page calls that a narrow lead for airflow.