SOAX

Builder, Team, and Sandbox charges

SOAX describes Builder and Team as paid plans with monthly credit allocations; Sandbox has no plan fee or allocation credits. The pricing page lists these plan fees, excluding VAT:

• Builder — $200 per month plus VAT (pricing page, checked 2026-10-30).
• Team — $500 per month plus VAT (pricing page, checked 2026-10-30).

SOAX states that one credit equals $1 and plans convert to credits automatically each month. Proxy usage is then charged against credits based on data transferred, the plan, and the egress IP geo tier. VAT is calculated at checkout from the billing address and is excluded from listed prices.

The Sandbox has no subscription fee or included credits, but top-up credits can be purchased for use at Sandbox rates and limits. By contrast, pricing and support describe Sandbox as not a free trial.

The homepage says SOAX accepts card, bank transfer, or crypto payments, with KYC required for crypto. The pricing page says the vendor accepts most major credit and debit cards, while bank transfer may be available to approved business accounts. The support page says postpaid billing is available for approved business accounts, is off by default, and requires business verification and written agreement on rates and payment terms.

SOAX states that paid plan fees are generally payable in advance; its terms define monthly and annual billing cycles as 30 calendar days and 365 calendar days. The billing policy says plan, top-up, and overage fees are generally non-refundable, subject to stated exceptions.

Residential, mobile, and data tools

SOAX describes its offering as proxies alongside a Web Data API, scraper APIs, AI-powered scraping tools, and a Web Unblocker. Its Web Data API is promoted for collecting pricing data from ecommerce platforms, price aggregators, and apps. The provider says the API extracts pricing data without requiring proxy management, CAPTCHA solving, or JavaScript rendering.

Pool-size claims differ across SOAX pages. The developer documentation describes a residential pool of over 155 million IPs across 195+ countries. A use-case page lists 155 million residential IPs and 195+ available geolocations. The about page instead describes a pool containing more than 191 million ethically sourced IPs.

Mobile figures also vary: developer documentation states over 30 million mobile IPs from carriers worldwide, while the use-case page lists 33 million across 5G, 4G, and LTE. Headful Browser is described as a stateful browser runtime co-located with SOAX exit nodes and in closed alpha.

Rotation, sessions, and protocols

SOAX says requests pass through its nodes, so target websites see a node address instead of the customer’s IP. Rotation can be configured per request, after a set number of requests, after a set time, or on error. A sticky session instead keeps requests on a single node without rotation.

The provider describes HTTP, HTTPS, and SOCKS5 support, and separately lists support for TCP and UDP. Customers can manage access through the dashboard or integrate using their preferred language; examples are provided for Python, Node.js, Go, and curl.

Headful Browser has a separate provisioning path and cannot be toggled from an existing plan’s dashboard. Because it is in closed alpha, endpoint signatures, schema shapes, and rate-limit behavior may change before general availability.

Questions for support before registration

Before choosing a proxy service, buyers typically match the expected workload to the provider’s billing unit and session options. Ask how the intended request pattern is charged, including what counts as transferred data and whether the relevant location changes the rate.

Clarify how long unused prepaid credits remain valid and what happens when the balance runs out. Ask which plan-specific features, limits, usage rates, and access entitlements apply to the account, rather than assuming every package works identically.

For a technical evaluation, ask whether the required integration approach and setup requirements are documented. Request details on operational traffic limits, support response and escalation terms, and the applicable geo-tier rates before committing to a workload.

Credit expiry and payment boundaries

SOAX’s pricing page states that credits added on Sandbox or a monthly plan expire 60 days after they are added. Annual-plan credits expire 12 months after they are added, according to support. The terms separately describe monthly-plan credits as generally valid for 60 calendar days after grant or purchase.

Usage accounting includes both traffic directions, partial responses, retries, and interrupted connections. Without postpaid billing, usage stops when prepaid credits reach zero. Credits cannot be withdrawn or transferred to another account.

The billing policy says plan, top-up, and overage payments are generally non-refundable, subject to stated exceptions. Cancelling a self-service plan stops its next renewal, but paid access continues through the current paid period. Upgrades take effect immediately and downgrades start at the next billing cycle; existing credits and packages remain unchanged mid-cycle.

