A
dagster
92.9
16,433 stars · Apache-2.0
Workflow Automation
trigger.dev leads by 4.2 · narrow
A
92.9
16,433 stars · Apache-2.0
B · leads
97.1
16,776 stars · Apache-2.0
dagster versus trigger.dev 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; trigger.dev is written mainly in TypeScript. The composite score is 92.9 for dagster and 97.1 for trigger.dev.
trigger.dev has 16,776 GitHub stars to dagster's 16,433, a gap of 343 (1.02×). Forks are 2,425 for dagster and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 94.
Push history: dagster was last pushed on 17 November 2026 (0 days ago), and trigger.dev was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,630 for dagster (0.160 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
Both dagster and trigger.dev 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 trigger.dev (16,776 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, trigger.dev is open source.
The lead is split. dagster is furthest ahead on fork community (100 to 94), while trigger.dev is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
trigger.dev finishes ahead at 97.1 against dagster at 92.9, a 4.2 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 | trigger.dev |
|---|---|---|
| GitHub stars | 16,433 | 16,776 |
| Forks | 2,425 | 1,534 |
| Open issues | 2,630 | 268 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 94 |
| Issue health | 34 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 97.1 |
An orchestration platform for the development, production, and observation of data assets.
Trigger.dev – build and deploy durable AI agents and workflows
trigger.dev has more GitHub stars: 16,776 versus 16,433 for dagster. The gap is 343 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dagster and trigger.dev 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. trigger.dev 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.
trigger.dev scores 97.1 and dagster scores 92.9. This page calls that a narrow lead for trigger.dev.