A · leads
airflow
96.5
47,513 stars · Apache-2.0
Workflow Automation
airflow leads by 9.1 · clear
A · leads
96.5
47,513 stars · Apache-2.0
B
87.4
23,434 stars · AGPL-3.0
airflow versus skyvern is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 96.5 for airflow and 87.4 for skyvern.
airflow has 47,513 GitHub stars to skyvern's 23,434, a gap of 24,079 (2.03×). Forks are 18,381 for airflow and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 79.
Push history: airflow was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,931 for airflow (0.041 per star) and 301 for skyvern (0.013 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for airflow and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both airflow (47,513 stars) and skyvern (23,434 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, skyvern is open source.
The lead is split. airflow is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
airflow finishes ahead at 96.5 against skyvern at 87.4, a 9.1 point clear 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 | skyvern |
|---|---|---|
| GitHub stars | 47,513 | 23,434 |
| Forks | 18,381 | 2,246 |
| Open issues | 1,931 | 301 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 79 |
| Issue health | 70 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 87.4 |
Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
Automate browser based workflows with AI
airflow has more GitHub stars: 47,513 versus 23,434 for skyvern. The gap is 24,079 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both airflow and skyvern 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
airflow scores 96.5 and skyvern scores 87.4. This page calls that a clear lead for airflow.