The terms say the service is designed primarily for business use and SOAX may restrict or decline personal or consumer access. Several details are missing; they are listed under What we could not confirm.

Routing controls and shared credits

SOAX’s stated controls let buyers choose between changing nodes and retaining one node.

• Rotation can follow each request, a set request count, a set time, or an error.
• A sticky session keeps requests on one node without rotation.
• Residential and mobile proxies are available, with targeting down to city, state, and ASN level.
• The provider supports username/password and IP allowlist authentication.
• Credits are prepaid usage units shared across SOAX products available to the account.
• Customers can manage access through the dashboard or use language examples provided by SOAX.

These controls offer choice, but the account’s plan still determines its included features, limits, rates, and credits.

Business workloads and public-web data

SOAX identifies products using fresh public-web data as runtime input as intended customers. The provider also presents its Web Data API for collecting pricing data from ecommerce platforms, price aggregators, and apps.

SOAX says rotating residential proxies suit large-scale data collection, while mobile proxies suit mobile-specific pricing. Its terms describe the platform as designed primarily for business use and permit restrictions or declined access for personal or consumer users.

Compare proxy billing and session terms

When comparing proxy services, match the proxy type and billing unit to the workload. Check whether session controls suit the request pattern, how location targeting affects charges, and which usage rules govern retries, data transfer, and prepaid balances.

Questions on SOAX credits and sessions

Is Sandbox a free trial?

Sandbox is not a free trial, according to SOAX’s pricing and support pages. It has no subscription fee and includes no credits; top-up credits can be purchased for use at Sandbox rates and limits.

How does SOAX charge proxy usage?

SOAX charges proxy usage in credits based on transferred data, the plan, and the egress IP geo tier. Its pricing page counts both traffic directions, partial responses, retries, and interrupted connections as usage. Ask which rate applies to the intended location and plan before estimating consumption.

What is the difference between rotation and a sticky session?

Rotation can be set to occur per request, after a request count, after a time, or on error. A sticky session instead keeps requests on one node without rotation. Choose between them according to whether the workload needs changing nodes or a retained node.

How does SOAX handle targeting and authentication?

SOAX states that targeting reaches city, state, and ASN level, and that authentication supports username/password or an IP allowlist. The provider also lists HTTP, HTTPS, and SOCKS5 protocols.

Is Headful Browser part of an existing plan?

Headful Browser is in closed alpha and uses separate provisioning; it cannot be toggled from an existing plan’s dashboard. SOAX says its endpoint signatures, schema shapes, and rate-limit behavior may change before general availability.

Proceed when the credit terms fit

Fits if the intended workload’s data-based credit charging, location tier, and credit validity are clear before registration.

Probably not if the workload requires access after prepaid credits reach zero without approved postpaid billing.

Main risk… usage includes retries, partial responses, and interrupted connections, while plan and top-up payments are generally non-refundable.

Sources

Every fact on this page traces back to a public page listed here, with the day it was read.

• soax.com/pricingchecked 2026-10-30
• soax.comchecked 2026-10-30
• soax.com/supportchecked 2026-10-30
• soax.com/use-cases/price-monitoringchecked 2026-10-30
• developers.soax.com/getting-started/what-is-soaxchecked 2026-10-30
• soax.com/legal/terms-of-usechecked 2026-10-30
• soax.com/aboutchecked 2026-10-30

Notes on the making of this review

Editorial team of Payout Desk. This page rests on the public sources listed above, which Payout Desk checked on 2026-10-30. There was no hands-on testing. The page is updated when the sources change.

Last updated: 2026-10-30

Right of reply

If you represent SOAX and think this entry is inaccurate or out of date, write to us and attach evidence. After the refutation is documented, the entry is corrected or removed. No payment changes what we publish.

Our contact for replies

No data available

Response time

No data available

Contact · Affiliate disclosure

Other reviews in this category: Proxies

• LiveProxies — Proxies
• IPFoxy — Proxies
• FloppyData — Proxies