Per-process proxy · Windows

Every process, its own IP.
Protect your IP.

A dedicated proxy per app — WhaleProxy separates traffic at the source, with no in-app configuration. Every app, process and window gets its own exit IP — DNS-leak-proof and fail-closed.

Windows 10/11 · 64-bit  •  SOCKS5 & HTTP  •  Multilingual

Actual app
Core features

What you use every day

The six things that matter most when running many apps — click to see the real UI of each.

Auto-assign
Round-robinQuota 2/proxy
POOLP1P2P3P4
🌐chrome #1→P1
🌐chrome #2→P2
🟩NoxPlayer→P3
🟨LDPlayer→P4
🌐chrome #3→P1
api · cli
# reroute cả loạt tiến trình — một lần gọi
POST /v1/reroute
{ "match":{"nickname":"App 3"}, "proxy":"jp-2" }
→ 200 · rerouted 1 · 12 flows moved

# kiểm proxy → IP thoát + độ trễ
$ whaleproxy proxies test --all

Drop in your whole proxy list — each process gets its own IP: round-robin spreads evenly, or quota caps N processes per proxy (overflow is blocked).

Round-robinQuota N/proxy

Match by name, path, MD5, or folder. One click adds a rule for LDPlayer, Nox, BlueStacks, MuMu, MEmu — with the process name pre-filled.

NameFull pathMD5FolderEmulators

Change a running process's proxy. Or send it direct (use the machine's own IP), or block it — with latency and the flows that will close shown.

ProxyDirectBlock

Name it “Work app” and pin it to lock that process to one proxy — kept across relaunches.

NicknamePin

Shrink to an always-on-top widget — watch the whole fleet, its IPs and throughput while you work on something else.

Always on top

Drive it by script: add/test proxies, edit rules, reroute a whole batch of processes — via the local REST API or CLI.

REST :8091CLI
TCP + UDPCatches TCP & UDP system-wide
5emulators detected per instance
SOCKS5·HTTP+ localnet (multi-NIC)
Fail-closeddead proxy = block, never leak
Why WhaleProxy

A separate proxy for each app — not one proxy for the whole PC

Two windows sharing one IP — or a single DNS query slipping to your ISP — is enough to expose your identity and real IP. Configuring a proxy inside every app is tedious and error-prone, and many apps don't support it at all.

Every app, its own IP

Decisions are per-PID: two Chrome windows or two emulators can exit from two different IPs at the same time.

Protects your real IP

Multi-layer DNS-leak prevention and a kill switch. When a proxy dies, traffic is blocked — never silently sent out on your real IP.

Never touches the app

Traffic is captured deep in the system. No SDK, no in-app proxy — the app can't bypass it, not even child processes.

How it works

Three steps and you're live

01

First-run setup

On first run WhaleProxy sets itself up in seconds. No separate installer, and it cleans itself up on exit.

02

Assign proxies per process

Set rules by name/path/MD5/emulator, or let it auto-spread. Child processes inherit the same IP as their parent.

03

Fail-closed — no leaks

If a proxy dies, the pool empties, or the license fails, the app is blocked instantly instead of leaking your real IP.

Signature feature

Change a running process's proxy — no restart

Other per-process proxifiers make you close and relaunch the app to change its IP. WhaleProxy moves a live PID to a different proxy instantly — one command, or one API call for a whole batch of processes.

Read the docs
terminal
# Đổi proxy của Chrome đang chạy sang line jp-2
$ whaleproxy reroute --name chrome.exe --to jp-2
✓ rerouted 1 process · 12 flows moved

# Cả loạt tiến trình, theo nickname — một lần gọi
POST /v1/reroute
{ "match": {"nickname":"App 3"}, "proxy":"jp-2" }
Ready to run

One machine, many IPs — assigned live, fail-closed.

Download WhaleProxy for Windows 10/11 — set up in minutes, each app routes through the right IP.