A · leads
bruno
96.5
48,427 stars · MIT
Workflow Automation
bruno leads by 11.4 · clear
A · leads
96.5
48,427 stars · MIT
B
85.1
19,463 stars · Apache-2.0
bruno versus taipy 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; taipy is written mainly in Python. The composite score is 96.5 for bruno and 85.1 for taipy.
bruno has 48,427 GitHub stars to taipy's 19,463, a gap of 28,964 (2.49×). Forks are 3,115 for bruno and 1,996 for taipy. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 94.
Push history: bruno was last pushed on 17 November 2026 (0 days ago), and taipy was last pushed on 10 August 2026 (99 days ago). Open issues stand at 2,002 for bruno (0.041 per star) and 233 for taipy (0.012 per star). Issue-health scores are 70 and 84; activity scores are 100 and 58.
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. taipy 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 taipy. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 stars) and taipy (19,463 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, taipy is open source.
The lead is split. bruno is furthest ahead on recent activity (100 to 58), while taipy is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
bruno finishes ahead at 96.5 against taipy at 85.1, a 11.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 | taipy |
|---|---|---|
| GitHub stars | 48,427 | 19,463 |
| Forks | 3,115 | 1,996 |
| Open issues | 2,002 | 233 |
| Adoption | 100 | 92 |
| Activity | 100 | 58 |
| Community | 100 | 94 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 85.1 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
Turns Data and AI algorithms into production-ready web applications in no time.
bruno has more GitHub stars: 48,427 versus 19,463 for taipy. The gap is 28,964 stars.
bruno was pushed more recently: 17 November 2026 versus 10 August 2026 for taipy. That is 99 days apart.
Yes. This catalog marks both bruno and taipy 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. taipy 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.
bruno scores 96.5 and taipy scores 85.1. This page calls that a clear lead for bruno.