SOAX

What Is SOAX?

You’re trying to access websites reliably without getting blocked, rate-limited, or flagged as “bot traffic.” Or you need to test how a site behaves from a specific city/ISP. A normal VPN often isn’t enough for that: the IP ranges are well-known, traffic patterns are predictable, and many targets treat VPN egress as “suspicious by default.”

SOAX sits in a different category: it’s a paid proxy network and control plane designed for routing HTTP/HTTPS/SOCKS5 traffic through residential and mobile IP space, with lots of knobs for routing, rotation, and guardrails. The goal isn’t “one-click privacy” like a consumer VPN; it’s controlled, programmatic access to the public web for teams doing scraping, automation, QA, ad verification, and geo-specific testing.

What makes it distinctive (versus many proxy sellers) is how much configuration SOAX exposes around sessions, rotation behavior, DNS handling, filtering, and error reporting, plus a pricing model that’s explicitly per-GB with geo tiers and “credits” accounting. (proxyway.com)

SOAX Features and Performance

SOAX is fundamentally a proxy service, not a VPN app. You connect to SOAX using standard proxy protocols and route traffic from your browser, scraper, or automation stack through SOAX infrastructure. On its site, SOAX lists support for HTTP, HTTPS, and SOCKS5, and also notes TCP and UDP transport support (relevant mainly for SOCKS5 use cases).

Protocols and authentication

From an integration standpoint, SOAX supports two main authentication approaches: username/password and an IP allowlist model. SOAX explicitly describes “Flexible authentication” with username/password and IP allowlist, and its integration guides walk through using either credentials or whitelisting for authorization.

SOAX also organizes access around the concept of packages (their term). Packages are used to separate projects/teams/use cases, each with its own authentication, routing rules, limits, and tracking. That’s useful if you want one set of rules for “production scraping,” another for “QA testing,” and a third for “partner access,” all under one account. (soax.com)

Rotation, sessions, and “control plane” features

SOAX emphasizes control over how requests are grouped and rotated. Its site describes sessions as defining how requests are “grouped” and “isolated,” and its rules system covers routing/rotation/error handling/filtering.

Independent testing/review coverage (Proxyway) describes multiple controls that matter in real-world scraping reliability:

• You can choose what happens when a proxy peer goes offline (switch device by default, fail requests, or use a “look-a-like rotation” option). (proxyway.com)
• You can choose where DNS gets resolved: at the SOAX gateway or at the proxy peer. (proxyway.com)
• You can block domains you don’t want to access (a practical way to reduce wasted bandwidth on third-party assets, or enforce compliance constraints). (proxyway.com)
• SOAX returns provider-specific error signaling in headers like X-SOAX-Error and X-SOAX-Detail (useful for retry logic and debugging). (proxyway.com)

These aren’t “privacy tool” features in the consumer sense; they’re operational features for keeping large-scale traffic stable and predictable.

Targeting (geo/ISP) and routing granularity

SOAX’s public pricing page shows targeting support at least down to Country, Region, City, and ISP across plans, with higher tiers adding additional targeting fields (it lists ASN and ZIP at higher tiers). (soax.com)

That’s a big part of why people pay for networks like this: not just “be in the US,” but “be in this city, on this ISP/carrier footprint,” which can materially change how a target site responds.

Performance reality check (what you should expect)

SOAX doesn’t publish a single universal “speed” number that you can count on, and that’s normal: residential/mobile proxy performance varies heavily by target site, geography, and session/rotation strategy. That said, third-party benchmark-style posts exist, but the most credible takeaway is not a single latency figure—it’s that the provider choice affects success rate and response time, while configuration and browser identity often matter as much or more. A Reddit benchmark post that included SOAX alongside multiple other providers reported specific average response times and success rates for test targets. Treat that as anecdotal (not a lab standard), but it matches what you see in practice: proxy networks are not “set and forget.”

If your goal is “private browsing” in the everyday sense (hide from your ISP, stop trackers, avoid fingerprinting), SOAX is the wrong primary tool. But if your goal is “don’t get blocked, and control exit location/IP behavior,” SOAX is built for that.

Pricing and Plans

SOAX is paid and uses a usage-based structure built around prepaid credits and per-GB rates that vary by plan and “geo tier.” The pricing page describes plans (including Sandbox, Builder, Team, Scale, Enterprise) and explains that credits are “prepaid usage units” used across products available to the account. (soax.com)

Published plan structure (what’s clear)

• SOAX states “One rate across residential and mobile.” (soax.com)
• It groups countries into three geo tiers (Tier 1 highest, Tier 3 lowest) and charges based on the country of the egress IP (the proxy IP that connects to the destination). (soax.com)
• It charges based on data transferred in both directions, including partial responses, retries, and interrupted connections, and defines 1 GB as 1,000,000,000 bytes. (soax.com)

Prices (only where the public pricing page is explicit)

SOAX’s pricing page shows example per-GB rates and plan fees. For example, it lists a Tier 1 rate of $5.00/GB on Sandbox and $3.00/GB on Builder, and shows Builder as $200 monthly (with a calculator example that reaches $300 total at 100 GB via extra credits). It also shows higher plan fees (e.g., $500, $1,500, $3,000) alongside lower per-GB rates. (soax.com)

