Profiles
Business
Scale the same browser workflow to larger operations.
The Business plan raises operational limits for Profiles, installations, saved proxies, User Scripts and Automation Studio. It does not require your team to learn a different browser product.
Business plan
Business plan at a glance
The current 3-year Business plan is designed for higher quantities and Automation Studio capacity.
Browser Installations
saved proxies
Automation Studio runs / month
Use cases
Where the Business plan fits
Use Business when quantity and operational scale are the constraint—not because you need a different browser engine.
Agencies
Keep client/account work separated by Profile and standardize repeatable workflows.
Automation teams
Run tested Workflows against larger target sets with explicit concurrency and verification.
Operations teams
Use persistent sessions, proxies, downloads and browser state without rebuilding the environment every run.
Developers
Combine Browser API, User Scripts, Puppeteer and MCP AI with the same browser Profiles.
Distributed installations
The Business plan raises Browser Installation limits for teams that need multiple authorized devices.
Custom requirements
Custom browser development remains a separate service and is not automatically included in the Business subscription.
Learn more →Operations
Deployment checklist
Treat a large deployment as an operating system for browser workflows, not just a high Profile count.
Capacity plan
Size CPU, memory and storage for peak active Profile concurrency, not stored Profile count.
Learn more →Workflow governance
Define who can change Workflows, proxies, scripts and MCP operation policies.
Backup strategy
Back up persistent Profile data according to the business recovery policy.
Support path
Use Support Center diagnostics, known issues and ticketing for production incidents.
Learn more →