A · leads
dagster
92.9
16,433 stars · Apache-2.0
Workflow Automation
dagster leads by 4.3 · narrow
A · leads
92.9
16,433 stars · Apache-2.0
B
88.6
3,025 stars · Apache-2.0
dagster versus lowdefy is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dagster is written mainly in Python; lowdefy is written mainly in JavaScript. The composite score is 92.9 for dagster and 88.6 for lowdefy.
dagster has 16,433 GitHub stars to lowdefy's 3,025, a gap of 13,408 (5.43×). Forks are 2,425 for dagster and 188 for lowdefy. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 67.
Push history: dagster was last pushed on 17 November 2026 (0 days ago), and lowdefy was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,630 for dagster (0.160 per star) and 15 for lowdefy (0.005 per star). Issue-health scores are 34 and 96; activity scores are 100 and 100.
Both dagster and lowdefy are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both dagster (16,433 stars) and lowdefy (3,025 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: dagster is open source, lowdefy is open source.
The lead is split. dagster is furthest ahead on fork community (100 to 67), while lowdefy is furthest ahead on issue health (96 to 34). Choose the dimension a rollout cannot compromise on.
dagster finishes ahead at 92.9 against lowdefy at 88.6, a 4.3 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 | dagster | lowdefy |
|---|---|---|
| GitHub stars | 16,433 | 3,025 |
| Forks | 2,425 | 188 |
| Open issues | 2,630 | 15 |
| Adoption | 100 | 83 |
| Activity | 100 | 100 |
| Community | 100 | 67 |
| Issue health | 34 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 88.6 |
An orchestration platform for the development, production, and observation of data assets.
Build apps that AI can generate, humans can review, and teams can maintain. Config that works between code and natural language.
dagster has more GitHub stars: 16,433 versus 3,025 for lowdefy. The gap is 13,408 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dagster and lowdefy as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. lowdefy 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
dagster scores 92.9 and lowdefy scores 88.6. This page calls that a narrow lead for dagster.