PROXY WORKBENCH

Open source · Runs on your machine

Find public proxies.
Verify the ones you use.

Collect from supported public sources or bring your own list. Check each proxy against the services you choose, understand the result, then export or connect through a rotating gateway and local API.

Download latest release Read the quick start
  • HTTP, HTTPS, SOCKS4 & SOCKS5
  • macOS, Windows, Linux & Docker
  • 12 interface languages
Tour of the Proxy Workbench interface, from scan setup to ranked results and proxy details
Interface tour with synthetic proxy data. The app opens in your browser and keeps its data locally.

A clear path to usable results

From a public list to a proxy that passes your checks.

You decide what a successful request means. Results keep the evidence behind each decision.

Choose the sources and targets

Use the supported source feeds or import your own lists. Add service URLs and set allowed responses, required text, or a response hash.

Run real checks

Make repeated requests through candidates, with a threshold for each target. Optional judge and denylist checks add anonymity and IP verdicts.

Inspect and use the results

See individual attempts, filter and rank the working set, then build files, client configs, a gateway pool, or a fresh local API snapshot.

The workspace

Every part of the workflow has a place.

Eight tabs connect discovery, verification, delivery, and maintenance in the current desktop interface.

Scan

Set service rules and check presets; start, stop, resume, or recheck while watching live progress.

Results

Separate fresh, expired, failed, and unknown results. Search, filter, inspect attempts, and build exports.

Rotating Gateway

Use one local HTTP or SOCKS5 endpoint for your verified proxies, with connection stats and client setup.

Mobile & Clients

Copy or download sing-box and Clash configs, or connect Telegram through the gateway.

Sources

Browse 150 catalog entries. Fresh installs select 106 supported feeds; you can add your own lists and manage their scope.

Pools & Schedules

Keep a chosen number of working proxies for a profile and schedule checks with time and budget limits.

API Keys

Create scoped keys for the control API, with permissions, limits, rotation, and an audit trail.

How it works

Follow the built-in guide, review diagnostics, and manage settings, backups, and local data.

Inside the interface

See the check. See the reason.

Current screens show ranking, source selection, gateway setup, pools, keys, and the evidence behind each check. All examples use synthetic documentation data.

Results screen with synthetic ranked proxies, status groups, filters, and export controls
Results · filter and export the verified set
Proxy details showing individual check attempts and their outcomes
Details · inspect why a proxy passed or failed
Sources screen with the public feed catalog and controls for custom lists
Sources · choose feeds and bring your own lists
Rotating Gateway screen with connection status and client setup options
Gateway · connect clients through one local endpoint
Pools and Schedules screen showing pool configuration and a scheduled check
Pools & Schedules · keep a working set fresh
API Keys screen with scoped permissions and key management
API Keys · control access to automation

The pictured addresses come from reserved documentation ranges (RFC 5737); they are examples, not usable public proxies. Availability of real public proxies and feeds changes over time.

One checked set, several ways to use it

Move from results to your tools.

Use an export when you need a file, the gateway when an app needs one proxy address, or the API when your code needs current results.

  • Exports: TXT, CSV, JSON, PAC, Clash / Mihomo, sing-box, and protocol lists.
  • Gateway: HTTP and SOCKS5 at 127.0.0.1:8899 while it is running.
  • Read-only API: /random, /proxies, /status, /pac, and /clash.

Get started

Pick the way you want to run it.

Desktop builds open the local browser interface. The Python package works across platforms; Docker runs the checker and services without the browser GUI.

Python 3.11+

Linux & other systems

Install with pipx or run from a source checkout; the command opens the local interface.

Read install steps ↗
Server & NAS

Docker

Use the bundled Compose setup for the checker, API, and rotating gateway.

Read Docker steps ↗

Desktop installers are currently unsigned; macOS or Windows may ask you to confirm the first launch. Published release checksums let you verify a download.

For scripts and services

Take a working proxy with one request.

The read-only API serves the most recent export on your computer. The separate /v1 control API uses scoped keys for jobs, results, and administration.

Local by default

While the GUI is open, the read-only endpoint listens on 127.0.0.1:8765. Filter by protocol, country, latency, or anonymity. A network-facing deployment requires a token.

Explore the API documentation → 
curl "http://127.0.0.1:8765/random?protocol=socks5&country=DE&format=txt"

Control and clarity

Know what was measured.

Checks you define

Set target URLs, response rules, attempts, and success thresholds. A reachable proxy is not automatically a match for your service.

Evidence you can inspect

View per-attempt outcomes, latency, quality, and optional anonymity or DNSBL verdicts before you export.

Data kept local

The GUI runs on loopback, with no account or telemetry. Public proxies can still see your traffic, so avoid sending secrets through them.