A · leads
crawlee
97.5
26,480 stars · Apache-2.0
Workflow Automation
crawlee leads by 5.3 · narrow
A · leads
97.5
26,480 stars · Apache-2.0
B
92.2
23,434 stars · AGPL-3.0
crawlee versus skyvern is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. crawlee is written mainly in TypeScript; skyvern is written mainly in Python. The composite score is 97.5 for crawlee and 92.2 for skyvern.
crawlee has 26,480 GitHub stars to skyvern's 23,434, a gap of 3,046 (1.13×). Forks are 1,772 for crawlee and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 97 versus 100.
Push history: crawlee was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 145 for crawlee (0.005 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for crawlee and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both crawlee (26,480 stars) and skyvern (23,434 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: crawlee is open source, skyvern is open source.
The lead is split. crawlee is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on fork community (100 to 97). Choose the dimension a rollout cannot compromise on.
crawlee finishes ahead at 97.5 against skyvern at 92.2, a 5.3 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 | crawlee | skyvern |
|---|---|---|
| GitHub stars | 26,480 | 23,434 |
| Forks | 1,772 | 2,246 |
| Open issues | 145 | 301 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 97 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.5 | 92.2 |
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.
Automate browser based workflows with AI
crawlee has more GitHub stars: 26,480 versus 23,434 for skyvern. The gap is 3,046 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both crawlee and skyvern as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
crawlee scores 97.5 and skyvern scores 92.2. This page calls that a narrow lead for crawlee.