A · leads
appium
98.3
22,233 stars · Apache-2.0
Workflow Automation
appium leads by 15.2 · decisive
A · leads
98.3
22,233 stars · Apache-2.0
B
83.1
28,420 stars · license n/a
appium versus budibase is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 98.3 for appium and 83.1 for budibase.
budibase has 28,420 GitHub stars to appium's 22,233, a gap of 6,187 (1.28×). Forks are 6,308 for appium and 2,237 for budibase. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 88.
Push history: appium was last pushed on 17 November 2026 (0 days ago), and budibase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 40 for appium (0.002 per star) and 318 for budibase (0.011 per star). Issue-health scores are 96 and 84; 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. budibase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for appium and 30 for budibase. This is a procurement signal, not legal advice.
Only appium is marked self-hostable here (22,233 stars, deploy score 100). budibase is not (28,420 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: appium is open source, budibase is unpriced in this catalog.
The lead is split. appium is furthest ahead on license flexibility (96 to 30), while budibase is furthest ahead on adoption (100 to 98). Choose the dimension a rollout cannot compromise on.
appium finishes ahead at 98.3 against budibase at 83.1, a 15.2 point decisive 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 | budibase |
|---|---|---|
| GitHub stars | 22,233 | 28,420 |
| Forks | 6,308 | 2,237 |
| Open issues | 40 | 318 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 96 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 98.3 | 83.1 |
Cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol
AI agents, automations and apps that run your operations. Model agnostic.
budibase has more GitHub stars: 28,420 versus 22,233 for appium. The gap is 6,187 stars.
Both were last pushed on 17 November 2026.
Only appium is marked self-hostable. budibase is not.
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. budibase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
appium scores 98.3 and budibase scores 83.1. This page calls that a decisive lead for appium.