Skip to content
DevUtils Online

Workflow Automation

bruno vs trigger.dev

bruno leads by 3.1 · narrow

A · leads

bruno

96.5

48,427 stars · MIT

bruno 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. bruno is written mainly in JavaScript; trigger.dev is written mainly in TypeScript. The composite score is 96.5 for bruno and 93.4 for trigger.dev.

bruno has 48,427 GitHub stars to trigger.dev's 16,776, a gap of 31,651 (2.89×). Forks are 3,115 for bruno and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 91.

Push history: bruno 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,002 for bruno (0.041 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 70 and 84; 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. 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. License scores in this pair are 96 for bruno and 96 for trigger.dev. This is a procurement signal, not legal advice.

In Workflow Automation, both bruno (48,427 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: bruno is open source, trigger.dev is open source.

The lead is split. bruno is furthest ahead on adoption (100 to 90), while trigger.dev is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.

bruno finishes ahead at 96.5 against trigger.dev at 93.4, a 3.1 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

bruno versus trigger.dev metrics
Signal bruno trigger.dev
GitHub stars 48,427 16,776
Forks 3,115 1,534
Open issues 2,002 268
Adoption 100 90
Activity 100 100
Community 100 91
Issue health 70 84
License 96 96
Self-hosting 100 100
Composite 96.5 93.4

Questions this page answers

Which has more GitHub stars, bruno or trigger.dev?

bruno has more GitHub stars: 48,427 versus 16,776 for trigger.dev. The gap is 31,651 stars.

Which was updated more recently, bruno or trigger.dev?

Both were last pushed on 17 November 2026.

Can I self-host both bruno and trigger.dev?

Yes. This catalog marks both bruno and trigger.dev as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, bruno or trigger.dev?

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. 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.

Who wins the bruno vs trigger.dev score?

bruno scores 96.5 and trigger.dev scores 93.4. This page calls that a narrow lead for bruno.

Related comparisons