ScrapingBee now supports up to 5× more concurrent requests across all plans.
This upgrade is live and has been applied automatically to every account. No settings to change, no migration, no extra steps. You can now run more requests in parallel, finish large scraping jobs faster, and spend less time waiting in queues.
Behind this change is a major infrastructure upgrade built to give every ScrapingBee user more throughput and more room to scale.
What changed
Every ScrapingBee plan now gets higher concurrency limits. We are also adding a new Enterprise 69 plan with 800 concurrent requests for teams that need even more throughput.
| Plan | Previous concurrency | New concurrency | Increase |
|---|---|---|---|
| Freelance | 10 | 50 | 5× |
| Startup | 50 | 100 | 2× |
| Business | 100 | 200 | 2× |
| Business + | 200 | 400 | 2× |
| Enterprise 14 | 200 | 500 | 2.5× |
| Enterprise 24 | 200 | 600 | 3× |
| Enterprise 41 | 200 | 700 | 3.5× |
| Enterprise 69 | — | 800 | New plan |
These new limits are already active. You do not need to change your code, update your account, or contact support to get access to them.
What this means for you
Higher concurrency helps large scraping jobs finish faster. Instead of waiting for requests to run in smaller groups, you can now process more pages in parallel. This is especially useful for batch jobs, recurring crawls, and any workflow where completion time matters.
It also helps reduce queue wait times during busy periods. If you are collecting data from many URLs, running scheduled jobs, or feeding scraped data into a production pipeline, the higher limits give your requests more room to move without extra throttling on your side.
For growing teams, this means more headroom before you need to upgrade just for concurrency. You can handle larger datasets, time-sensitive scraping tasks, and heavier workloads on your current plan.
Built for higher-throughput scraping
This increase comes from a broader infrastructure upgrade across ScrapingBee. We have added more capacity to support higher request volume, shorter queues, and more stable performance for heavy workloads. It is part of our ongoing work to make ScrapingBee faster and more reliable for teams running scraping jobs at scale.
Live now for all users
The new concurrency limits are live now across all plans. Try them with a larger batch job, raise the number of parallel requests in your worker setup, or rerun an existing pipeline to see how much faster it completes with the added headroom.
To compare current plan limits, visit our pricing page. For implementation details, see the ScrapingBee documentation. If you need higher limits for enterprise-scale workloads, contact our team.
FAQ
Do I need to do anything to get the new concurrency limits?
No. The new limits have already been applied automatically to all ScrapingBee accounts. You do not need to change any settings or request access.
Are the new limits available on every plan?
Yes. Every plan now has higher concurrency limits, from Freelance to Enterprise.
Does this change the price of my plan?
No. This upgrade gives you more concurrency on your current plan at no extra cost.
Will this make my scraping jobs faster?
In many cases, yes. If your jobs were limited by concurrency, you can now run more requests in parallel and complete large batches faster.
Ilya is an IT tutor and author, web developer, and ex-Microsoft/Cisco specialist. His primary programming languages are Ruby, JavaScript, Python, and Elixir. He enjoys coding, teaching people and learning new things. In his free time he writes educational posts, participates in OpenSource projects, tweets, goes in for sports and plays music.
