Choosing a product

The short version

Residential is the default. It works on targets the other two cannot reach, and it is the only product with full targeting and the full protocol set.

Reach for Rotating ISP or Rotating DC when the target puts up no real defense and you are moving enough volume that price per gigabyte is the deciding factor.

Compared

	Residential	Rotating ISP	Rotating DC
Works on defended targets	Yes	Sometimes	Rarely
Looks like a home connection	Yes	Yes	No
Country targeting	Yes	Yes	Yes
State, city, ZIP, ASN	Yes	No	No
Device OS targeting	Yes	No	No
SOCKS5 and UDP protocols	Yes	No	No
Speed	Slowest	Fast	Fastest
Cost per GB	Highest	Middle	Lowest

Full breakdown: Feature availability.

Start with Residential

If you do not already know how a target behaves, start here. A Residential exit looks like a person on a home connection, which is the only description that holds up against a target actively checking.

You can also narrow to a state, city, ZIP code or carrier, and reach it over SOCKS5, HTTP/3 or STUN. None of that is available anywhere else.

When ISP or DC makes sense

Undefended targets at high volume. Public APIs, your own infrastructure, sites with no bot protection at all. If Residential works and the bill is the only complaint, testing a cheaper product is reasonable.

Test before you switch. A product that blocks on 30% of requests is not cheaper, because you pay for the failures and the retries too.

When the IP is not the problem

If you are blocked on Residential, more rotation rarely fixes it. Modern targets read browser fingerprints, JavaScript execution and session consistency, and an authentic IP does not make the rest of the session believable.

Residential Proxies vs Browser Infrastructure covers what else is being checked.

When to use no proxy at all

If what you want is the page content rather than the connection, the Scraping API does proxy selection, browser rendering and retries for you. You send a URL and get HTML back.