Skip to content
DevUtils Online

Workflow Automation

airflow vs bruno

airflow leads by 2.5 · narrow

A · leads

airflow

96.5

47,513 stars · Apache-2.0

B

bruno

94.0

48,427 stars · MIT

airflow versus bruno 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; bruno is written mainly in JavaScript. The composite score is 96.5 for airflow and 94.0 for bruno.

bruno has 48,427 GitHub stars to airflow's 47,513, a gap of 914 (1.02×). Forks are 18,381 for airflow and 3,115 for bruno. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 82.

Push history: airflow was last pushed on 17 November 2026 (0 days ago), and bruno was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,931 for airflow (0.041 per star) and 2,002 for bruno (0.041 per star). Issue-health scores are 70 and 70; 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. bruno 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 bruno. This is a procurement signal, not legal advice.

In Workflow Automation, both airflow (47,513 stars) and bruno (48,427 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, bruno is open source.

The lead is split. airflow is furthest ahead on fork community (100 to 82), while bruno is furthest ahead on adoption (100 to 100). Choose the dimension a rollout cannot compromise on.

airflow finishes ahead at 96.5 against bruno at 94.0, a 2.5 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

airflow versus bruno metrics
Signal airflow bruno
GitHub stars 47,513 48,427
Forks 18,381 3,115
Open issues 1,931 2,002
Adoption 100 100
Activity 100 100
Community 100 82
Issue health 70 70
License 96 96
Self-hosting 100 100
Composite 96.5 94.0

Questions this page answers

Which has more GitHub stars, airflow or bruno?

bruno has more GitHub stars: 48,427 versus 47,513 for airflow. The gap is 914 stars.

Which was updated more recently, airflow or bruno?

Both were last pushed on 17 November 2026.

Can I self-host both airflow and bruno?

Yes. This catalog marks both airflow and bruno as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, airflow or bruno?

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. bruno 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.

Who wins the airflow vs bruno score?

airflow scores 96.5 and bruno scores 94.0. This page calls that a narrow lead for airflow.

Related comparisons