Bright Data

Bright Data routes requests through a superproxy backconnect gateway. For residential proxies, each outbound connection exits through a different peer device unless a sticky session is active. Targeting parameters — country, city, ZIP, ASN, carrier — are passed in the proxy username string per request, without changing zones or plans. The gateway handles peer selection, failover, and session management transparently.

Sticky sessions are activated by appending a -session parameter to the proxy username. The session persists until idle for 7 minutes — this threshold is fixed and cannot be configured. Both rotating and sticky modes can coexist within the same proxy zone by passing different parameters per request. Rotation configuration is code-level only — there is no dashboard toggle. Authentication is credential-based: username and password embedded in the proxy URL. IP whitelisting is not documented as a primary authentication method.

Bright Data's bet is that compliance infrastructure and scale can be sold as a single product. The residential pool is sourced through a proprietary SDK in opt-in partner apps — users explicitly consent and are compensated monthly. KYC is applied to clients. The Acceptable Use Policy prohibits a defined list of regulated use cases. The intent is to make the network defensible, legally and reputationally, at enterprise scale.

The honest limitation: compliance overhead is real. KYC adds friction before you access the full residential pool. For teams that need to show a DPA, an AUP, and a documented sourcing model to their legal department, Bright Data's documentation stack includes documented DPA, AUP, Code of Ethics, and EWDCI membership as part of the compliance stack. For teams that need to start making requests today — it's the wrong starting point.

On anti-bot protected targets — Cloudflare, Akamai, Datadome — Bright Data is positioned as suitable for large-scale scraping with proper rotation logic. Success on these targets depends on request strategy and session management, not just proxy quality. This is a compliance-first, scale-first network. If you need speed and simplicity, it's the wrong tool.

The residential pool contains 150M+ unique IPs across 195 countries — self-reported, no independent third-party audit of this figure exists. City, state, ZIP, and ASN targeting are confirmed for residential and mobile proxies. Datacenter and ISP static proxies support country and city targeting only — ZIP and ASN targeting are not available on those types. Mobile proxies cover 3G/4G/5G networks with carrier targeting; the total number of unique carrier operators is not published in public documentation.

Session behavior: rotating mode (new peer per request) is default. Sticky sessions are activated via the -session parameter. The idle timeout is fixed at 7 minutes and cannot be changed. Concurrent session limits are not documented in public evidence. Automatic Failover replaces unavailable peers on the next connection without requiring code changes. HTTP, HTTPS, and SOCKS5 protocols are confirmed. Username/password authentication is required — IP whitelisting is not documented as a primary authentication method.

IPv6 proxy support is not documented in public evidence. ISP static coverage is approximately 50 locations — substantially narrower than the residential network's 195-country footprint. The provider states a 99.9% datacenter success rate — self-reported and not part of the SLA.

Residential and mobile proxies are billed per GB. Datacenter proxies are available per GB (shared) or per IP (dedicated). ISP static proxies are billed per IP. PAYG is available for all proxy types with no monthly commitment. Subscription plans add volume discounts. Free trial credits are available for new accounts. After the trial, continued access requires payment — there is no ongoing free tier.

The pricing page displays promotional discounts alongside standard rates, which makes it difficult to establish what the actual base rate is before testing. Enterprise pricing above standard tiers requires contacting sales. Monthly commitment balances reset — unused funds do not roll over while the account is active. For teams with variable or unpredictable monthly volume, this structure adds cost risk that PAYG eliminates at the expense of per-GB rates.

You gain a residential proxy pool reported at 150M+ unique IPs — self-reported, no independent audit exists. Targeting depth on residential and mobile includes ZIP and ASN parameters. The compliance documentation stack includes DPA, AUP, Code of Ethics, and EWDCI membership. Automatic failover handles peer failure transparently. The SLA covers 99.99% uptime with a 15-minute engineer response on covered plans.

You give up simplicity at every layer. KYC before full residential access. Pricing complexity that requires testing to understand. Rotation configuration via code-level parameters — no dashboard toggle. A 7-minute session idle limit that cannot be extended without running additional infrastructure. No dedicated pip or npm SDK. ZIP and ASN targeting disappear on datacenter and ISP proxy types. The 15-minute SLA response only applies to SLA-covered plans — PAYG users are on standard support. The independent audit that would verify the claimed pool size and success rates does not exist.

• You're scraping Cloudflare, Akamai, or Datadome-protected targets at high volume and other residential networks are hitting block walls
• Your team needs to show legal documentation — a DPA, an AUP, and a documented sourcing model — before procurement can approve a proxy vendor
• You're running multi-region price intelligence or market data pipelines that require consistent city or ZIP-level IP targeting at scale
• You need dedicated residential IPs with exclusive peer assignment — where IP sharing with other customers is not acceptable
• You're building custom automation pipelines where per-request targeting via username parameters fits the architecture

Bright Data's constraints are structural, not incidental:

• You need to start making requests today without a KYC process — the verification requirement blocks immediate full-network access
• Your sessions need to persist longer than 7 minutes without maintaining additional keep-alive infrastructure — the idle timeout is fixed
• Your targets require ZIP or ASN-level precision on datacenter or ISP proxy types — those targeting levels are residential and mobile only
• Your budget is startup-scale — the pricing structure is optimized for teams spending thousands per month, not hundreds
• You need IPv6 proxy addresses — IPv6 support is not documented in public evidence

If Bright Data's scale or compliance overhead doesn't match what you need:

• Oxylabs — enterprise proxy provider with ISO 27001 and SOC 2 Type 2 certification; relevant if independently audited compliance documentation is required rather than self-reported
• Decodo — residential proxy provider with ISO 27001 and EWDCI co-founder status; relevant for teams prioritizing simpler onboarding and lower entry thresholds
• Webshare — lowest friction entry for datacenter proxies, including a permanent free tier; the right path if your targets don't require residential IPs and cost is the binding constraint

If you're not already hitting scaling limits on other residential networks, you don't need Bright Data. Use it if your targets are heavily protected, your volume justifies enterprise pricing, and your team can manage code-level proxy configuration with a KYC onboarding process. Skip it if you need a fast start, if your targets don't require residential IP quality, or if a fixed 7-minute session limit breaks your pipeline architecture.