A
dagster
88.4
16,433 stars · Apache-2.0
Workflow Automation
Huginn leads by 7.8 · clear
A
88.4
16,433 stars · Apache-2.0
B · leads
96.2
50,561 stars · MIT
dagster versus Huginn 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; Huginn is written mainly in Ruby. The composite score is 88.4 for dagster and 96.2 for Huginn.
Huginn has 50,561 GitHub stars to dagster's 16,433, a gap of 34,128 (3.08×). Forks are 2,425 for dagster and 4,356 for Huginn. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 93 versus 100.
Push history: dagster was last pushed on 17 November 2026 (0 days ago), and Huginn was last pushed on 09 November 2026 (8 days ago). Open issues stand at 2,630 for dagster (0.160 per star) and 692 for Huginn (0.014 per star). Issue-health scores are 34 and 84; activity scores are 100 and 92.
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. Huginn 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 Huginn. This is a procurement signal, not legal advice.
In Workflow Automation, both dagster (16,433 stars) and Huginn (50,561 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, Huginn is open source.
The lead is split. dagster is furthest ahead on recent activity (100 to 92), while Huginn is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
Huginn finishes ahead at 96.2 against dagster at 88.4, a 7.8 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 | Huginn |
|---|---|---|
| GitHub stars | 16,433 | 50,561 |
| Forks | 2,425 | 4,356 |
| Open issues | 2,630 | 692 |
| Adoption | 90 | 100 |
| Activity | 100 | 92 |
| Community | 93 | 100 |
| Issue health | 34 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.4 | 96.2 |
An orchestration platform for the development, production, and observation of data assets.
Huginn is a self-hosted agent system that watches the web and triggers actions from events. It predates the current wave of LLM agents and is closer to a personal IFTTT you run yourself.
Huginn has more GitHub stars: 50,561 versus 16,433 for dagster. The gap is 34,128 stars.
dagster was pushed more recently: 17 November 2026 versus 09 November 2026 for Huginn. That is 8 days apart.
Yes. This catalog marks both dagster and Huginn 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. Huginn 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.
Huginn scores 96.2 and dagster scores 88.4. This page calls that a clear lead for Huginn.