Web Scraping Concurrency Limits Increased Across Plans
Parallel request capacity has been raised for every plan tier, with the largest proportional gain on Freelance and a new top Enterprise tier added for very large workloads. The change is already active and requires no account or code changes.
What changed
Every plan tier now allows more simultaneous requests. Freelance moves from 10 to 50, a fivefold increase and the largest proportional jump. Startup rises from 50 to 100, Business from 100 to 200, and Business + from 200 to 400, each doubling. Enterprise 14 goes from 200 to 500, Enterprise 24 from 200 to 600, and Enterprise 41 from 200 to 700. A new Enterprise 69 tier adds 800 concurrent requests for teams whose workloads exceed the previous top tier.
Before-and-after limits by plan
Use the table as a quick check before changing your own setup. If your plan is Freelance, you can now run up to 50 requests at once instead of 10. Mid-tier plans double their headroom. Enterprise plans gain between 300 and 500 additional concurrent slots, and Enterprise 69 sits above all of them at 800.
What this means for your jobs
More parallel capacity matters most when a job is waiting on the concurrency cap rather than on the target site or your own code. Batch collection, recurring crawls, and production pipelines that feed downstream processing can move more pages per run. Shorter queues during busy periods also reduce the time requests spend waiting to start. For growing teams, the practical effect is more headroom before concurrency alone forces an upgrade.
Why capacity increased
The increase follows added infrastructure capacity intended to support higher request volume and steadier performance under heavy load. That context matters when judging results: a higher cap helps only if your workers, network, and target sites can use the extra parallelism.
How to use the extra headroom
Try the new headroom on a larger batch, raise the parallel-request count in your worker configuration, or rerun an existing pipeline and compare completion time. Compare current plan limits on the pricing page, check implementation details in the documentation, and contact the team if enterprise-scale workloads need more.
| Plan | Previous concurrency | New concurrency | Increase |
|---|---|---|---|
| Freelance | 10 | 50 | 5x |
| Startup | 50 | 100 | 2x |
| Business | 100 | 200 | 2x |
| Business + | 200 | 400 | 2x |
| Enterprise 14 | 200 | 500 | 2.5x |
| Enterprise 24 | 200 | 600 | 3x |
| Enterprise 41 | 200 | 700 | 3.5x |
| Enterprise 69 | — | 800 | New plan |
Limits as reported in the captured plan table; confirm current limits and pricing with the publishing owner before publication.
Frequently asked questions
Do I need to do anything to get the new concurrency limits?
No. The higher limits were applied automatically to all accounts, with no settings change, migration, code change, or support request needed.
Are the new limits available on every plan?
Yes. Every plan, from Freelance through Enterprise, received a higher limit.
Does this change the price of my plan?
{{OWNER_PRICE_CHANGE_CONFIRMATION: confirm whether existing plan prices remain unchanged and whether the new Enterprise 69 plan is priced at {{OWNER_ENTERPRISE_69_PRICE}} per {{OWNER_BILLING_PERIOD}} with {{OWNER_ENTERPRISE_69_TERMS}} }}
Will this make my scraping jobs faster?
Often, yes, when concurrency was the bottleneck. Running more requests in parallel can shorten large batch jobs, but total speed also depends on your worker setup, target sites, and other limits in the pipeline.
| 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 |