Start With the Current Commercial Model#
See the dated Databay vs SOAX comparison for published residential prices, targeting, trial terms and billing differences. This article keeps the migration checklist for teams planning the switch.
A SOAX alternative should be compared with the SOAX plan available to the buyer now. A historical flat rate, an enterprise headline and a no-subscription account can imply very different customer commitments. A migration also has to recover the package and routing controls that the application actually uses.
Databay can be evaluated for shared rotating residential, mobile or datacenter traffic. Keep SOAX when its package model, geography mix or application behavior remains the better fit. This is a decision guide with a testable migration method, not a performance ranking.
| Reason for considering a change | First comparison | A reason to retain the current route |
|---|---|---|
| Irregular traffic and unused recurring credits | Applicable commitment, expiry and actual consumption | Current rollover and usage mix already fit demand |
| A costly mix of exit countries | Same country-by-country byte workload | Lower advertised rates apply to different geography or volume |
| Package administration is the main requirement | Ownership, limits, access and usage attribution | Candidate lacks a mandatory control |
| A different session failure policy is required | Identity continuity and fail-closed behavior | Candidate silently replaces a peer when the application must stop |
| A raw rotating proxy is sufficient | Same-product transport and actual output | Current provider passes all gates and migration adds no proven benefit |
Use the current Databay rate cards to select an offer and the workload calculator to estimate traffic requirements. An estimate is not an invoice or an executed network result.
Sources and Commercial Interest#
The Databay Research Team reviewed SOAX's pricing and billing FAQ, package management, authentication and residential reference on October 25, 2026.
Databay owns this publication and sells competing services. We did not create a SOAX account, accept private terms, buy credits, use a proxy, inspect private analytics or contact support. The guide contains no comparative latency, success, supply, session-continuity or support measurements. Public documentation describes configuration; a buyer's current contract and actual observed results remain separate evidence.
Normalize Credits, Geography and Bytes#
The reviewed SOAX page shows Builder at $200/month plus VAT with 200 included credits. Its tier-one traffic rate is $3 per gigabyte. The page's 100 GB US example totals $300 before VAT, including $100 in extra credits. Sandbox has no subscription fee or included credits. The FAQ says exit-country geo tiers determine rates, counts both transfer directions including retries, and defines GB as one billion bytes. SOAX pricing and billing FAQ
These values are a dated scenario, not a promise of a buyer's quote. The example applies to a tier-one US workload on the stated plan. Do not substitute a lower enterprise or other-country rate. Confirm the current country-tier mapping, available balance, renewal, rollover, top-up price and applicable tax before purchase.
| Comparable field | Required evidence | A misleading shortcut to reject |
|---|---|---|
| Product class | Residential or mobile selected explicitly | Combining the cheapest rates from different networks |
| Exit geography | Byte distribution by exit country | Using the customer's country or destination country as the exit tier |
| Commitment | Exact plan fee, included credits and usage window | Multiplying only an advertised GB rate |
| Additional usage | Top-up amount and applicable rate | Assuming all excess usage is already included |
| Units | Actual transferred bytes and provider definition | Treating decimal GB and binary GiB as equal |
| Validity | Renewal and unused-credit/package rules | Treating unused expiring allowance as consumed value |
| Final charge | Currency, tax and authorized eligible discounts | Comparing one tax-inclusive total with another pre-tax banner |
Normalize traffic with decimal GB = bytes / 1,000,000,000 and GiB = bytes / 1,073,741,824. Then use each provider's applicable package or credit calculation. Keep uncertain fields unresolved rather than filling them with a convenient assumption. Compare the total customer payment needed for the same workload, then measure cost per valid output if a pilot is authorized.
Recover the Package as an Access Boundary#
SOAX documents a package as a separately configured route with a package key, network permissions, traffic and connection controls, and an IP allowlist. It also documents a customer-wide ceiling across packages and a shared credit balance. Separate packages therefore do not establish separate purchased balances or remove account-wide limits. SOAX package management
This distinction prevents a common migration error: reproducing the hostname and credentials while losing the workload boundary that kept usage and access attributable.
| Package item | Requirement to recover | Replacement evidence |
|---|---|---|
| Owner and assigned users | Who may configure and use the route | Access test for authorized and unauthorized users |
| Package key | Which clients share a secret | Secret references and a tested rotation procedure |
| Allowed networks | Whether mobile or residential use is permitted | Explicit product selection and observed exit class |
| Traffic limit | Scope of the consumption stop | Boundary test and separately retained usage |
| RPS and concurrent limits | Queueing and rejection behavior | Client concurrency, status and retry observations |
| Customer ceiling | Shared bottleneck across workloads | Simultaneous workload test within authorized limits |
| Usage attribution | Which job consumed the traffic | Workload ID, provider meter and charge reconciliation |
SOAX's current authentication guide puts routing rules in the username and the package key in the password. It also describes IP authentication separately. A stored connection from an older tutorial may therefore be the wrong migration baseline; recover the current generated settings from the account. SOAX authentication
Do not copy package secrets into a public scorecard. Preserve the source configuration and keep the old route available. Use an independent candidate secret and a provider-specific adapter. Changing one shared credential without knowing its consumers can break workloads that were outside the pilot.
Session Rules Are an Application Contract#
SOAX's current residential reference distinguishes rotating access and sessions. It documents a sixty-second idle expiry, locks routing rules on the first request for a session, and returns a parameter-mismatch error when those rules change. It also documents explicit node binding that fails when the assigned node fails. These settings have different consequences from simply requesting another rotating exit. SOAX residential reference
Recover whether the application needs an exit to remain the same, whether it can recover after replacement, and whether an error is safer than continuing. A shopping, authentication or other stateful transaction must be tested under its permitted usage and actual identity rules. A fresh session label cannot migrate an IP, cookies or an account's trust state between networks.
For any candidate, test normal operation, idle resume, peer failure, changed targeting and restart. Record the observed exit sequence and how the application reacts. Reusing a label is a requested behavior; it is not evidence of permanent IP ownership or guaranteed peer uptime.
Where Databay Is a Candidate and an Adverse Fit#
Databay's four current offers are standard residential, Residential Flex, mobile and datacenter. All are shared rotating access. Standard residential supports one active location selector among country, state, city, ZIP, coordinates and ASN, subject to live eligible exits. The other products have narrower country/continent controls.
Test Databay when a supported shared rotating product, its current traffic package and the required available selector fit the workload. Do not assume that SOAX's stacked rules, package features or node-binding behavior transfer unchanged. Databay is an adverse fit for a permanent residential address, exclusive peers, guaranteed sticky continuity, unsupported filter combinations or an unverified administration requirement.
The two services' use of the word sandbox also needs care. SOAX's no-subscription commercial plan is described above. It does not imply free network traffic. A separately labelled API test environment is another contract and should never be interpreted as paid-network benchmark evidence. Check the selected product's usage restrictions and acceptable-use policy.
Pilot and Roll Back Without Losing the Original Boundary#
- Inventory a single workload. Record package purpose, consumers, product, country mix, rules, secret reference, account limits and usage window. Keep the source settings and route available.
- Declare gates before testing. Define valid output, observed network/geo requirements, permitted destinations, session behavior, limit enforcement, retries and customer-charge reconciliation. Set application-specific thresholds and record unresolved requirements.
- Build an independent candidate. Generate current Databay settings for the exact selected product. Do not translate a composite SOAX rule into several unsupported Databay filters. Preserve TLS verification and verify client DNS behavior.
- Run comparable authorized work. Use the same destination sample, country distribution, client version and concurrency conditions. Separate valid outputs from challenges, denials, wrong geography, transport errors and exhausted retries. Record bytes, charge and session behavior independently.
- Exercise isolation and recovery. Check that the candidate's usage cannot silently consume an unrelated workload's allowance and that a limit failure produces the expected application response. Retain evidence; do not mark an unexecuted boundary test as passed.
- Choose from actual results. Reject the candidate when any mandatory control, output, legal, price or identity gate fails. A correct price estimate or successful connection alone is insufficient.
To roll back, stop new candidate jobs, safely drain active work and restore the retained original route reference. Verify the control output and check for duplicate jobs caused by retries. Reconcile candidate consumption and revoke the unused candidate secret after recovery. Retire the original package only after rollback is tested and the application owner accepts the migration.
Publish an Auditable Decision#
Keep provider, product/plan, exit countries, current quote, source date, client version, configuration hash, sample size, valid outputs, failures, byte counts, charge and decision together. Label evidence documented, observed or unresolved. The guide provides the documentary baseline; no paid-network result is implied.
For a correction, use the support@databay.com with the article URL, affected statement, current official source and effective date. Redact credentials and personal data. A source update should change the affected claim and review date; it should not turn an unexecuted migration method into a customer success story.
