SOAX Alternative for Mobile Proxies

At a glance

The SOAX column comes from its pricing page and mobile proxies page, read on 30 October 2026. The Coronium column comes from the live catalog when this page loads. For a SOAX comparison with another per-GB provider, see SOAX vs Decodo.

How SOAX bills mobile traffic

SOAX uses one rate card for residential and mobile traffic. You pick a plan, and the plan sets a per-GB price for each geographic tier. The exit country decides the tier.

On the pricing page checked for this article, the plans were Sandbox with no subscription fee and no included credits, then Builder at $200 a month, Team at $500, Scale at $1,500 and Enterprise at $3,000, each plus VAT and each including credits equal to its fee. One credit buys roughly one dollar of usage. Tier 1 rates ran from $5.00 per GB on Sandbox to $3.00 on Builder, $2.20 on Team, $1.50 on Scale and from $0.85 on Enterprise. Tier 3 rates were lower, from $2.00 on Sandbox down to $0.35 on Enterprise. Credits from monthly plans stay valid for 60 days from the date they arrive, and top-up credits can be bought on any plan.

Two things follow for planning. A subscription only pays off if you use most of its credits within the 60-day window, so size the plan to your real monthly traffic rather than your peak month. And the country you need changes the price, so compare at your actual exit country rather than the lowest rate on the page.

How a dedicated line bills

A Coronium line is priced per device and period: 24 hours, 7 days or 30 days, in USD. Not every carrier offers all three periods. Data is not metered on dedicated lines, so a busy month and a quiet month cost the same. Brazil is the exception, with 20 GB of mobile data per month per line.

There is no subscription or credit expiry. You buy a line for a period, renew it if you want to keep it, and stop when you are done. Teams buying 10 or more lines can ask for a 10% discount code, or 15% from 25 lines.

The trade-off is that you pay for the line whether you use it or not. For light, occasional work, metered credits cost less.

Cost at three traffic levels

This assumes the United States sits in SOAX's Tier 1, as its pricing page indicated when we checked, and leaves out VAT. At Sandbox rates, one US line costs the same as about 28 GB of traffic; at Builder rates, about 46 GB. Our proxy cost estimator runs the same arithmetic with your own numbers and countries.

What you get after buying

The two products also differ in what lands in your account.

With SOAX, you get access to a gateway. You build a username that encodes the country, region, city, ISP or session you want, and the gateway picks a device for each connection. The account page lets administrators restrict protocols and allow or block domains, according to SOAX's mobile page. That model is efficient when one set of credentials needs to reach many locations.

With a Coronium line, you get one device. The dashboard shows its host, HTTP and SOCKS5 ports, username and password, its carrier and region, and the controls for rotation and the timer. On lines that support them, you can change the password, set an allowlist of client addresses and download an OpenVPN profile; lines in stock today with OpenVPN are in Brazil, Georgia, Germany, Netherlands, Poland, Singapore, United Kingdom and United States. The same actions are available through REST API v3 with a token from Account, API Access, and through the hosted MCP server at https://api.coronium.io/mcp for AI agents.

Payment is by card, cryptocurrency or account balance in the dashboard. Up to 2 device replacements per rolling 24 hours are available if a device fails; a replacement comes with new credentials and may be on a different carrier.

Sessions and rotation

SOAX's mobile page describes keeping the same IP through multiple requests or rotating on every request, with rotation by request count, by time or on error, and sticky sessions that lock requests to a single node. Because exits are shared devices, a sticky session holds only while that device stays online.

A dedicated line works from the other end. The address stays where it is until you change it, or until the carrier hands the modem a different one on reconnect. You rotate it from the dashboard, through the API, with a private rotation link or on a timer, and the minimum interval is 60 seconds (Coronium API reference). Brazil lines rotate on request only.

For logged-in work that difference is the main reason to choose a line: nobody else's traffic moves your exit, and nothing rotates it unless you ask. For collection that wants a different exit every request, SOAX's model fits better, because a line gives one address at a time.

Targeting

SOAX lists country, region, city and ISP targeting on its entry plans, with ASN and ZIP targeting from the Scale plan. If your work needs results from many cities or postcodes, that breadth is hard to match with dedicated hardware.

Coronium lines are chosen by country and carrier, with the regions each carrier has in stock shown on the country pages. The carrier is the network sites actually see, so for app traffic and account work it is often the more useful choice; our ASN vs geo targeting guide explains why. The live list of countries and carriers is on the mobile proxy locations page.

Where SOAX fits better

SOAX is the better choice in several situations, and a fair comparison should say so.

• You need many countries or cities in one project, or ZIP and ASN targeting.
• Your job needs a different exit IP on most requests, or hundreds of exits at once.
• Your monthly traffic is small or irregular, and Sandbox top-ups cover it.
• You want residential and mobile traffic on one balance and one rate card.

There is also a middle path. If most of your work is broad sampling but a few accounts need a stable home, keep SOAX for the sampling and put those accounts on lines. The two do not conflict, and splitting by job is usually cheaper than forcing one product to do both. Review the split every month: as account work grows, more of the budget tends to move to lines, and as sampling grows, more moves to per-GB traffic.

A dedicated line is the better choice when one identity must stay stable for hours or days, when traffic runs high every day in a single country, or when you need control over exactly when the address changes. Compare current options on the mobile proxies overview.

Switching in practice

If you are moving part of a workload from SOAX to dedicated lines, change it in stages.

1. Pick the jobs that suffer from shared exits. Account sessions and app tests usually move first; broad collection can stay on per-GB traffic.
2. Buy the 24-hour plan on your target carrier. Run the real workflow for a day before committing to longer periods.
3. Change the connection format. SOAX encodes targeting and session options in the username. A Coronium line gives you a host, port, username and password per line for HTTP and SOCKS5, with no parameters to add.
4. Set rotation on purpose. Leave the timer off for account lines; set a timer or call the API between batches on collection lines.
5. Move account by account. Keep each account on one line and record which line it uses.

Resellers can automate the same steps with the REST API, and the open reseller kit shows a full integration. Endpoint details are in the OpenAPI specification, and live stock and prices are published at the public catalog endpoint.

How we checked

SOAX facts come only from SOAX's own pricing and mobile proxy pages, read on 30 October 2026; plans and rates can change, so check them at checkout. Coronium facts come from the published product facts, the API documentation and the live catalog when this page renders. Coronium sells a competing service. We did not run a speed or success-rate test of either service.

Frequently asked questions