John Sabo
← All work

Self-hosted rotating proxy infrastructure

Proxy Infrastructure Platform Running service

internal service

A rotating proxy server I run myself, fed by a collection arm that has harvested 721,000 proxies from 2,631 documented sources.

What it is

Scraping and automation need connections that do not all come from one address. This platform finds open proxies across the web, validates them and serves them behind one local endpoint with routing that keeps each target on a stable exit.

It started as a tool for my own pipelines and became infrastructure: health checking, TLS interception detection, provider auditing and an operations scoreboard for 2,631 sources of varying quality.

The architecture: collection, validation, the pool and the rotating server
The architecture: collection, validation, the pool and the rotating server
The architecture: collection, validation, the pool and the rotating server

Under the hood

Why build it

Rented proxy services charge per request and rate-limit exactly when you need volume. The open proxy world is enormous but mostly junk. The platform is the filter between those two facts: harvest everything, prove what works and serve only what survives.

721K
proxies harvested
2,631
sources documented
11
protocol checks

Stack

Python asyncio Redis aiohttp Docker systemd

Working on something like this?

One sentence about the problem is enough.

john@johnsabo.org