A rotating residential proxy gives you a different real-home IP for every request (or every few minutes, with sticky sessions). To the target site each request looks like a different household visitor, which keeps per-IP request counts low - the single strongest signal that gets scrapers blocked. It is the default choice for crawling, price monitoring, ads verification and SERP work.
Rotation modes: round-robin vs sticky
| Mode | How it works | Use it for |
|---|---|---|
| Round-robin | New exit IP on every request | Crawling, SERP, price checks, monitoring |
| Sticky session | Same IP held 1-30 minutes via username parameter | Logins, carts, multi-step flows |
Rule of thumb: read-only collection rotates, anything with a session sticks. Login flows, carts, paginated results tied to a cookie and multi-step forms all need the same exit for the duration of the flow - switch to sticky for those requests and back to rotation after.
Pricing: pay per GB, tiers as you grow
| Order size | Unit price | Total | Best for |
|---|---|---|---|
| 100 GB | $1.20 / GB | $120 | First orders, target testing |
| 1,000 GB (1 TB) | $0.96 / GB | $960 | Steady production crawling |
| 5,000 GB (5 TB) | $0.72 / GB | $3,600 | Multi-market monitoring |
| 10,000 GB (10 TB) | $0.60 / GB | $6,000 | High-volume operations |
Datacenter traffic (for soft targets that do not need residential exits) stays at $1/GB with the same 100 GB minimum. Everything shares one balance in one console.
How much rotating traffic do you need?
Traffic is page weight times requests, so the honest answer comes from your own targets - but the arithmetic is predictable. A typical product page pulled as raw HTML is 200-600 KB; a search-results page 200-500 KB; a JSON API response often under 50 KB. At 400 KB per page, 1 GB covers roughly 2,500 pages, so the 100 GB entry tier is about 250,000 pages - enough to validate an entire workflow before you commit to a larger tier. Two things inflate the bill quietly: retries on blocked requests (each retry pays full freight) and headless browsers (10-50x the weight of a plain HTTP call). Fetch embedded JSON where it exists and keep the browser for targets that truly require it.
Getting started
- Create an account and top up - 100 GB ($120) is the smallest dynamic residential tier.
- Copy the endpoint from the console - HTTP or SOCKS5, and add your targeting and rotation preferences directly in the username: country, city, sticky duration.
- Run a smoke test against https://ipinfo.io/json from a few countries to confirm exits.
- Watch the hourly usage dashboard, tune concurrency per domain, and scale to a lower per-GB tier when your monthly volume justifies it.