A · leads
dagster
92.9
16,433 stars · Apache-2.0
Workflow Automation
dagster leads by 13.7 · clear
A · leads
92.9
16,433 stars · Apache-2.0
B
79.2
2,639 stars · MIT
dagster versus shepherd 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.2 for shepherd.
dagster has 16,433 GitHub stars to shepherd's 2,639, a gap of 13,794 (6.23×). Forks are 2,425 for dagster and 227 for shepherd. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 70.
Push history: dagster was last pushed on 17 November 2026 (0 days ago), and shepherd was last pushed on 09 September 2026 (69 days ago). Open issues stand at 2,630 for dagster (0.160 per star) and 13 for shepherd (0.005 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. shepherd 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 shepherd. This is a procurement signal, not legal advice.
In Workflow Automation, both dagster (16,433 stars) and shepherd (2,639 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, shepherd is open source.
The lead is split. dagster is furthest ahead on recent activity (100 to 58), while shepherd is furthest ahead on issue health (96 to 34). Choose the dimension a rollout cannot compromise on.
dagster finishes ahead at 92.9 against shepherd at 79.2, a 13.7 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 | shepherd |
|---|---|---|
| GitHub stars | 16,433 | 2,639 |
| Forks | 2,425 | 227 |
| Open issues | 2,630 | 13 |
| Adoption | 100 | 81 |
| Activity | 100 | 58 |
| Community | 100 | 70 |
| Issue health | 34 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 79.2 |
An orchestration platform for the development, production, and observation of data assets.
A runtime substrate that turns an agent's execution into a reversible, Git-like trace, so meta-agents can observe, fork, replay, and revert any run. Couples agent and environments in a copy-on-write fork ~5x faster than docker commit, with ~95% KV-cache reuse on replay. Framework built for meta-agents to supervise, optimize, and train other agents
dagster has more GitHub stars: 16,433 versus 2,639 for shepherd. The gap is 13,794 stars.
dagster was pushed more recently: 17 November 2026 versus 09 September 2026 for shepherd. That is 69 days apart.
Yes. This catalog marks both dagster and shepherd 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. shepherd 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.9 and shepherd scores 79.2. This page calls that a clear lead for dagster.