Summary of an article published on The Web Scraping Club on 2025-03-25 (free to read). Read the full article

Anti-detect browsers were built for multi-account management, and their pricing pages still show it. For scraping, the numbers that decide the bill are API requests per minute, requests per hour and how many automated browsers you can run in parallel. A plan that looks cheap can hit an hourly cap long before your scraper reaches its real load, and every profile creation or browser launch counts as a request.

We defined one scenario: 50 automated browsers running at once, about 30 seconds per session, with profile creation and launch counted as API calls. Then we checked public pricing as of March 5 for Kameleo, OctoBrowser, Multilogin, Incogniton, Undetectable.io and NST Browser, normalized to monthly subscriptions. For each one we looked at RPM and RPH limits, concurrency and what it takes to scale beyond the plan. Some vendors do not publish those limits at all.

What’s inside

  • How an hourly request cap can quietly override a generous per-minute limit, and why you need to check both.
  • How many API calls a single browser session typically consumes, and how that turns 50 parallel browsers into a request rate.
  • Which vendors sell extra capacity as more RPM, more browser slots or more usage hours, and how that changes the final cost.
  • Why Incogniton and Undetectable.io are hard to compare: they price on profiles and seats, not on API limits, so you have to ask support.

In the full article: Plan names and monthly prices per vendor, the RPM and RPH caps behind them, how each tool fits the 50-browser scenario, the closing recommendations and links to each pricing page.

Read the full article on The Web Scraping Club