A
Activepieces
96.0
25,581 stars · MIT
Workflow Automation
appium leads by 2.6 · narrow
A
96.0
25,581 stars · MIT
B · leads
98.6
22,233 stars · Apache-2.0
Activepieces versus appium 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 96.0 for Activepieces and 98.6 for appium.
Activepieces has 25,581 GitHub stars to appium's 22,233, a gap of 3,348 (1.15×). Forks are 4,476 for Activepieces and 6,308 for appium. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 96 versus 100.
Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and appium was last pushed on 17 November 2026 (0 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 40 for appium (0.002 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
Activepieces 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. 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. License scores in this pair are 96 for Activepieces and 96 for appium. This is a procurement signal, not legal advice.
In Workflow Automation, both Activepieces (25,581 stars) and appium (22,233 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: Activepieces is open source, appium is open source.
The lead is split. Activepieces is furthest ahead on adoption (100 to 99), while appium is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
appium finishes ahead at 98.6 against Activepieces at 96.0, a 2.6 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 | Activepieces | appium |
|---|---|---|
| GitHub stars | 25,581 | 22,233 |
| Forks | 4,476 | 6,308 |
| Open issues | 961 | 40 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 96 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.0 | 98.6 |
Activepieces is a TypeScript workflow tool positioned as a self-hosted automation builder. It focuses on connecting business apps with a visual builder and an MIT-licensed core.
Cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol
Activepieces has more GitHub stars: 25,581 versus 22,233 for appium. The gap is 3,348 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Activepieces and appium as self-hostable. Confirm each project's deploy docs before you plan a migration.
Activepieces 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
appium scores 98.6 and Activepieces scores 96.0. This page calls that a narrow lead for appium.