A · level
bruno
96.1
48,427 stars · MIT
Workflow Automation
Too close to call · 96.1 to 96.4
A · level
96.1
48,427 stars · MIT
B · level
96.4
30,151 stars · Apache-2.0
bruno versus sim 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; sim is written mainly in TypeScript. The composite score is 96.1 for bruno and 96.4 for sim.
bruno has 48,427 GitHub stars to sim's 30,151, a gap of 18,276 (1.61×). Forks are 3,115 for bruno and 3,915 for sim. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 97 versus 100.
Push history: bruno was last pushed on 17 November 2026 (0 days ago), and sim was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,002 for bruno (0.041 per star) and 330 for sim (0.011 per star). Issue-health scores are 70 and 84; 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. sim is listed as Apache-2.0, 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 96 for bruno and 96 for sim. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 stars) and sim (30,151 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, sim is open source.
The lead is split. bruno is furthest ahead on adoption (100 to 96), while sim is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
Composite score: bruno 96.1, sim 96.4. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | sim |
|---|---|---|
| GitHub stars | 48,427 | 30,151 |
| Forks | 3,115 | 3,915 |
| Open issues | 2,002 | 330 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 97 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.1 | 96.4 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.
bruno has more GitHub stars: 48,427 versus 30,151 for sim. The gap is 18,276 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both bruno and sim 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. sim is listed as Apache-2.0, 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.
Neither tool clears a one-point margin. bruno scores 96.1 and sim scores 96.4.