A · leads
crawlee
96.3
26,480 stars · Apache-2.0
Workflow Automation
crawlee leads by 1.5 · narrow
A · leads
96.3
26,480 stars · Apache-2.0
B
94.8
27,230 stars · MIT
crawlee versus vagrant 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; vagrant is written mainly in Ruby. The composite score is 96.3 for crawlee and 94.8 for vagrant.
vagrant has 27,230 GitHub stars to crawlee's 26,480, a gap of 750 (1.03×). Forks are 1,772 for crawlee and 4,491 for vagrant. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 89 versus 100.
Push history: crawlee was last pushed on 17 November 2026 (0 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 145 for crawlee (0.005 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 84 and 70; activity scores are 100 and 92.
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. vagrant 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. License scores in this pair are 96 for crawlee and 96 for vagrant. This is a procurement signal, not legal advice.
In Workflow Automation, both crawlee (26,480 stars) and vagrant (27,230 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, vagrant is open source.
The lead is split. crawlee is furthest ahead on issue health (84 to 70), while vagrant is furthest ahead on fork community (100 to 89). Choose the dimension a rollout cannot compromise on.
crawlee finishes ahead at 96.3 against vagrant at 94.8, a 1.5 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 | vagrant |
|---|---|---|
| GitHub stars | 26,480 | 27,230 |
| Forks | 1,772 | 4,491 |
| Open issues | 145 | 760 |
| Adoption | 100 | 100 |
| Activity | 100 | 92 |
| Community | 89 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.3 | 94.8 |
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.
Vagrant is a tool for building and distributing development environments.
vagrant has more GitHub stars: 27,230 versus 26,480 for crawlee. The gap is 750 stars.
crawlee was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.
Yes. This catalog marks both crawlee and vagrant 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. vagrant 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
crawlee scores 96.3 and vagrant scores 94.8. This page calls that a narrow lead for crawlee.