Proxy Backconnect

A backconnect proxy presents one fixed gateway address to your client while, behind the scenes, routing each connection through a large pool of exit IPs. You connect to the single endpoint and the provider handles rotation for you, so you never manage individual addresses. It is the delivery mechanism most rotating proxy services use: one entry point, many exits. The design hides pool complexity behind a stable front door.

Your requests all go to the same gateway host and port; the gateway forwards each to a different exit IP from its pool according to a rotation policy — per request, per session or timed. This makes distributing traffic across many addresses effortless from the client's side, which suits large-scale scraping that must dodge per-IP rate limits. The downside is less direct control over which specific exit any request uses, and stateful flows need a session-sticky mode to stay on one address.

s4m exposes its authenticated proxies as direct endpoints — SOCKS5 on port 1080 and HTTP on port 3128 in a single region — rather than a rotating backconnect gateway. For work needing a stable, single exit you can add a dedicated IP; for lighter multi-IP needs you can cycle through the free public list in your own client. If you specifically need large-pool backconnect rotation, that is a different product shape than s4m's transparent datacenter model. See the proxy plans.