A · leads
dagster
92.8
16,433 stars · Apache-2.0
Workflow Automation
dagster leads by 3.5 · narrow
A · leads
92.8
16,433 stars · Apache-2.0
B
89.3
17,077 stars · MIT
dagster versus edict 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.8 for dagster and 89.3 for edict.
edict has 17,077 GitHub stars to dagster's 16,433, a gap of 644 (1.04×). Forks are 2,425 for dagster and 1,771 for edict. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 96.
Push history: dagster was last pushed on 17 November 2026 (0 days ago), and edict was last pushed on 28 September 2026 (50 days ago). Open issues stand at 2,630 for dagster (0.160 per star) and 15 for edict (0.001 per star). Issue-health scores are 34 and 96; activity scores are 100 and 58.
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. edict 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 dagster and 96 for edict. This is a procurement signal, not legal advice.
In Workflow Automation, both dagster (16,433 stars) and edict (17,077 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, edict is open source.
The lead is split. dagster is furthest ahead on recent activity (100 to 58), while edict is furthest ahead on issue health (96 to 34). Choose the dimension a rollout cannot compromise on.
dagster finishes ahead at 92.8 against edict at 89.3, a 3.5 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 | edict |
|---|---|---|
| GitHub stars | 16,433 | 17,077 |
| Forks | 2,425 | 1,771 |
| Open issues | 2,630 | 15 |
| Adoption | 100 | 100 |
| Activity | 100 | 58 |
| Community | 100 | 96 |
| Issue health | 34 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.8 | 89.3 |
An orchestration platform for the development, production, and observation of data assets.
🏛️ 三省六部制 · OpenClaw Multi-Agent Orchestration System — 9 specialized AI agents with real-time dashboard, model config, and full audit trails
edict has more GitHub stars: 17,077 versus 16,433 for dagster. The gap is 644 stars.
dagster was pushed more recently: 17 November 2026 versus 28 September 2026 for edict. That is 50 days apart.
Yes. This catalog marks both dagster and edict 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. edict 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.
dagster scores 92.8 and edict scores 89.3. This page calls that a narrow lead for dagster.