Skip to content
DevUtils Online

Workflow Automation

automa vs bruno

bruno leads by 28.8 · decisive

A

automa

67.7

21,723 stars · license n/a

B · leads

bruno

96.5

48,427 stars · MIT

automa versus bruno is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. automa is written mainly in Vue; bruno is written mainly in JavaScript. The composite score is 67.7 for automa and 96.5 for bruno.

bruno has 48,427 GitHub stars to automa's 21,723, a gap of 26,704 (2.23×). Forks are 2,341 for automa and 3,115 for bruno. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 96 versus 100.

Push history: automa was last pushed on 02 March 2026 (260 days ago), and bruno was last pushed on 17 November 2026 (0 days ago). Open issues stand at 379 for automa (0.017 per star) and 2,002 for bruno (0.041 per star). Issue-health scores are 84 and 70; activity scores are 36 and 100.

automa is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. License scores in this pair are 30 for automa and 96 for bruno. This is a procurement signal, not legal advice.

Only bruno is marked self-hostable here (48,427 stars, deploy score 100). automa is not (21,723 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: automa is unpriced in this catalog, bruno is open source.

The lead is split. automa is furthest ahead on issue health (84 to 70), while bruno is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

bruno finishes ahead at 96.5 against automa at 67.7, a 28.8 point decisive 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.

automa versus bruno metrics
Signal automa bruno
GitHub stars 21,723 48,427
Forks 2,341 3,115
Open issues 379 2,002
Adoption 93 100
Activity 36 100
Community 96 100
Issue health 84 70
License 30 96
Self-hosting 35 100
Composite 67.7 96.5

Questions this page answers

Which has more GitHub stars, automa or bruno?

bruno has more GitHub stars: 48,427 versus 21,723 for automa. The gap is 26,704 stars.

Which was updated more recently, automa or bruno?

bruno was pushed more recently: 17 November 2026 versus 02 March 2026 for automa. That is 260 days apart.

Can I self-host both automa and bruno?

Only bruno is marked self-hostable. automa is not.

Which license is easier to embed in a commercial product, automa or bruno?

automa is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the automa vs bruno score?

bruno scores 96.5 and automa scores 67.7. This page calls that a decisive lead for bruno.

Related comparisons