Choosing a product line
Billing unit, targeting granularity and fit for dynamic residential, premium residential, mobile, static residential, unlimited residential, datacenter, IPv6, mobile 4G/5G and more.
The lines don't differ by "which is better" — they differ by billing unit and whether the IP is fixed. Decide whether your workload is traffic-heavy or connection-heavy, and whether you need an IP that never changes. The rest follows.
At a glance
| Billing unit | Fixed IP | Targeting | Session options | |
|---|---|---|---|---|
| Dynamic residential | GB | No, sticky per session | Country / state / city / ASN | session + time |
| Premium residential | GB (separate balance) | No, sticky per session | Country / state / city / operating system | session + time |
| Mobile | GB (separate balance) | No, sticky per session | Country / state / city | session + time |
| Static residential | IP × 1–90 days, by type | Yes, for the lease | Country; Standard / Clean ISP add city and carrier | None; the IP is already fixed |
| Unlimited residential | Ports or account-wide bandwidth × validity period | No | Configurable exit country | Set by the plan |
| Datacenter | IP pool (100–15,000 IPs + data allowance) × 1/7/30 days | Yes, or rotate within the pool | IP count spread by country | None; fixed IPs or rotate within the pool |
| IPv6 | Per GB, or unlimited data by bandwidth | No, a new IP per request by default | Gateway region | Sticky sessions up to 24 hours |
| Mobile 4G/5G | Dedicated port × 1/7/15/30 days, unlimited data | Dedicated port; change the IP any time | Country / carrier / 4G or 5G | None |
| AI account IPs | IP × 30 days | Yes, for the lease | United States | None; the IP is already fixed |
| Use-case ISP | IP × 30 days | Yes, for the lease | Country, in pools per use case | None; the IP is already fixed |
Pick by workload shape
Scraping, price comparison, SERP collection → dynamic residential
Small payloads, many requests, frequent IP changes and fine-grained geography. Per-gigabyte pricing is cheapest here because you consume request count, not bandwidth.
You need to choose the exit device's operating system, or want traffic accounted apart from dynamic residential → premium residential
Also per gigabyte, with a separate balance that never expires. Any dynamic residential sub-account connects with type-premium; it targets down to the city and the exit device's operating system, but not ASN.
You need mobile carrier exits and only reach web pages and HTTPS APIs → mobile
Per gigabyte with a separate balance that never expires, connected with type-mobile. Only ports 80 and 443 are open, and payments, streaming and other categories are blocked; see Access restrictions.
Account warming, social media operations, "this account must always use this IP" → static residential
Target sites treat IP changes as a risk signal. Static residential gives you a fixed, dedicated residential IP for the lease, with unlimited traffic and no session expiry to think about. It comes as Standard, Clean and Native ISP, on terms from 1 to 90 days; see Static residential.
Claude, ChatGPT and other accounts you keep for a long time → AI account IPs
Clean, dedicated IPs on tier-1 US carriers (AT&T, RCN, Windstream and others), fixed for the lease, with optional SOCKS5 UDP. See AI account IPs.
Sneakers, ticketing, retail drops, social and other specific targets → Use-case ISP
Dedicated ISP IPs picked per use case and tuned for those target sites, for 30 days. See Use-case ISP.
You need a dedicated mobile carrier exit and don't want to meter long runs → Mobile 4G/5G
One dedicated real-carrier port per order: pick the country, carrier and 4G / 5G, change the IP any time, with unlimited data, priced by term. It is a different product from mobile, which is per GB on a shared pool. See Mobile 4G/5G.
Large downloads, video streams, sustained high bandwidth → unlimited residential
Priced by day/week/month and bandwidth tier, not metered by gigabyte. If your workload will move hundreds of gigabytes, per-GB pricing gets out of hand.
You don't care about residential attribution, only stability and speed → datacenter
A batch of dedicated datacenter IPs at once (100 to 15,000 per pool), with the best latency and the lowest cost per IP, but the ASN belongs to a hosting provider, which strict anti-bot systems detect more easily. Good for API calls, internal service egress, and scraping where residential attribution isn't required.
Your target supports IPv6 and you need a huge number of different IPs → IPv6
A huge pool of IPv6 addresses: a new IP on every request by default, or keep one for up to 24 hours, priced per GB or with unlimited data by bandwidth. Exits are IPv6 only, so the target must have an IPv6 (AAAA) address, and many smaller sites don't. See IPv6 proxies.
How the billing models actually differ
Dynamic residential balance: purchases accumulate into the account's traffic pool. In the current implementation there is no code-level automatic expiry or forfeiture — the balance does not zero out with time.
Dynamic residential quotes: a quote is valid for 5 minutes by default, shortened further if a promotion ends or the product is delisted sooner. An expired quote has to be re-requested.
Static residential lease: 1 / 7 / 30 days for Standard and Clean ISP, 7 / 30 / 90 days for Native ISP. IPs are reclaimed at expiry; renewal keeps the same IPs, and auto-renew is available.
Datacenter term: 1 / 7 / 30 days; smaller pools offer fewer terms. Renewing adds a term on top of the current end date and keeps the same IP pool; the data allowance resets and unused data does not carry over. Expired plans can't be renewed — you buy a new pool with different IPs. Datacenter IPs bought one by one before the pools launched can still be renewed, which extends the existing IP's expiry.
Unpaid orders: expire after 30 minutes by default and stock is returned. Stripe checkout links are kept for 30 days.
Targeting granularity is not equal
Dynamic residential, premium residential and mobile all target down to the city. Only dynamic residential targets an operator's ASN; dynamic and premium residential target the exit device's operating system:
USERNAME-country-US-state-California-city-Los%20Angeles
USERNAME-country-US-asn-7922
USERNAME-type-premium-country-US-state-California-city-Los%20Angeles-os-windows
Premium residential and mobile use their own location catalogues, which do not fully match dynamic residential; outside the US premium residential needs a city.
Static residential Standard and Clean ISP let you choose the country, city and carrier (ASN) at checkout; Native ISP and datacenter are purchased by country only (for datacenter, you spread the pool's IPs over countries). Either way you get specific IPs, and you cannot change their location per request.
Can you mix them
Yes, and it's common. One account can hold balances and resources across several lines, with each proxy sub-account bound to one product. A dynamic residential sub-account can also add type-premium or type-mobile to its username to use the premium residential or mobile balance per connection, with no extra sub-account. Typical combinations:
- Dynamic residential for discovery and scraping, then static residential for follow-up actions on a hit
- Datacenter for internal services and monitoring, residential for outbound scraping
For how to split and isolate traffic across sub-accounts, see Proxy sub-accounts.