SOAX

SOAX routes requests through a proxy network where the exit IP selection, session behavior, and targeting parameters are controlled via the proxy username string. The network supports rotating and sticky session modes. Rotating mode assigns a new exit IP per request. Sticky mode reuses the same IP across requests until the session expires. An IP refresh rate that is customizable is confirmed in the plan features — the specific maximum sticky session duration is not published in public documentation.

Targeting parameters — country, region, city, and ISP — are passed in the proxy username. ASN targeting is absent from the documented feature set. Texas is excluded from the network due to regulatory constraints on IP address usage and anonymity in that state — this is documented on the pricing page and is a geographic boundary on the network, not a configuration option. Authentication uses username/password in the proxy string. IP whitelisting is not confirmed as a primary authentication method in evidence.

The network supports HTTP(S), SOCKS5, UDP, and QUIC protocols — confirmed in the pricing page feature list. Multi-language proxy API access is available with PHP, Python, .NET, Java, JavaScript, C/C++, and C# confirmed on the proxies page. The dashboard provides diagnostics including speed, failure rates, and banned IPs. Custom reports and alerts are available. Sub-user or team account management is not confirmed in public documentation.

SOAX is built around protocol completeness paired with pool depth at a mid-to-upper pricing tier. The addition of UDP and QUIC alongside the standard HTTP(S) and SOCKS5 stack expands support for non-HTTP transport use cases. The residential pool is sourced from users who voluntarily share bandwidth — consent-based sourcing is stated on the trust page. GDPR and CCPA compliance are stated. SOC 2 and ISO 27001 certifications are explicitly described as in progress on the trust page — they have not been obtained.

The compliance gap between "in progress" and "certified" matters for procurement teams that require documentation rather than stated intent. For teams that can accept stated compliance without third-party audit, SOAX's documentation stack covers the basics. For teams that need to show an auditor an ISO certificate, the gap requires revisiting once the certification is completed. The Texas exclusion is a second factual constraint that informs geographic scope planning — it is not a minor edge case if your targets include Texas-based services that respond to local IPs.

SOAX serves teams that need residential and mobile IP quality across a large pool with diagnostic visibility into failure rates and banned IPs. Suitability for anti-bot protected targets depends on rotation strategy and session management — not just protocol or pool size. The network is not positioned as a no-configuration anti-blocking solution.

The residential pool is reported at 155M+ unique IPs across 195+ countries — self-reported, no independent third-party audit of this figure exists. The mobile pool is reported at 33M+ IPs from real cellular carriers covering 5G/4G/3G/LTE networks. Datacenter proxies are available in the US in shared and dedicated configurations. ISP static proxies are available with per-IP billing starting at 300 IPs minimum. Country, region, city, and ISP targeting are confirmed. ASN targeting is absent from the documented feature list. Texas is excluded from the proxy network — it is not available as a targeting destination.

Rotating and sticky sessions are both confirmed. Customizable IP refresh rate is documented. Maximum sticky session duration is not published in the pricing page feature list or FAQ. Concurrent session limits are not documented in public evidence. HTTP(S), SOCKS5, UDP, and QUIC protocols are all confirmed. No API rate limits or concurrency caps are documented in the public API reference.

The dashboard reports speed metrics, failure rates, and banned IP counts. Custom reports and alerts are confirmed. IP whitelisting as a primary authentication method is not confirmed — credential-based authentication is the documented default. The provider is headquartered in London, UK. GDPR and CCPA compliance are stated on the trust page — no independent audit of those compliance claims is referenced.

Four monthly tiers are documented: Starter at $90/month (25 GB, $3.60/GB), Advanced at $170/month (50 GB, $3.40/GB), Professional at $740/month (300 GB, $2.46/GB), and Business at $1,600/month (800 GB, $2.00/GB). Enterprise pricing from $0.32/GB is available by negotiation. A 3-day trial with 400 MB is available for $1.99. ISP and datacenter proxies are available per-IP starting at 300 IPs minimum.

No permanent free tier is available — the minimum entry is the $1.99 trial. All plans are monthly subscriptions with explicit per-GB rates published on the pricing page. The pricing page documents four standard tiers and enterprise by negotiation — there is no ambiguity between pricing grid and FAQ sections. Whether unused monthly bandwidth rolls over is not documented on the pricing page.

You gain HTTP(S), SOCKS5, UDP, and QUIC documented within a single network — UDP and QUIC support are documented alongside HTTP(S) and SOCKS5. The residential pool at 155M+ and mobile pool at 33M+ provide large-scale coverage for residential and mobile use cases. Failure-rate and banned-IP diagnostics in the dashboard give operational visibility that generic usage-only dashboards lack. ISP and city targeting are both confirmed. Pricing tiers are transparent with no pricing-grid inconsistencies reported in evidence.

You give up ASN targeting, which limits precision for carrier-specific or network-specific targeting scenarios. Texas is excluded from the network — this is a geographic hard stop that no configuration can override. Maximum sticky session duration is not published, which makes session planning for long-duration scraping jobs harder to design without testing. SOC 2 and ISO 27001 certifications are in progress and not yet obtained — compliance-driven procurement cannot rely on these credentials yet. Sub-user or team management is not confirmed in public documentation. IP whitelisting as a primary authentication method is not documented.

• Your scraping pipeline uses QUIC or UDP transport layers that require proxy support beyond the standard HTTP(S)/SOCKS5 stack
• You need a combined residential and mobile pool at scale without separate network products — the 155M+ residential and 33M+ mobile pools are a single platform
• Dashboard diagnostics showing failure rates and banned IPs are part of your operational monitoring workflow, not just bandwidth consumption
• ISP-level targeting on residential proxies is required — SOAX confirms ISP targeting, which many mid-market providers omit
• Your geographic scope does not include Texas — the network exclusion is not a constraint for use cases focused on non-Texas markets

SOAX's constraints are structural, not incidental:

• Your use case specifically requires Texas residential or mobile IPs — the state is excluded from the network by regulatory constraint, and this cannot be worked around with configuration
• Your pipeline requires ASN-level targeting on residential or mobile proxies — ASN targeting is not in SOAX's documented feature set
• Your procurement team requires ISO 27001 or SOC 2 certification before approval — both are in progress and have not been obtained as of the last evidence review
• You need to enforce sticky session duration precisely for multi-step web workflows — maximum sticky session duration is not published, making reliable session timeout design impossible without empirical testing
• Sub-user or team account isolation is required across multiple projects — team management features are not confirmed in public documentation

If SOAX's Texas exclusion, missing ASN targeting, or pending certifications are blockers:

• Bright Data — documents full US geographic coverage including Texas, with ASN targeting and EWDCI membership; fits if the Texas gap is the primary constraint
• Decodo — ISO 27001:2022 already certified with EWDCI co-founder status; fits if compliance certification rather than protocol breadth is the driving requirement
• NetNut — ISP-direct sourcing via DiviNetworks with 85M+ residential pool; fits if the sourcing model (B2B from ISPs, not P2P consent) is relevant to your compliance posture

Use SOAX if UDP and QUIC protocol support matter to your pipeline, if combined residential and mobile pool depth at scale is a requirement, and if your geographic scope excludes Texas. Skip it if ASN targeting is required, if your procurement needs ISO or SOC 2 documentation now rather than at some future certification date, or if Texas IP coverage is a hard requirement for your use case.