Backconnect proxy

A backconnect proxy gives you one fixed hostname and port to connect to, and behind that single entry point the provider forwards your traffic through a changing set of IP addresses. You configure the gateway once and never touch the individual IPs, they change underneath you.

Why providers sell it this way

It makes a pool of thousands of addresses usable. Instead of maintaining a list that goes stale, your tool points at one endpoint forever and the provider handles which IP is live. It's the standard packaging for large residential pools, and it's where most rotating proxy products live.

Why it matters when you buy proxies

Convenience costs you control. You don't choose which address you get, you can't inspect its history, and holding one address for a long stretch depends on the provider's sticky session settings rather than on you. If a run breaks, you often can't tell whether the cause was your tooling or an address the pool handed you.

The alternative

A dedicated device is the other model: one known IP that's yours for the term, which you change on demand or on a schedule. It's more to manage and it costs more per address, but you always know what address you're on and what it has been used for, see dedicated IP.

A concrete example

Scraping a thousand product pages suits a backconnect gateway: point the scraper at one endpoint, let the pool spread the requests, and never think about addresses again. Running one account that has to be recognized as the same person every week doesn't, because the address is chosen for you and can be handed to somebody else the moment you stop using it.