Skip to content
DevUtils Online

Workflow Automation

bruno vs keep

bruno leads by 20.4 · decisive

A · leads

bruno

96.5

48,427 stars · MIT

B

keep

76.1

12,531 stars · license n/a

bruno versus keep 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; keep is written mainly in Python. The composite score is 96.5 for bruno and 76.1 for keep.

bruno has 48,427 GitHub stars to keep's 12,531, a gap of 35,896 (3.86×). Forks are 3,115 for bruno and 1,555 for keep. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 91.

Push history: bruno was last pushed on 17 November 2026 (0 days ago), and keep was last pushed on 16 November 2026 (1 day ago). Open issues stand at 2,002 for bruno (0.041 per star) and 708 for keep (0.056 per star). Issue-health scores are 70 and 52; 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. keep 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. License scores in this pair are 96 for bruno and 30 for keep. This is a procurement signal, not legal advice.

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

bruno is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is recent activity at 0 points (100 vs 100).

bruno finishes ahead at 96.5 against keep at 76.1, a 20.4 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.

bruno versus keep metrics
Signal bruno keep
GitHub stars 48,427 12,531
Forks 3,115 1,555
Open issues 2,002 708
Adoption 100 88
Activity 100 100
Community 100 91
Issue health 70 52
License 96 30
Self-hosting 100 35
Composite 96.5 76.1

Questions this page answers

Which has more GitHub stars, bruno or keep?

bruno has more GitHub stars: 48,427 versus 12,531 for keep. The gap is 35,896 stars.

Which was updated more recently, bruno or keep?

bruno was pushed more recently: 17 November 2026 versus 16 November 2026 for keep. That is 1 days apart.

Can I self-host both bruno and keep?

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

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

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. keep 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the bruno vs keep score?

bruno scores 96.5 and keep scores 76.1. This page calls that a decisive lead for bruno.

Related comparisons