A
appium
90.0
22,233 stars · Apache-2.0
Workflow Automation
n8n leads by 1.0 · narrow
A
90.0
22,233 stars · Apache-2.0
B · leads
91.0
210,804 stars · Sustainable Use License
appium versus n8n 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 90.0 for appium and 91.0 for n8n.
n8n has 210,804 GitHub stars to appium's 22,233, a gap of 188,571 (9.48×). Forks are 6,308 for appium and 61,571 for n8n. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 79 versus 100.
Push history: appium was last pushed on 17 November 2026 (0 days ago), and n8n was last pushed on 17 November 2026 (0 days ago). Open issues stand at 40 for appium (0.002 per star) and 1,266 for n8n (0.006 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. n8n is listed as Sustainable Use License, which this catalog treats as source-available terms, not a standard OSI open-source license. The grant often limits competing hosted services or some commercial uses. License scores in this pair are 96 for appium and 38 for n8n. This is a procurement signal, not legal advice.
In Workflow Automation, both appium (22,233 stars) and n8n (210,804 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, n8n is freemium.
The lead is split. appium is furthest ahead on license flexibility (96 to 38), while n8n is furthest ahead on fork community (100 to 79). Choose the dimension a rollout cannot compromise on.
n8n finishes ahead at 91.0 against appium at 90.0, a 1.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 | appium | n8n |
|---|---|---|
| GitHub stars | 22,233 | 210,804 |
| Forks | 6,308 | 61,571 |
| Open issues | 40 | 1,266 |
| Adoption | 82 | 100 |
| Activity | 100 | 100 |
| Community | 79 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 38 |
| Self-hosting | 100 | 100 |
| Composite | 90.0 | 91.0 |
Cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol
n8n is a workflow automation product with a node canvas, self-hosting, and a paid cloud. Its code is source-available under a sustainable-use license, not an OSI open-source license.
n8n has more GitHub stars: 210,804 versus 22,233 for appium. The gap is 188,571 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both appium and n8n 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. n8n is listed as Sustainable Use License, which this catalog treats as source-available terms, not a standard OSI open-source license. The grant often limits competing hosted services or some commercial uses. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
n8n scores 91.0 and appium scores 90.0. This page calls that a narrow lead for n8n.