A · leads
dagster
92.9
16,433 stars · Apache-2.0
Workflow Automation
dagster leads by 13.0 · clear
A · leads
92.9
16,433 stars · Apache-2.0
B
79.9
12,531 stars · license n/a
dagster 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 92.9 for dagster and 79.9 for keep.
dagster has 16,433 GitHub stars to keep's 12,531, a gap of 3,902 (1.31×). Forks are 2,425 for dagster and 1,555 for keep. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 94.
Push history: dagster 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 2,630 for dagster (0.160 per star) and 708 for keep (0.056 per star). Issue-health scores are 34 and 52; activity scores are 100 and 100.
dagster 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 dagster and 30 for keep. This is a procurement signal, not legal advice.
Only dagster is marked self-hostable here (16,433 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: dagster is open source, keep is unpriced in this catalog.
The lead is split. dagster is furthest ahead on license flexibility (96 to 30), while keep is furthest ahead on issue health (52 to 34). Choose the dimension a rollout cannot compromise on.
dagster finishes ahead at 92.9 against keep at 79.9, a 13.0 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 | dagster | keep |
|---|---|---|
| GitHub stars | 16,433 | 12,531 |
| Forks | 2,425 | 1,555 |
| Open issues | 2,630 | 708 |
| Adoption | 100 | 97 |
| Activity | 100 | 100 |
| Community | 100 | 94 |
| Issue health | 34 | 52 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 92.9 | 79.9 |
An orchestration platform for the development, production, and observation of data assets.
The open-source AIOps and alert management platform
dagster has more GitHub stars: 16,433 versus 12,531 for keep. The gap is 3,902 stars.
dagster was pushed more recently: 17 November 2026 versus 16 November 2026 for keep. That is 1 days apart.
Only dagster is marked self-hostable. keep is not.
dagster 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.
dagster scores 92.9 and keep scores 79.9. This page calls that a clear lead for dagster.