Every product,
one price list.

Right tool for

• Retail and marketplace data at scale
• Search engine results across many locales
• Ad verification where the viewer must look local

Wrong tool for

• High-throughput bulk transfer — per-gigabyte pricing makes this expensive
• Workloads needing one unchanging IP for weeks; use ISP instead

Right tool for

• Accounts that must be reached from the same address every time
• Sneaker, ticketing and release workloads that need speed and trust together
• Long-lived sessions where rotation breaks the flow

Wrong tool for

• Wide-net crawling where you want a different IP each request; use Residential
• Very large IP counts in one small country — check availability first

Right tool for

• High-volume crawling of targets that tolerate datacenter ranges
• Internal tooling, uptime checks and synthetic monitoring
• Work that wants a stable address you can whitelist somewhere

Wrong tool for

• Major retail and social targets, which block datacenter ranges aggressively
• Anything requiring the request to look like a household connection

Right tool for

• Crawling catalogues and listing pages on a schedule
• Collection jobs too small to justify running a pool
• Teams with nobody to babysit rotation and retries

Wrong tool for

• Targets that answer with a challenge rather than a page — that is the Unblocker API
• Anything needing a specific address held across requests

Right tool for

• Pages that return an interstitial or a challenge instead of content
• Targets where a plain fetch succeeds only sometimes
• Work that would otherwise be a week of tuning by hand

Wrong tool for

• Targets that answer a plain fetch — you would be paying for retries nobody needs
• Anything needing a specific address held across requests