A · leads
dagster
92.9
16,433 stars · Apache-2.0
Workflow Automation
dagster leads by 15.3 · decisive
A · leads
92.9
16,433 stars · Apache-2.0
B
77.6
2,919 stars · license n/a
dagster versus LoopForge 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; LoopForge is written mainly in Go. The composite score is 92.9 for dagster and 77.6 for LoopForge.
dagster has 16,433 GitHub stars to LoopForge's 2,919, a gap of 13,514 (5.63×). Forks are 2,425 for dagster and 423 for LoopForge. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 78.
Push history: dagster was last pushed on 17 November 2026 (0 days ago), and LoopForge was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,630 for dagster (0.160 per star) and 176 for LoopForge (0.060 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. LoopForge 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 LoopForge. This is a procurement signal, not legal advice.
In Workflow Automation, both dagster (16,433 stars) and LoopForge (2,919 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, LoopForge is unpriced in this catalog.
The lead is split. dagster is furthest ahead on license flexibility (96 to 30), while LoopForge is furthest ahead on issue health (52 to 34). Choose the dimension a rollout cannot compromise on.
dagster finishes ahead at 92.9 against LoopForge at 77.6, a 15.3 point decisive 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 | LoopForge |
|---|---|---|
| GitHub stars | 16,433 | 2,919 |
| Forks | 2,425 | 423 |
| Open issues | 2,630 | 176 |
| Adoption | 100 | 82 |
| Activity | 100 | 100 |
| Community | 100 | 78 |
| Issue health | 34 | 52 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 77.6 |
An orchestration platform for the development, production, and observation of data assets.
Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.
dagster has more GitHub stars: 16,433 versus 2,919 for LoopForge. The gap is 13,514 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dagster and LoopForge 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. LoopForge 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 LoopForge scores 77.6. This page calls that a decisive lead for dagster.