System-wide proxy
A transparent TUN routes the whole machine — browsers, automation, native apps. Choose how UDP is handled per session: block it, proxy it, or send it direct so voice and games still work without exposing your IP.
capabilities
PROXA is a Windows-native privacy layer: a system-wide proxy underneath every process, plus a per-profile fingerprint engine so each identity stands on its own.
A transparent TUN routes the whole machine — browsers, automation, native apps. Choose how UDP is handled per session: block it, proxy it, or send it direct so voice and games still work without exposing your IP.
Each profile gets its own canvas, WebGL, audio, font set, timezone, and hardware story — generated to stay consistent with your real host class, so a detector sees a believable machine instead of an obvious spoof.
WebRTC, DNS, IPv6 and raw-socket paths are sealed at the routing layer. An interface-scoped kill switch blocks anything bound to the physical NIC, so a process can't quietly bypass the tunnel.
Create hundreds of isolated browser profiles in bulk, drive them with recorded automations and a scheduler, and keep them organized — built for multi-account work at scale.
Profiles sync selectively and encrypted — cookies, storage and settings move with you, while large local caches stay put. Open the same identity on another machine and pick up where you left off.
Run a profile in antidetect mode to present a clean identity, antitrack mode to block trackers at the network layer, or both at once. The mode is set per profile, not globally.
Assign a dedicated residential exit to each profile, or route the whole device through one. Mix per-profile browser proxying with the system tunnel as the job requires.
A single bundled installer with the runtime, the tunnel engine, and the fingerprint hooks inside. Nothing to pip-install, no separate driver to babysit.
Sign in once; your plan and limits follow your account and your synced profiles. Log out and the app fully locks — no half-authenticated state.
We tried to deanonymize our own client with the proxy on. Here's what happened.
Read the leak test →