A · leads
bruno
96.5
48,427 stars · MIT
Workflow Automation
bruno leads by 15.4 · decisive
A · leads
96.5
48,427 stars · MIT
B
81.1
10,094 stars · license n/a
bruno versus superplane 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; superplane is written mainly in Go. The composite score is 96.5 for bruno and 81.1 for superplane.
bruno has 48,427 GitHub stars to superplane's 10,094, a gap of 38,333 (4.80×). Forks are 3,115 for bruno and 710 for superplane. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 82.
Push history: bruno was last pushed on 17 November 2026 (0 days ago), and superplane was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,002 for bruno (0.041 per star) and 266 for superplane (0.026 per star). Issue-health scores are 70 and 70; 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. superplane 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 superplane. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 stars) and superplane (10,094 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, superplane is unpriced in this catalog.
bruno is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is self-hosting at 0 points (100 vs 100).
bruno finishes ahead at 96.5 against superplane at 81.1, a 15.4 point decisive margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | bruno | superplane |
|---|---|---|
| GitHub stars | 48,427 | 10,094 |
| Forks | 3,115 | 710 |
| Open issues | 2,002 | 266 |
| Adoption | 100 | 86 |
| Activity | 100 | 100 |
| Community | 100 | 82 |
| Issue health | 70 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 81.1 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
Open source factory for one-shot engineering
bruno has more GitHub stars: 48,427 versus 10,094 for superplane. The gap is 38,333 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both bruno and superplane as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. superplane 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.
bruno scores 96.5 and superplane scores 81.1. This page calls that a decisive lead for bruno.