A · leads
appium
96.7
22,233 stars · Apache-2.0
Workflow Automation
appium leads by 1.3 · narrow
A · leads
96.7
22,233 stars · Apache-2.0
B
95.4
48,427 stars · MIT
appium versus bruno is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. appium is written mainly in TypeScript; bruno is written mainly in JavaScript. The composite score is 96.7 for appium and 95.4 for bruno.
bruno has 48,427 GitHub stars to appium's 22,233, a gap of 26,194 (2.18×). Forks are 6,308 for appium and 3,115 for bruno. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 100 versus 92.
Push history: appium was last pushed on 17 November 2026 (0 days ago), and bruno was last pushed on 17 November 2026 (0 days ago). Open issues stand at 40 for appium (0.002 per star) and 2,002 for bruno (0.041 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
appium 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. 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. License scores in this pair are 96 for appium and 96 for bruno. This is a procurement signal, not legal advice.
In Workflow Automation, both appium (22,233 stars) and bruno (48,427 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: appium is open source, bruno is open source.
The lead is split. appium is furthest ahead on issue health (96 to 70), while bruno is furthest ahead on adoption (100 to 93). Choose the dimension a rollout cannot compromise on.
appium finishes ahead at 96.7 against bruno at 95.4, a 1.3 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 | appium | bruno |
|---|---|---|
| GitHub stars | 22,233 | 48,427 |
| Forks | 6,308 | 3,115 |
| Open issues | 40 | 2,002 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 92 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.7 | 95.4 |
Cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
bruno has more GitHub stars: 48,427 versus 22,233 for appium. The gap is 26,194 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both appium and bruno as self-hostable. Confirm each project's deploy docs before you plan a migration.
appium 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
appium scores 96.7 and bruno scores 95.4. This page calls that a narrow lead for appium.