[chruffins]

Don't merge until per-region limits are live in the API. These pages describe the new behavior, so they'd be wrong before then.

Summary

Concurrency and browser-create rate limits become per region: each region has its own limits, and usage in one region doesn't count against another. These pages said limits apply across all regions combined.

• Concurrency and limits: the concurrency table has a row per region (us-east unchanged; eu-west and ap-southeast at 150 for Start-Up and 150 or custom for Enterprise). It explains that limits apply per region and that a raised limit applies only to its region. It documents the 429 region_limit_exceeded response, and says the browser create rate is per region while other rate limits stay org-wide.
• Regional browsers: new "Limits per region" section with the same table. It covers default create rates, asking for more capacity in a specific region, the 429 region_limit_exceeded and 403 region_limit_required responses, and project caps counting every region combined. It removes the "concurrency and rate limits apply across all regions combined" bullet from "What stays global".
• Projects: the organization limit is now described as regional limits. A per-project cap counts the project's browsers in every region, regional limits still apply on top, and the org-wide default cap can't exceed the us-east limit. GET /org/limits reports the us-east limit.
• Browser pools: pool capacity counts against the limit of the pool's region.

Testing

mintlify broken-links reports no broken links. Not checked in the preview build.

---

Note

Low Risk
Documentation-only updates; accuracy depends on merging after per-region limits ship in the API, as noted in the PR description.

Overview
Docs now describe per-region limits instead of a single org-wide concurrency cap across all regions.

Concurrency and limits splits the plan table by region (us-east, eu-west, ap-southeast), clarifies that pool and standby usage counts in the pool/browser’s region, and documents 429 with region_limit_exceeded when a region is full. Browser create rate is per region; other API rate limits stay org-wide.

Regional browsers adds a Limits per region section (tables, per-region raises, region_limit_required on 403) and drops the old claim that concurrency/rate limits are global across regions.

Projects reframes the org limit as regional limits, notes that per-project caps sum browsers in every region while regional ceilings still apply, and that GET /org/limits reflects the us-east concurrency limit.

Browser pools states reserved capacity counts against the pool’s region limit.

^{Reviewed by Cursor Bugbot for commit ffe6055. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Oct 19, 2026, 1:47 PM

💡 Tip: Enable Automations to automatically generate PRs for you.