A · leads
bruno
96.1
48,427 stars · MIT
Workflow Automation
bruno leads by 11.3 · clear
A · leads
96.1
48,427 stars · MIT
B
84.8
18,414 stars · GPL-3.0
bruno versus InstaPy 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; InstaPy is written mainly in Python. The composite score is 96.1 for bruno and 84.8 for InstaPy.
bruno has 48,427 GitHub stars to InstaPy's 18,414, a gap of 30,013 (2.63×). Forks are 3,115 for bruno and 3,896 for InstaPy. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 97 versus 100.
Push history: bruno was last pushed on 17 November 2026 (0 days ago), and InstaPy was last pushed on 26 October 2026 (21 days ago). Open issues stand at 2,002 for bruno (0.041 per star) and 586 for InstaPy (0.032 per star). Issue-health scores are 70 and 70; 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. InstaPy 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 InstaPy. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 stars) and InstaPy (18,414 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, InstaPy is open source.
The lead is split. bruno is furthest ahead on license flexibility (96 to 64), while InstaPy is furthest ahead on fork community (100 to 97). Choose the dimension a rollout cannot compromise on.
bruno finishes ahead at 96.1 against InstaPy at 84.8, a 11.3 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 | InstaPy |
|---|---|---|
| GitHub stars | 48,427 | 18,414 |
| Forks | 3,115 | 3,896 |
| Open issues | 2,002 | 586 |
| Adoption | 100 | 91 |
| Activity | 100 | 78 |
| Community | 97 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 96.1 | 84.8 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
📷 Instagram Bot - Tool for automated Instagram interactions
bruno has more GitHub stars: 48,427 versus 18,414 for InstaPy. The gap is 30,013 stars.
bruno was pushed more recently: 17 November 2026 versus 26 October 2026 for InstaPy. That is 21 days apart.
Yes. This catalog marks both bruno and InstaPy 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. InstaPy 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.1 and InstaPy scores 84.8. This page calls that a clear lead for bruno.