Skip to content
DevUtils Online

Workflow Automation

bruno vs nanobot

nanobot leads by 3.1 · narrow

A

bruno

94.8

48,427 stars · MIT

B · leads

nanobot

97.9

50,147 stars · MIT

bruno versus nanobot 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; nanobot is written mainly in Python. The composite score is 94.8 for bruno and 97.9 for nanobot.

nanobot has 50,147 GitHub stars to bruno's 48,427, a gap of 1,720 (1.04×). Forks are 3,115 for bruno and 8,755 for nanobot. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 89 versus 100.

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

Both bruno and nanobot 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 nanobot (50,147 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, nanobot is open source.

nanobot 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 14 points (70 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).

nanobot finishes ahead at 97.9 against bruno at 94.8, 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 nanobot metrics
Signal bruno nanobot
GitHub stars 48,427 50,147
Forks 3,115 8,755
Open issues 2,002 872
Adoption 100 100
Activity 100 100
Community 89 100
Issue health 70 84
License 96 96
Self-hosting 100 100
Composite 94.8 97.9

Questions this page answers

Which has more GitHub stars, bruno or nanobot?

nanobot has more GitHub stars: 50,147 versus 48,427 for bruno. The gap is 1,720 stars.

Which was updated more recently, bruno or nanobot?

Both were last pushed on 17 November 2026.

Can I self-host both bruno and nanobot?

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

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. nanobot 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 nanobot score?

nanobot scores 97.9 and bruno scores 94.8. This page calls that a narrow lead for nanobot.

Related comparisons