Skip to main content

What is Proxy Hopper?

Proxy Hopper sits between your application and the internet. Configure your HTTP client to use it as a proxy, and Proxy Hopper handles picking an IP from your pool, retrying on failure, and automatically quarantining broken proxies.
Your app  ──────────────────►  Proxy Hopper  ──►  external proxy IP  ──►  target site
          HTTP proxy / CONNECT   (rotating)          (from your pool)

Key features

IP rotation

Each target maintains its own FIFO queue of proxy IPs. IPs are held off the pool between requests to respect rate limits.

Automatic quarantine

IPs that accumulate failures are quarantined for a configurable period, then released back into rotation automatically.

Three integration modes

HTTP proxy, HTTPS CONNECT tunnel, and URL-forwarding — all using the same rotation and retry logic.

Redis HA

In-memory backend for single-instance deployments. Redis backend for multi-instance HA with shared pool state.

Integration modes

ModeHow to useBest for
HTTP proxySet http_proxy=http://proxy-hopper:8080Any HTTP client with proxy support
CONNECT tunnelSet https_proxy=http://proxy-hopper:8080HTTPS via standard proxy settings
URL forwardingChange base URL to http://proxy-hopper:8080/https/api.example.comFull retry support for HTTPS — Proxy Hopper owns the request end-to-end
Why forwarding mode? CONNECT tunnels are opaque byte relays — Proxy Hopper cannot retry a mid-flight HTTPS failure. In forwarding mode, Proxy Hopper owns the full HTTPS request, enabling retries and IP rotation on 429 or 5xx responses.

Next steps

Quick start

Install, configure, and send your first request in minutes.

Config reference

Full reference for all configuration fields and environment variables.

Docker & Compose

Deploy with Docker or Docker Compose.

Kubernetes

Deploy on Kubernetes with Redis for HA.