Proxies for multi-threaded software
Parsers, checkers and task schedulers are limited not by bandwidth but by the number of addresses: a target site starts returning errors after a few dozen requests from one IP. A proxy pool removes that ceiling — your software keeps running at the configured thread count while requests leave from different addresses.
From 650 ₽ a month for 50 threads.
Threads in the plan
Rotation · timed mode available
Both protocols
Both auth methods at once
Billed per thread, not per address
Rotating plans are measured in concurrent connections: Starter-1 gives 50 threads for 650 ₽ per month. How many addresses the pool cycles through in that time does not matter — you pay for concurrency, not for units. For multi-threaded software this beats buying addresses one by one: you don't have to guess in advance how many IPs your task list will consume.
What to configure in your software
One gateway address with a port and a login/password pair is enough — rotation happens on our side and your software never needs to know about it. The alternative is adding the machine's IP to the whitelist and working without a password, which suits server-side jobs and cron runs. Both authentication methods are active at the same time, so there is nothing to switch between.
Which software this works with
Anything that accepts an HTTP or SOCKS5 proxy with authentication: A-Parser, Key Collector, ZennoPoster, BrowserAutomationStudio, Netpeak Checker, Screaming Frog, XEvil, CapMonster, as well as your own scripts in Python, Node.js and Go. No plugin or integration is required — to the program this is an ordinary proxy server.
What people take for this
Three products. The difference is the address type and whether it changes: some jobs need a pool, others a single fixed IP.
- 10 different /29 networks
- Rotation: per-request or time-based
- Connections as you need
- HTTP, SOCKS5
- User/pass and IP — at once
- 10,000+ rotating IPs
- Rotation: per-request
- Connections as you need
- HTTP, SOCKS5
- User/pass and IP — at once
- 15,000+ static IPv4
- Dedicated stable IPs
- HTTP, HTTPS, SOCKS5
- User/pass and IP — at once
How to connect
Setup fits in one line: the program only needs a gateway host and port. Rotation happens on our side — the program never has to know about it.
- 1Pick a plan
The plan's thread count must be at least what the program is set to, or some connections will sit waiting for a free slot.
- 2Get the credentials
Gateway host, HTTP and SOCKS5 ports, login and password appear in the dashboard right after payment.
- 3Paste it into the program
One address instead of a list: any field that takes a normal proxy server with authentication will do.
Frequently asked questions
Short answers to what gets asked before ordering. Everything else goes to support, which answers around the clock.
How many threads should I take?
Match your software's own setting: the plan's thread count should be no lower than what the program is configured for. If the parser runs 100 threads, a 50-thread plan becomes the bottleneck and some connections will wait for a free slot. Starting at 50 and increasing once you hit the ceiling is reasonable.Will rotation break session-based work?
Not necessarily. Rotation can be left per-request or set to a timed interval — then the address is held for a fixed period and a sequence of requests leaves from one IP. For tasks where a chain of steps matters, use the second mode.Is there a traffic limit?
Rotating plans do not meter traffic — the only limit is the number of concurrent connections. On static datacenter addresses the traffic volume is part of the configuration and is chosen at order time, starting from 250 GB.IPv6 or IPv4 for software?
Technically your program sees no difference beyond the address format and the price: an IPv6 pool costs less at the same thread count. The difference appears on the target side — some resources do not accept IPv6 connections at all. If your target is IPv4-only, take an IPv4 plan.
Other use cases
- For parsing and scraping
- For marketplaces
- For antidetect browsers
- For captcha software
- For SEO and SERP checks
- Rotating IPv6 and IPv4
- IPv6 proxies
- Static datacenter IPv4
Covered in the blog
- ReferenceChrome proxy errors: what each code means, and how −111 differs from −130ERR_TUNNEL_CONNECTION_FAILED and ERR_PROXY_CONNECTION_FAILED sound alike but describe different stages. A table checked against the source, and what Chrome actually does when a proxy fails.Read
- SetupAutomating proxies over the API: whitelist, purchase and renewal from a scriptA PUT to the whitelist replaces the whole list rather than adding to it — that is how people lock themselves out. A walkthrough of our API: the key and its limits, updating an address from cron, purchase and renewal, error codes.Read
Pick a plan by thread count
Rotating IPv6 from 650 ₽ for 50 threads, IPv4 from 1375 ₽ for 100. Minimum balance top-up is 100 ₽.