Skip to content
DevUtils Online

Workflow Automation

bruno vs leon

bruno leads by 3.0 · narrow

A · leads

bruno

96.5

48,427 stars · MIT

B

leon

93.5

17,690 stars · MIT

bruno versus leon 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; leon is written mainly in TypeScript. The composite score is 96.5 for bruno and 93.5 for leon.

bruno has 48,427 GitHub stars to leon's 17,690, a gap of 30,737 (2.74×). Forks are 3,115 for bruno and 1,484 for leon. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 91.

Push history: bruno was last pushed on 17 November 2026 (0 days ago), and leon was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,002 for bruno (0.041 per star) and 118 for leon (0.007 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.

Both bruno and leon are listed as MIT. 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 bruno (48,427 stars) and leon (17,690 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, leon is open source.

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

bruno finishes ahead at 96.5 against leon at 93.5, a 3.0 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 leon metrics
Signal bruno leon
GitHub stars 48,427 17,690
Forks 3,115 1,484
Open issues 2,002 118
Adoption 100 91
Activity 100 100
Community 100 91
Issue health 70 84
License 96 96
Self-hosting 100 100
Composite 96.5 93.5

Questions this page answers

Which has more GitHub stars, bruno or leon?

bruno has more GitHub stars: 48,427 versus 17,690 for leon. The gap is 30,737 stars.

Which was updated more recently, bruno or leon?

Both were last pushed on 17 November 2026.

Can I self-host both bruno and leon?

Yes. This catalog marks both bruno and leon 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 leon?

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

Who wins the bruno vs leon score?

bruno scores 96.5 and leon scores 93.5. This page calls that a narrow lead for bruno.

Related comparisons