Every process, its own IP.
Zero leaks.
WhaleProxy routes each app's traffic through its own proxy deep in the system, invisible to the app. Every account, emulator, and window gets a distinct exit IP — DNS-leak-proof, fail-closed, with nothing to configure inside the app.
Windows 7/10/11 · 64-bit • SOCKS5 & HTTP • Vietnamese + English
What you use every day
The six things that matter most for running many accounts — click to see the real UI of each.
# reroute cả loạt acc — một lần gọi
POST /v1/reroute
{ "match":{"nickname":"Acc 3"}, "proxy":"jp-2" }
→ 200 · rerouted 1 · 12 flows moved
# kiểm proxy → IP thoát + độ trễ
$ whaleproxy proxies test --allDrop 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).
Match by name, path, MD5, or folder. One click adds a rule for LDPlayer, Nox, BlueStacks, MuMu, MEmu — with the process name pre-filled.
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.
Name it “Sales acc” and pin it to lock that process to one proxy — kept across relaunches.
Shrink to an always-on-top widget — watch the whole fleet, its IPs and throughput while you work on something else.
Drive it by script: add/test proxies, edit rules, reroute a whole batch of accounts — via the local REST API or CLI.
One system proxy isn't enough to run many accounts
Two windows sharing one IP — or a single DNS query slipping to your ISP — is all it takes to link accounts and get them mass-banned. Configuring a proxy inside every app is impossible at scale, and the app can still bypass it.
One IP per account
Decisions are per-PID: two Chrome windows or two emulators can exit from two different IPs at the same time.
Never leak the 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.
Three steps and you're live
First-run setup
On first run WhaleProxy sets itself up in seconds. No separate installer, and it cleans itself up on exit.
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.
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.
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 accounts.
Read the docs# Đổ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 acc emulator, theo nickname — một lần gọi
POST /v1/reroute
{ "match": {"nickname":"Acc 3"}, "proxy":"jp-2" }One machine, many IPs — assigned live, fail-closed.
Download WhaleProxy for Windows 7/10/11 and route your first account in minutes.