A · leads
airflow
96.5
47,513 stars · Apache-2.0
Workflow Automation
airflow leads by 5.5 · narrow
A · leads
96.5
47,513 stars · Apache-2.0
B
91.0
27,230 stars · MIT
airflow versus vagrant 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; vagrant is written mainly in Ruby. The composite score is 96.5 for airflow and 91.0 for vagrant.
airflow has 47,513 GitHub stars to vagrant's 27,230, a gap of 20,283 (1.74×). Forks are 18,381 for airflow and 4,491 for vagrant. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 86.
Push history: airflow was last pushed on 17 November 2026 (0 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 1,931 for airflow (0.041 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 70 and 70; activity scores are 100 and 92.
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. vagrant 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. License scores in this pair are 96 for airflow and 96 for vagrant. This is a procurement signal, not legal advice.
In Workflow Automation, both airflow (47,513 stars) and vagrant (27,230 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, vagrant is open source.
airflow is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 14 points (100 vs 86), and the tightest is self-hosting at 0 points (100 vs 100).
airflow finishes ahead at 96.5 against vagrant at 91.0, a 5.5 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 | vagrant |
|---|---|---|
| GitHub stars | 47,513 | 27,230 |
| Forks | 18,381 | 4,491 |
| Open issues | 1,931 | 760 |
| Adoption | 100 | 95 |
| Activity | 100 | 92 |
| Community | 100 | 86 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 91.0 |
Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
Vagrant is a tool for building and distributing development environments.
airflow has more GitHub stars: 47,513 versus 27,230 for vagrant. The gap is 20,283 stars.
airflow was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.
Yes. This catalog marks both airflow and vagrant 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. vagrant 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
airflow scores 96.5 and vagrant scores 91.0. This page calls that a narrow lead for airflow.