SOAX also shows credit rollover periods (commonly 60 days on the pricing table; Enterprise shows a “60/365 days” entry on the page). (soax.com)

Because SOAX’s pricing is presented as a matrix (plan fee + included credits + top-ups + geo tiers), the most honest summary is: you pay a monthly plan fee, receive credits, and spend credits based on per-GB rates that depend on plan and egress geo tier. (soax.com)

Refunds and billing policy

SOAX’s Terms of Use include a Billing and Refund Policy (versioned and dated). In that policy, SOAX states a general rule that plan fees, top-up credit fees, and overage fees are non-refundable, with listed exceptions and SOAX discretion for adjustments. It also states that adjustments may be handled via internal billing mechanisms (such as credit notes or balance adjustments). (soax.com)

Bottom line: don’t assume a consumer-style “30-day money-back guarantee.” Read the policy, and expect refunds (if any) to be exception-based rather than automatic. (soax.com)

Privacy and Security Assessment

Jurisdiction: England and Wales

Your database lists jurisdiction as England and Wales, and SOAX’s legal terms identify the company as SOAX LTD incorporated under the laws of England and Wales with a registered office in Uxbridge, England. (soax.com)

Jurisdiction matters less here than with a VPN because SOAX is not primarily positioned as an anonymity provider. Still, it’s relevant because your account, billing, and operational logs (whatever they keep) sit under UK legal context.

Logging posture (what SOAX actually says)

SOAX publishes a Privacy Policy that describes categories of data it processes, including usage data, login and authentication data, and account-related data to operate the platform. It also mentions KYC/KYB data “where applicable” for eligibility for certain services or payment methods. That is the opposite of a “no data ever” stance, and it’s important: proxy infrastructure providers typically must log some operational data to run abuse controls, billing, and reliability.

What you should look for (and what we did not see clearly in the surfaced sources): an independent, public “no-logs” audit in the way top VPNs sometimes publish. If SOAX has one, it wasn’t confirmed in the sources we pulled for this review—so we’re not going to claim it exists.

Open-source posture

Nothing in the sources above indicates SOAX is open source, and there’s no evidence of public reproducible builds or client source releases in the material we referenced. So for transparency, assume it’s a proprietary commercial platform unless SOAX states otherwise elsewhere.

Known criticisms and risk considerations

• Residential/mobile proxy networks come with inherent trust trade-offs. You are routing traffic through third-party infrastructure and/or endpoints. That’s not unique to SOAX, but it matters if your mental model is “VPN = privacy.” With proxies, the provider can still be in a position to observe metadata and enforce policy. (This is a general proxy reality, not a SOAX-specific accusation.)

• Supply-chain questions exist in the proxy industry. Proxyway’s broader market research has previously flagged concerns about residential proxy composition for multiple providers and notes that SOAX had a specific issue in older measurement work (e.g., a higher-than-expected share of commercial IPs in a 2021 dataset). That’s historical and not proof of current conditions, but it’s relevant context: don’t buy any proxy provider purely on “pool size” claims. Test what you receive.

• SOAX explicitly restricts mapping/fingerprinting/benchmarking their network in its Terms of Use. That’s legally normal for providers protecting their network, but it also makes independent verification harder for customers.

Strengths and Limitations

Strengths

• Strong protocol coverage for proxy workflows: HTTP/HTTPS/SOCKS5, plus stated TCP/UDP support.
• Clear operational controls around sessions, routing rules, DNS resolution options, and error signaling (useful for automation at scale).
• Per-GB pricing is transparent on the public page, with geo-tier logic explained and a cost calculator. (soax.com)
• Team/project separation (“packages” and seats) is built into the model, which is better than sharing one credential across everything. (soax.com)

Limitations

• Not a VPN, and not “private browsing” in the consumer sense. It won’t magically stop fingerprinting, tracking scripts, or ISP-level visibility for non-proxied traffic.
• Refunds are not positioned as unconditional. The policy states plan/top-up/overage fees are non-refundable by default, with exceptions. (soax.com)
• Usage-based billing can surprise you because SOAX counts data both directions and includes retries/partial responses in usage. (soax.com)
• You may need time to configure it well (rotation, sessions, DNS behavior, allow/deny rules). The power is there, but it’s not one-button-simple.

Who Should Use SOAX?

Good fit

1. Web scraping / data collection teams that need residential/mobile egress and want control over routing, rotation, DNS handling, and error diagnosis.
2. QA, localization, and ad verification workflows where you must test location- and ISP-specific behavior (country/region/city/ISP targeting is a core part of the platform). (soax.com)
3. Automation stacks using anti-detect browsers (SOAX publishes integration guides for tools like Multilogin and Undetectable, which is a common pairing in this space).

Not a good fit

1. People who just want a VPN for everyday privacy (ISP shielding, simple on/off, device-wide tunneling, streaming access). SOAX is proxies + control plane, not a consumer VPN.
2. Anyone who needs a clear “no-logs audited VPN-style promise.” We did not confirm an independent no-logs audit in the sources used here, and SOAX’s Privacy Policy explicitly describes collecting usage/login/account data.
3. Users who want predictable flat-rate pricing. SOAX is usage-based per GB with geo tiers, and usage includes retries and partial responses—great for scalability, not great for “set budget and forget.” (soax.com)