Pick a proxy by the job it has to do
Everyday residential
Location-aware browsing
Advanced identity
Priority pools and ASN control
What teams run on Ludax
Collect
Gather public data at volume
Verify
Confirm what each market sees
Understand
Turn signals into decisions
Every workload fails for a different reason — geography, address reputation, TLS fingerprint, or raw throughput cost. This hub names the constraint, points you at one of the four Ludax products, and hands you a starting configuration you can run today.
ONE GATEWAY · FIVE PRODUCTS · ROUTING SET PER REQUEST IN THE PASSWORD FIELD
Three questions. We name one product, explain the reasoning, and give you a configuration to start from.
Six worked guides, each with the blocker it addresses and the configuration it starts from. Filter by the constraint you are up against.
SHOWING 6 OF 6 GUIDES
-country-us-country-de-city-berlin-session-a1-time-10-country-fr-country-jp-asn-2516These do not have a dedicated guide yet. Each links to the product page or the closest existing guide.
The same six workloads against the current portfolio. Alternatives are the sensible second choice, not a fallback for a failed run.
| WORKLOAD | PRIMARY | ALTERNATIVE | WHY | STARTING CONFIGURATION |
|---|---|---|---|---|
| Web Scraping | Residential | Residential Premium | Geography is the constraint; rate limiting is solved by rotating addresses, not by a better pool. | Rotate per request · -country-us |
| SEO Monitoring | Residential | Residential Premium | Results are localised, so city targeting matters more than pool screening — step up only if results degrade. | Rotate per request · -country-de-city-berlin |
| Ad Verification | Residential TLS | Residential Premium TLS | Delivery decisions read the handshake, so the TLS profile must match the user agent you send. | Sticky 10 min · -session-a1-time-10 |
| Price Monitoring | Residential Premium TLS | Residential TLS | Currency and locale are session-bound and repeat visits are scored, so pin both the exit and the handshake. | Sticky 10 min per market · -country-fr |
| Market Research | Residential Premium | Residential | Screened addresses see the catalogue a normal visitor sees; ASN targeting keeps the sample consistent. | Rotate per request · -country-jp-asn-2516 |
| AI & Data Pipelines | Residential | Residential TLS | Throughput-bound work on tolerant sources is cheapest on the standard pool, where the per-GB rate bottoms out at 1 TB. | Rotate per request · |
-country-us-country-de-city-berlin-session-a1-time-10-country-fr-country-jp-asn-2516-pool-wwFull specifications and pricing for all five products are on the comparison page.
Work down the list and stop at the first line that describes your situation. Paying for a capability you do not need is the most common mistake.
Geography is the only constraint — you need the page as a country or city sees it.
Residential FROM $0.49 / GB
The target inspects the TLS handshake and your client signature has to stay consistent.
Residential TLS FROM $0.74 / GB
You need a cleaner screened pool, priority routing and ASN targeting.
Residential Premium FROM $1.69 / GB
You need both the screened pool and a pinned browser handshake.
Residential Premium TLS FROM $2.54 / GB
Buy the smallest package that fits the product you picked and run a few hundred requests. Residential has the lowest entry at $0.99 for 1 GB, and the lowest rate per gigabyte at $0.49 / GB on the 1 TB package.
Log status codes, response shape, the locale you actually got, session lifetime and retry rate. A rising retry rate is the signal to change product — not to raise concurrency.
Move up the volume tiers once the configuration is stable. One wallet balance pays for plans on any of the four residential products; each plan is valid for 30 days from activation.
If two products in a row behave the same way, the constraint is probably not the one you assumed. Support can look at the request pattern with you before you spend more.
Every parameter below is documented in the reference. Credentials are placeholders — substitute your own.
gw.ludaxproxy.com:9999
resi-user_a1f9c2-AE-chrome145-country-de-city-berlin:yourpassRotating per request. No session token, so every query leaves from a different Berlin exit.
EXAMPLE DATA — OBSERVE AND LOG
gw.ludaxproxy.com:9999
resi-user_a1f9c2-AE-chrome145-country-us-session-a1-time-10:yourpassSticky for ten minutes with a pinned Chrome 145 handshake, so the creative and its landing page are observed by one consistent client.
EXAMPLE DATA — OBSERVE AND LOG
gw.ludaxproxy.com:9999
resi-user_a1f9c2-AE-chrome145-country-fr-session-fr7-time-10:yourpassA screened French exit held for the length of one market pass, with the handshake pinned so currency and locale stay bound to the session.
EXAMPLE DATA — OBSERVE AND LOG
gw.ludaxproxy.com:9999
resi-user_a1f9c2-AE-chrome145:yourpassWorldwide rotation per request on the standard pool — the lowest per-GB rate, which is what bandwidth-heavy ingestion is priced on.
EXAMPLE DATA — OBSERVE AND LOG
Everything on this page assumes you are collecting public data, verifying your own advertising, testing your own builds, or operating accounts and systems you are authorized to operate. That covers the overwhelming majority of proxy work, and it is the work we support.
Outside that line the answer is simple: credential stuffing, account takeover, unauthorized access, payment or platform-enforcement circumvention and abusive automation are prohibited, and accounts are terminated without refund. Rate-respecting, permitted, attributable traffic is what keeps the network healthy for everyone on it.
Start from your blocker. If geography is the only constraint, standard Residential is enough. If the target inspects the TLS handshake, use Residential TLS. If the target scores IP reputation, use Residential Premium for the screened pool and ASN targeting. If you need both a screened address and a pinned browser handshake, use Residential Premium TLS. If the target is tolerant and the job is bandwidth-heavy, standard Residential at the 1 TB rate is the cheapest per unit of throughput.
They solve different problems. Premium changes which IP address you exit from: a screened pool with priority routing and ASN targeting. TLS changes how your client looks on the wire: a captured browser handshake pinned to the profile you request. Residential Premium TLS combines both.
Yes. Residential, Residential TLS, Residential Premium and Residential Premium TLS all draw from your prepaid balance, metered per request, so one account can cover every workload on this page.
Rotate per request when each request is independent, such as list pages or search results. Use a sticky session when the workflow has state to preserve, such as a cart, a locale selection or a multi-step page flow. Sticky sessions run 1 to 1000 minutes and are set with a session token in the password field.
Residential and Residential TLS support country and city targeting. Residential Premium and Residential Premium TLS add ASN targeting. The TLS products additionally accept a browser profile parameter.
Every product is metered by traffic through the gateway, counted per request, and drawn from a prepaid plan that is valid for 30 days from activation.
Anything in the acceptable use policy: credential stuffing, account takeover, unauthorized access, payment or platform-enforcement circumvention, and abusive automation. Accounts are terminated without refund for those.
More answers in the full FAQ.