A · level
appium
98.1
22,233 stars · Apache-2.0
Workflow Automation
Too close to call · 98.1 to 97.2
A · level
98.1
22,233 stars · Apache-2.0
B · level
97.2
30,151 stars · Apache-2.0
appium versus sim 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.1 for appium and 97.2 for sim.
sim has 30,151 GitHub stars to appium's 22,233, a gap of 7,918 (1.36×). Forks are 6,308 for appium and 3,915 for sim. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 100 versus 94.
Push history: appium was last pushed on 17 November 2026 (0 days ago), and sim was last pushed on 17 November 2026 (0 days ago). Open issues stand at 40 for appium (0.002 per star) and 330 for sim (0.011 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both appium and sim are listed as Apache-2.0. 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 appium (22,233 stars) and sim (30,151 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, sim is open source.
The lead is split. appium is furthest ahead on issue health (96 to 84), while sim is furthest ahead on adoption (100 to 97). Choose the dimension a rollout cannot compromise on.
Composite score: appium 98.1, sim 97.2. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | sim |
|---|---|---|
| GitHub stars | 22,233 | 30,151 |
| Forks | 6,308 | 3,915 |
| Open issues | 40 | 330 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 94 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 98.1 | 97.2 |
Cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol
Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.
sim has more GitHub stars: 30,151 versus 22,233 for appium. The gap is 7,918 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both appium and sim 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. sim 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.
Neither tool clears a one-point margin. appium scores 98.1 and sim scores 97.2.