A · leads
appium
98.5
22,233 stars · Apache-2.0
Workflow Automation
appium leads by 2.6 · narrow
A · leads
98.5
22,233 stars · Apache-2.0
B
95.9
26,480 stars · Apache-2.0
appium versus crawlee 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.5 for appium and 95.9 for crawlee.
crawlee has 26,480 GitHub stars to appium's 22,233, a gap of 4,247 (1.19×). Forks are 6,308 for appium and 1,772 for crawlee. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 86.
Push history: appium was last pushed on 17 November 2026 (0 days ago), and crawlee was last pushed on 17 November 2026 (0 days ago). Open issues stand at 40 for appium (0.002 per star) and 145 for crawlee (0.005 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both appium and crawlee 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 crawlee (26,480 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, crawlee is open source.
The lead is split. appium is furthest ahead on fork community (100 to 86), while crawlee is furthest ahead on adoption (100 to 98). Choose the dimension a rollout cannot compromise on.
appium finishes ahead at 98.5 against crawlee at 95.9, 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 | appium | crawlee |
|---|---|---|
| GitHub stars | 22,233 | 26,480 |
| Forks | 6,308 | 1,772 |
| Open issues | 40 | 145 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 86 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 98.5 | 95.9 |
Cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol
Crawlee—A web scraping and browser automation library for Node.js to build reliable crawlers. In JavaScript and TypeScript. Extract data for AI, LLMs, RAG, or GPTs. Download HTML, PDF, JPG, PNG, and other files from websites. Works with Puppeteer, Playwright, Cheerio, JSDOM, and raw HTTP. Both headful and headless mode. With proxy rotation.
crawlee has more GitHub stars: 26,480 versus 22,233 for appium. The gap is 4,247 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both appium and crawlee 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. crawlee 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.5 and crawlee scores 95.9. This page calls that a narrow lead for appium.