A · leads
bruno
96.5
48,427 stars · MIT
Workflow Automation
bruno leads by 12.4 · clear
A · leads
96.5
48,427 stars · MIT
B
84.1
21,625 stars · GPL-3.0
bruno versus Obtainium 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; Obtainium is written mainly in Dart. The composite score is 96.5 for bruno and 84.1 for Obtainium.
bruno has 48,427 GitHub stars to Obtainium's 21,625, a gap of 26,802 (2.24×). Forks are 3,115 for bruno and 704 for Obtainium. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 82.
Push history: bruno was last pushed on 17 November 2026 (0 days ago), and Obtainium was last pushed on 01 November 2026 (16 days ago). Open issues stand at 2,002 for bruno (0.041 per star) and 403 for Obtainium (0.019 per star). Issue-health scores are 70 and 84; activity scores are 100 and 78.
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. Obtainium is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for bruno and 64 for Obtainium. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 stars) and Obtainium (21,625 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, Obtainium is open source.
The lead is split. bruno is furthest ahead on license flexibility (96 to 64), while Obtainium is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
bruno finishes ahead at 96.5 against Obtainium at 84.1, a 12.4 point clear 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 | Obtainium |
|---|---|---|
| GitHub stars | 48,427 | 21,625 |
| Forks | 3,115 | 704 |
| Open issues | 2,002 | 403 |
| Adoption | 100 | 92 |
| Activity | 100 | 78 |
| Community | 100 | 82 |
| Issue health | 70 | 84 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 84.1 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
Get Android app updates straight from the source.
bruno has more GitHub stars: 48,427 versus 21,625 for Obtainium. The gap is 26,802 stars.
bruno was pushed more recently: 17 November 2026 versus 01 November 2026 for Obtainium. That is 16 days apart.
Yes. This catalog marks both bruno and Obtainium 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. Obtainium is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
bruno scores 96.5 and Obtainium scores 84.1. This page calls that a clear lead for bruno.