Skip to main content

​
What is Proxy Hopper?

Proxy Hopper sits between your application and the internet. When your application needs to call a third-party API, it sends the request to Proxy Hopper instead. Proxy Hopper picks an IP from your pool, makes the HTTPS request on your behalf, and returns the response — retrying on failure by rotating to a different IP and automatically quarantining broken proxies along the way. 
Your app ─── X-Proxy-Hopper-Target: https://api.example.com ──► Proxy Hopper ──► proxy IP ──► api.example.com
Because Proxy Hopper owns the full HTTPS connection, it can retry on 429 or 5xx responses using a fresh IP without your application ever knowing a failure occurred.

​
When to use it

Proxy Hopper is useful when your application:
  • Makes outbound API requests at scale and hits rate limits per IP
  • Needs to rotate through a pool of IPs to avoid blocks
  • Requires automatic retry and failure recovery without building it yourself
  • Needs per-API rate limit policies without coupling them to your application code

​
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.

Client identity

Each (IP, target) pair can carry a persistent browser fingerprint and cookie jar that rotates automatically on quarantine or 429.

Per-request control

Override retries or attach a metrics tag on individual requests using X-Proxy-Hopper-* headers — no config changes required.

Redis HA

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

​
Next steps

Quick start

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

Targets

Understand how targets work — the core routing concept.

Docker deployment

Deploy with Docker or Docker Compose.

Kubernetes

Deploy on Kubernetes with the official Helm chart.