A rotating HTTPS proxy server that routes outbound requests through a pool of external proxy IP addresses — with automatic retries, failure tracking, and IP quarantine.

Get started → GitHub Releases

●Open Source ●Self Hostable ●Docker Ready ●No cloud required

The problem

When your application needs to make outbound HTTP requests at scale — scraping, API polling, data collection — you run into rate limits, IP blocks, and connection failures. Managing a pool of proxy IPs manually means writing retry logic, tracking which IPs are healthy, rotating through them fairly, and handling failures gracefully. Every project reinvents this wheel.

Proxy Hopper solves it once, as a standalone service.

How it works

Define your external proxy IPs — grouped by provider with credentials and region tags. Set targets as URL regex patterns, each with its own pool, rate limit, and retry policy. Add one header to your HTTP requests: X-Proxy-Hopper-Target set to the real destination. No changes to your application logic. IP rotation, rate limiting between requests, automatic quarantine of failing IPs, retries on failure, and health probing in the background.

Key features

Each target maintains its own FIFO queue. IPs are held off the pool between requests to respect rate limits. IPs that accumulate failures are quarantined automatically and released back into rotation after a configurable timeout. Different targets can have different rate limits, retry counts, and quarantine thresholds — match the policy to the API. Proxy Hopper owns the HTTPS connection end-to-end, so it can retry any failed request on a different IP — including mid-flight 429s and 5xx errors. In-memory backend for single-instance deployments. Redis backend for multi-instance HA with shared pool state. Full observability — request rates, retry counts, queue depth, quarantine events, and per-IP probe status.

Get started

```yaml theme={} # config.yaml targets: - name: general regex: '.*' ipList: - "10.0.0.1:3128" - "10.0.0.2:3128" minRequestInterval: 1s numRetries: 3 ``` ```bash theme={} docker run -v $(pwd)/config.yaml:/etc/proxy-hopper/config.yaml \ -p 8080:8080 \ ghcr.io/cams-data/proxy-hopper:latest ``` ```python theme={} import requests session = requests.Session() session.headers["X-Proxy-Hopper-Target"] = "https://api.example.com" resp = session.get("http://localhost:8080/v1/endpoint") ``` Step-by-step guide with providers, pools, and a first proxied request. Pre-built multi-arch images for amd64 and arm64.

Deployment options

In-memory backend. Zero external dependencies. Good for development and single-host deployments. Redis backend. Survives restarts. Scale to multiple replicas sharing a single IP pool. Official Helm chart — Deployment, HPA, Redis subchart, ServiceMonitor. Scales automatically with traffic.

Free and open source. Forever.

Proxy Hopper is MIT licensed and built for self-hosting. No SaaS, no usage fees, no data leaving your infrastructure. Run it on a single container or scale it across a Kubernetes cluster — you own the deployment entirely.

Contributions, bug reports, and feature requests are welcome on GitHub.

```bash theme={} # Memory backend (default) docker pull ghcr.io/cams-data/proxy-hopper:latest # Redis backend docker pull ghcr.io/cams-data/proxy-hopper:latest-redis ```