Per-app routing
Pick an app by its real icon — no typing process names. Pick a proxy. Done.
macOS · Per-app routing
Send every app down
the path it belongs on.
Decide which apps connect directly and which use your proxy. ProxyRouter routes traffic at the macOS system layer, with no per-app setup — including real UDP and QUIC proxying.
Your rules, connection traces and traffic content stay on your Mac. ProxyRouter handles routing; you stay in control of every upstream.
What it does
A clear decision for every connection.
Real UDP / QUIC proxy
SOCKS5 UDP ASSOCIATE forwarding — something Proxifier simply can't do. QUIC gets three states: proxy, fall back to TCP, or direct.
Rule-trace explainer
Expand any connection to see exactly why it took that path. A dry-run tester tells you which rule matches — without sending a packet.
Auto network switching
Wi-Fi by SSID; wired by gateway MAC + subnet — so 'office cable' and 'home cable' are told apart. Bind a profile to a network and it switches back on its own.
CLI + MCP
proxyrouterctl on the command line, URL Scheme, App Intents — and a built-in MCP server so Claude and other LLMs manage your rules directly.
Safe defaults, built in
fake-IP DNS, loopback protection, localhost guards — the defaults you'd only get right after being burned are already configured.
Rule-trace explainer
Every routing decision comes with an answer.
Every live connection expands into the exact chain of rules it walked — matched, skipped, and why. The dry-run tester answers the same question before a single packet leaves your machine.
- Pure-function rule engine — the tester and the live path always agree.
- Same logic drives the UI, the CLI and MCP — behavior never drifts.
Chrome
→
edge.quic.example.com:443
SOCKS5 · JP
- rule 01app = Slackskip
- rule 02dst in cn-direct.listno match
- rule 03app = Chrome · proto = QUICmatch
- actionproxy → SOCKS5 · JP (UDP ASSOCIATE)
Dry-run · no packet sent
$ proxyrouterctl route add --app Chrome --proxy jp-socks
✓ rule 03 Chrome · QUIC → SOCKS5 · JP
$ proxyrouterctl test --app Chrome --host example.com
→ match rule 03 · proxy SOCKS5 · JP · no packet sent
# or just ask Claude, over MCP
→ "route Chrome's QUIC through the Japan node" doneCLI + MCP
Drive it from the terminal — or hand it to Claude.
proxyrouterctl ships with zero third-party dependencies. The built-in MCP server exposes the same automation surface the UI uses, so an LLM can read your connections and reshape your rules in plain language.
Honest comparison
Familiar per-app routing, with fewer blind spots.
| Capability | ProxyRouter | Proxifier |
|---|---|---|
| Per-app routing (real icons) | Yes | Process names |
| SOCKS5 UDP / QUIC proxy | Yes | No |
| Rule-trace explainer + dry run | Yes | No |
| Auto network-env switching | Wi-Fi + wired | Limited |
| CLI + MCP (LLM control) | Yes | No |
| fake-IP DNS + loop guards | Yes | Manual |
Good to know
The essentials, before you install.
Does ProxyRouter include proxy servers?
No. It is a traffic router, not a proxy service. Bring your own SOCKS5 or HTTP upstream.
Do I need to configure every app?
No. Choose the app and route in ProxyRouter; the target app does not need its own proxy settings.
Is my traffic sent to your servers?
No. Routing, rule evaluation and license checks happen locally. Traffic goes only to destinations you configure.
Which Macs are supported?
macOS 13 or later, on both Apple Silicon and Intel Macs.
Still unsure? Contact us or read the system requirements.
Pricing
Try it free for 3 days. Then own it your way.
Every plan is the full app — nothing is held back during the trial. When a trial or subscription ends, only proxying stops; your config is never touched.
Monthly
$0.99/ month
- All features
- Billed monthly
- Cancel anytime
Yearly
$7.99/ year
- All features
- About $0.67/month
- Updates and new macOS support
Lifetime
$19.99one-time
- All features forever
- All future updates included
- Move between your Macs
Every plan starts with the same 3-day full-feature trial — no card required. Payments are securely handled by Paddle.