A
airflow
94.4
47,513 stars · Apache-2.0
Workflow Automation
puppeteer leads by 3.8 · narrow
A
94.4
47,513 stars · Apache-2.0
B · leads
98.2
95,849 stars · Apache-2.0
airflow versus puppeteer 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; puppeteer is written mainly in TypeScript. The composite score is 94.4 for airflow and 98.2 for puppeteer.
puppeteer has 95,849 GitHub stars to airflow's 47,513, a gap of 48,336 (2.02×). Forks are 18,381 for airflow and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 100 versus 93.
Push history: airflow was last pushed on 17 November 2026 (0 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,931 for airflow (0.041 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
Both airflow and puppeteer 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 puppeteer (95,849 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, puppeteer is open source.
The lead is split. airflow is furthest ahead on fork community (100 to 93), while puppeteer is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
puppeteer finishes ahead at 98.2 against airflow at 94.4, 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 | puppeteer |
|---|---|---|
| GitHub stars | 47,513 | 95,849 |
| Forks | 18,381 | 9,607 |
| Open issues | 1,931 | 201 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 93 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.4 | 98.2 |
Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 47,513 for airflow. The gap is 48,336 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both airflow and puppeteer 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. puppeteer 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.
puppeteer scores 98.2 and airflow scores 94.4. This page calls that a narrow lead for puppeteer.