What you control
Control allowed egress region, routing mode, work domains, traffic limits, domain/category policy, active sessions, and session history.
QA testing
Test public web flows through approved egress
QA needs to check how public web flows behave from an approved region, with clear limits and a record of who ran the session.
What stays outside
This is for accountable testing of public web experiences. It is not for unblocking, scraping, anonymity, bypassing restrictions, or testing private/internal networks through the browser-proxy path.
Proof points
Backed by implementation
- Run tests through an approved egress region exposed by the plan.
- Session history records who connected and when.
- Traffic/session limits keep runs bounded.
- Browser-path HTTPS content is not decrypted.
- Private/internal network ranges are blocked on the browser-proxy path.
FAQ
Can we use this for scraping or bypassing restrictions?
No. BusinessProxy is for accountable work browsing and public web testing. It is not an anonymity, scraping, unblocking, or evasion tool.
Can QA choose any country?
Only approved egress regions exposed by the current plan are shown. We do not claim global region coverage unless the region catalog and plan support it.
Does this inspect test page content?
Not on the browser-proxy path. HTTPS page content is not decrypted; policy is enforced through domains, metadata, configured rules, and category data.
Related use cases