Skip to content
DevUtils Online

Workflow Automation

airflow vs keep

airflow leads by 22.6 · decisive

A · leads

airflow

96.5

47,513 stars · Apache-2.0

B

keep

73.9

12,531 stars · license n/a

airflow versus keep 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 73.9 for keep.

airflow has 47,513 GitHub stars to keep's 12,531, a gap of 34,982 (3.79×). Forks are 18,381 for airflow and 1,555 for keep. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 75.

Push history: airflow was last pushed on 17 November 2026 (0 days ago), and keep was last pushed on 16 November 2026 (1 day ago). Open issues stand at 1,931 for airflow (0.041 per star) and 708 for keep (0.056 per star). Issue-health scores are 70 and 52; 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. keep is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for airflow and 30 for keep. This is a procurement signal, not legal advice.

Only airflow is marked self-hostable here (47,513 stars, deploy score 100). keep is not (12,531 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: airflow is open source, keep is unpriced in this catalog.

airflow is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is recent activity at 0 points (100 vs 100).

airflow finishes ahead at 96.5 against keep at 73.9, a 22.6 point decisive 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 keep metrics
Signal airflow keep
GitHub stars 47,513 12,531
Forks 18,381 1,555
Open issues 1,931 708
Adoption 100 88
Activity 100 100
Community 100 75
Issue health 70 52
License 96 30
Self-hosting 100 35
Composite 96.5 73.9

Questions this page answers

Which has more GitHub stars, airflow or keep?

airflow has more GitHub stars: 47,513 versus 12,531 for keep. The gap is 34,982 stars.

Which was updated more recently, airflow or keep?

airflow was pushed more recently: 17 November 2026 versus 16 November 2026 for keep. That is 1 days apart.

Can I self-host both airflow and keep?

Only airflow is marked self-hostable. keep is not.

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

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. keep is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the airflow vs keep score?

airflow scores 96.5 and keep scores 73.9. This page calls that a decisive lead for airflow.

Related comparisons