SOAX Review

SOAX launched in 2020 with residential proxies. It is operated by SOAX LTD, registered in England and Wales, with its registered address in Uxbridge. The business now combines a self-service proxy platform with managed data delivery for customers who want an agreed dataset, format and collection schedule.

Residential and Mobile use the same traffic rate within a given plan and geographic tier. A plan's credit allowance can therefore be spent across both networks without reserving a separate mobile quota. Geography still affects consumption: the allowance represents spending units, with the number of GB depending on where traffic exits.

Country, region, city and ISP filters are available throughout the plan range. ASN and ZIP selection require Scale or Enterprise. This is a consequential difference between tiers for a project that needs a particular autonomous system or postal area; basic access to the Mobile network does not carry that same plan restriction.

Sandbox provides ongoing access to both networks without a recurring subscription fee. Traffic is paid for through credit top-ups; there is no included free traffic allowance. It supports 2 packages and 1 user, making it a way to evaluate actual connections and controls before committing to a paid plan.

SOAX documents 4,000 simultaneous connections per proxy gateway for Sandbox, alongside package and account limits.

Access is issued through packages, each with its own proxy password, permitted networks, source-IP allowlist and usage limits. Quick Connect generates connection settings for the selected network, location and session behavior, and includes a connection check.

Credentials and source-IP allowlisting can operate together, with authorization controlled per package. Paid activation is subject to the identity or business checks requested in the dashboard.

Packages give individual jobs their own access and capacity controls while drawing on the organization's shared funds. Each has limits for requests per second and simultaneous connections, plus an optional GB cap. Account-wide ceilings still apply across packages. The GB cap is useful for containing an experiment, although the corresponding credit cost changes with its geographic tier.

Usage reporting breaks consumption down by package, network, country and tier, with credits, GB and average credits per GB. More detailed logs include destinations and exit addresses, and can be exported as CSV. This makes it possible to trace a rise in spending to the workload or geography responsible.

Human access uses Owner and Member roles. Owners administer billing, packages, limits and the team; Members use their assigned packages and permitted analytics. The management API offers finer restrictions through key permissions and package scope. A monitoring service can receive usage access without receiving authority to change proxy passwords or manage every package in the organization.

The API covers packages, connection strings, credentials, locations, credit blocks and analytics. Its limits are 5 calls per second per API key and 500 per minute per source IP. These apply to administrative calls; proxy traffic has its own package and account limits.

The developer reference documents connection rules, package limits, permissions and error behavior in detail. Its troubleshooting guidance draws a useful boundary around automatic recovery: a successfully delivered CAPTCHA page or target-side rejection is not the same as a failed proxy connection. Within an encrypted HTTPS tunnel, the proxy cannot inspect the page to make that distinction for the application.

SOAX's recovery controls therefore help maintain transport, while the collector still has to recognize unusable results. This is particularly relevant when assessing the service's advertised retry features for protected websites.

Payment options include Visa, Mastercard and American Express, cryptocurrencies, and bank transfer. USD is the contractual base currency unless the agreed order specifies otherwise. Applicable taxes are added according to billing details and the transaction; invoices are available in Billing.

Paid plans include traffic credits, and extra credits can be purchased without changing the plan. Subscription renewals are charged separately from the traffic balance. Both uploaded and downloaded data count once a connection is established. A delivered challenge page or an unsuccessful application result can therefore consume credits, as can the transferred data from retries.

Credits have their own expiry dates. The published period is 60 days for Sandbox and monthly plans, and 12 months for annual plans. The earliest-expiring block is used first. Renewal or a plan change does not restart the clock, so rollover offers a limited opportunity to use spare capacity rather than indefinite storage.

Ordinary prepaid access is paused or limited when credit is exhausted. Postpaid continuation requires business approval, verification and written terms. After a paid subscription ends, the account returns to Sandbox: unexpired credits remain usable, but Sandbox's rates and limits apply. Closing the account can forfeit the remaining balance.

Subscription charges, top-ups and overage are ordinarily non-refundable. The policy reserves exceptions for billing errors, defined service failures, certain provider-initiated termination and mandatory consumer rights. Unused credits or disappointing results from a target website do not create a general refund entitlement.

Billing errors must be reported within 30 calendar days with the payment or invoice details. SLA compensation is separate and is issued as credit toward future bills. Sandbox has no subscription fee against which those service credits can be awarded.

Some destinations and ports are restricted by default, including mail traffic on ports 25, 465 and 587. Verified account Owners can request access exceptions through package controls, subject to review. Financial, government and certain news resources are among the categories discussed in the restrictions.

The acceptable-use terms also address business models that go beyond ordinary collection. They restrict unauthorized resale and white-label access, competing infrastructure, and supplying node or IP attributes to enrich proxy-detection and reputation databases. Those conditions are relevant to data and security products that would otherwise treat proxy access as an unrestricted input.

SOAX distinguishes round-the-clock AI support from human assistance. Sandbox has AI support; paid plans add human coverage during published hours, and Enterprise adds a customer success manager. Chat, tickets and email are the main contact routes. The plan's “24/7” label therefore needs to be understood in that context.

The SLA covers SOAX's own management and proxy systems. Target-site blocks, the accuracy of returned data and failures of a deliberately bound node are outside that guarantee. This makes the contract a measure of provider availability rather than a promised scraping completion rate.

Managed Data Acquisition is the offer for customers who want SOAX to deliver an agreed dataset. The work can include source assessment, extraction, parsing, validation and ongoing operation, with a defined schema and schedule. Delivery options include JSON, JSONL, CSV and Parquet through cloud storage, SFTP or an API. Custom Solutions extend this arrangement to a tailored API or feed. Both involve a sales-led agreement rather than activating a proxy package.

Headful Browser provides a browser runtime close to the exit node, with state, cookies and the page preserved between steps. Its purpose is multi-step browser work where repeated interaction and continuity matter. Web Data API offers structured retrieval for supported types of public-web targets, removing the need for the customer to maintain those parsers. Both are in closed alpha on the new platform and require separate access arrangements. They are relevant to SOAX's direction, but should not be counted as features immediately available inside an ordinary proxy subscription.

The public utility range includes a proxy checker, IP checker, cURL converter and browser fingerprint test.