A · leads
bruno
96.5
48,427 stars · MIT
Workflow Automation
bruno leads by 7.4 · clear
A · leads
96.5
48,427 stars · MIT
B
89.1
16,433 stars · Apache-2.0
bruno versus dagster is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bruno is written mainly in JavaScript; dagster is written mainly in Python. The composite score is 96.5 for bruno and 89.1 for dagster.
bruno has 48,427 GitHub stars to dagster's 16,433, a gap of 31,994 (2.95×). Forks are 3,115 for bruno and 2,425 for dagster. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 97.
Push history: bruno was last pushed on 17 November 2026 (0 days ago), and dagster was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,002 for bruno (0.041 per star) and 2,630 for dagster (0.160 per star). Issue-health scores are 70 and 34; activity scores are 100 and 100.
bruno 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. 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. License scores in this pair are 96 for bruno and 96 for dagster. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 stars) and dagster (16,433 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: bruno is open source, dagster is open source.
bruno is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 36 points (70 vs 34), and the tightest is self-hosting at 0 points (100 vs 100).
bruno finishes ahead at 96.5 against dagster at 89.1, a 7.4 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 | bruno | dagster |
|---|---|---|
| GitHub stars | 48,427 | 16,433 |
| Forks | 3,115 | 2,425 |
| Open issues | 2,002 | 2,630 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 97 |
| Issue health | 70 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 89.1 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
An orchestration platform for the development, production, and observation of data assets.
bruno has more GitHub stars: 48,427 versus 16,433 for dagster. The gap is 31,994 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both bruno and dagster as self-hostable. Confirm each project's deploy docs before you plan a migration.
bruno 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
bruno scores 96.5 and dagster scores 89.1. This page calls that a clear lead for bruno.