head to head · open source
scrapy vs wreq
scrapy has 64,394 GitHub stars, 11,964 forks, 394 open issues and last shipped yesterday. wreq has 1,025 stars, 124 forks, 23 open issues and last shipped yesterday. scrapy leads on adoption by 6,182% (64,394 vs 1,025 stars). scrapy is written in Python under BSD-3-Clause; wreq is written in Rust under Apache-2.0. scrapy has attracted 19% as many forks as stars, wreq 12%. scrapy was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (crawler), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 8884 open source comparisons
Side by side
| scrapy | wreq | |
|---|---|---|
| GitHub stars | ★ 64K | ★ 1.0K |
| License | BSD-3-Clause | Apache-2.0 |
| Written in | Python | Rust |
| Last push | 2026-09-17 | 2026-09-17 |
| Forks | ⑂ 12K | ⑂ 124 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick scrapy if
- You weight community size — 64K stars and counting
- You want the BSD-3-Clause license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick wreq if
- You want the wreq feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Rust
- You evaluated both and wreq fits your workflow better
About scrapy
Scrapy is a web scraping framework written in Python, distributed under the BSD 3 Clause license, and described in its own README as a tool to extract structured data from websites. It is cross platform and requires Python 3.10 or newer. The project is maintained by Zyte, formerly known as Scrapinghub, together with a broader group of contributors, and it lives in the Python ecosystem as an installable library rather than a hosted service. Its repository is roughly seventeen years old, which places it among the longer running projects in the web scraping space.
read the full scrapy overview →
About wreq
wreq [![Discord chat][discord badge]][discord url] [discord badge]: [discord url]: 🚀 Help me work seamlessly with open source sharing by sponsoring me on GitHub An ergonomic and modular Rust HTTP Client for high fidelity protocol matching, featuring customizable TLS, JA3/JA4, and HTTP/2 signature capabilities. Features Plain bodies, JSON, urlencoded, multipart HTTP Trailer Cookie Store Redirect Policy Original Header Rotating Proxies Tower Middleware WebSocket Upgrade HTTPS via BoringSSL HTTP/2 over TLS Parity Certificate Store (CAs & mTLS) Multiple Runtime (Tokio, Compio) Example The following example uses the …
More in Data & Analytics
Related comparisons
More Data Extraction & Web Scraping projects
Compare either of these against the rest of the Data Extraction & Web Scraping field.
Frequently asked questions
Is scrapy or wreq more popular?
scrapy has 64,394 GitHub stars and wreq has 1,025. scrapy has the larger community by that measure.
Are scrapy and wreq free?
Both are open source. scrapy is licensed under BSD-3-Clause and wreq under Apache-2.0. Neither carries a licence fee.
What is the difference between scrapy and wreq?
scrapy is written in Python and wreq in Rust. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, scrapy or wreq?
Choose scrapy if you want the larger community (64,394 stars) or its BSD-3-Clause licence terms. Choose wreq if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.