A
bruno
95.5
48,427 stars · MIT
Workflow Automation
fastlane leads by 2.0 · narrow
A
95.5
48,427 stars · MIT
B · leads
97.5
42,399 stars · MIT
bruno versus fastlane 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; fastlane is written mainly in Ruby. The composite score is 95.5 for bruno and 97.5 for fastlane.
bruno has 48,427 GitHub stars to fastlane's 42,399, a gap of 6,028 (1.14×). Forks are 3,115 for bruno and 6,057 for fastlane. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 92 versus 100.
Push history: bruno was last pushed on 17 November 2026 (0 days ago), and fastlane was last pushed on 16 November 2026 (1 day ago). Open issues stand at 2,002 for bruno (0.041 per star) and 660 for fastlane (0.016 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
Both bruno and fastlane are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 stars) and fastlane (42,399 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, fastlane is open source.
The lead is split. bruno is furthest ahead on adoption (100 to 99), while fastlane is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
fastlane finishes ahead at 97.5 against bruno at 95.5, a 2.0 point narrow 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 | fastlane |
|---|---|---|
| GitHub stars | 48,427 | 42,399 |
| Forks | 3,115 | 6,057 |
| Open issues | 2,002 | 660 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 92 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.5 | 97.5 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
🚀 The easiest way to automate building and releasing your iOS and Android apps
bruno has more GitHub stars: 48,427 versus 42,399 for fastlane. The gap is 6,028 stars.
bruno was pushed more recently: 17 November 2026 versus 16 November 2026 for fastlane. That is 1 days apart.
Yes. This catalog marks both bruno and fastlane 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. fastlane 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
fastlane scores 97.5 and bruno scores 95.5. This page calls that a narrow lead for fastlane.