BetaEarly release for macOS 14 and later

Every app gets
its own route

Routekeeper sends the apps you choose through your proxy server and leaves the rest alone. And it makes sure nothing leaks: if the proxy goes down, traffic won’t go direct, and anything that slips past shows up.

Beta · macOS 14 Sonoma or later · your own SOCKS5, HTTP or HTTPS proxy · no accounts

Apps

try switching a route
No leaks when the proxy goes down See everything that slipped past Apps known by signature, not name No accounts, no telemetry
Routekeeper icon: a brass lantern with a railway switch on its glass
Why the name

The keeper of the routes

Old railway junctions had one person nothing worked without. They stood at the fork, knew every route and threw the switches: this train to the right, that one to the left, the suspicious one onto a siding.

And at night they walked the tracks with a lantern, looking for anything that had slipped through.

Routekeeper does the same for your Mac.

  • The switches are your rules: which app takes which route.
  • The lantern is the monitor and leak detector: anything that went off its route.
How it works

From app to website, and not a step off the route

No need to push everything through a VPN. Pick where each app goes, and let the rest work as usual.

No accounts and no Routekeeper servers. Traffic goes only along the routes you set, and nowhere else.

Add a proxy

SOCKS5, HTTP or HTTPS, with or without a password. Add several: work, home, another country. If one goes down, move your apps to another with one click from the menu bar.

Set the routes

GitHub via Amsterdam, Safari direct, that pushy updater to a dead end. One click per app.

The keeper keeps watch

The monitor shows every connection, and the leak detector flags anything that strayed from its route.

Features

As precise as a switchman at the junction

A firewall and a router in one window. No config files in the terminal, no noise.

Rules by destination

A wildcard domain, an IP, a subnet or a port. One route per app, plus exceptions where you need them.

G*.github.comproxy
S*.corp.exampleoffice
›_10.0.0.0/8direct
Aany addressdead end

Asks before letting anything out

An unknown connection waits for your answer, and the answer becomes a rule: just once, while the app runs, or forever.

Live connection monitor

App, destination, matching rule, route and traffic. Turn any odd-looking line into a rule with one click.

Leak detector

Catches anything that went around the proxy, including DNS queries to your ISP.

Zoom went around the proxy52.84.12.7:443 GitHub Safari DNS sent to your ISPChrome · example.org Slack

By signature, not by name

A renamed copy will not inherit someone else’s route.

GitHub Desktop.app✓ signed
GitHub Desktop copy✕ mismatch
+ helperssame route

Any proxy, even for stubborn apps

Works with apps that have no proxy settings of their own: command-line tools, Electron apps, messengers. UDP and QUIC are closed for them, so traffic can’t slip past the proxy.

SOCKS5HTTP CONNECTHTTPSusername & passwordcurl · git · node
For developers

AI assistants and the terminal, through your server

Routekeeper can send just ChatGPT, Claude, Cursor and Copilot through your proxy and leave everything else direct. No HTTP_PROXY, no VPN for the whole Mac.

Desktop AI apps

ChatGPT, Claude, Codex and other Electron apps go through the proxy together with all their helper processes.

A terminal without env vars

A rule for Terminal or iTerm with its child processes covers curl, git, npm, pip and brew, even when they know nothing about proxies.

The editor and its extensions

A rule for VS Code or Cursor applies to extensions too: Copilot and other assistants run inside the editor’s processes.

Only the addresses you need

You don’t have to route the whole app: send just the API, say *.openai.com, through the proxy and keep the rest direct.

Modes

And when there’s no rule?

Then the mode decides. Start gentle and tighten things up whenever you like.

Privacy

Traffic goes only where you told it to

No servers of ours

Routekeeper sends nothing to its developer. No analytics, no accounts.

Passwords under lock

Proxies and passwords live in a config only root can read. Even the app’s own window can’t see them.

Names resolved by the proxy

When the hostname is known, the proxy server resolves it, not your ISP’s DNS.

Built the Apple way

A system network extension with no kernel extensions. macOS itself asks for your permission.

What Routekeeper sees and what it connects to on its own — in the privacy policy.

What you need

Set your first route in five minutes

On first launch Routekeeper walks you through it: installs the extension, asks macOS for permission and helps you add a proxy.

  • A Mac with macOS 14 Sonoma or laterRoutekeeper uses Apple’s system network extensions, no kernel extensions.
  • Three permissions on first launchTurn on the network extension in System Settings (General → Login Items & Extensions on macOS 15 and later, Privacy & Security on macOS 14), then click Allow in two macOS prompts: network content filtering and the proxy configuration. Routekeeper walks you through it, and the quick start shows every step.
  • Your own proxy serverSOCKS5, HTTP CONNECT or HTTPS, with or without a password. Only for proxy routes: the firewall needs no server.
  • That’s itNo account, no subscription to someone else’s servers, no second client running alongside.
FAQ

Frequently asked questions

How is this different from a VPN?

A VPN wraps your whole Mac in one tunnel, and then your bank or local services see a foreign address and may turn you away. Routekeeper decides per app and per destination: your work messenger through your server, your bank and Zoom direct, the pushy updater nowhere. Everything else works as if Routekeeper weren’t there.

I use VLESS or Shadowsocks. Will it work?

Not directly: Routekeeper talks to the server over SOCKS5, HTTP CONNECT or HTTPS. But a VLESS or Shadowsocks client (sing-box, Xray, Clash and others) usually opens a local SOCKS5 port on your Mac, such as 127.0.0.1:1080. Add it to Routekeeper as a proxy: the client handles the protocol to the server, and Routekeeper decides which apps go there and makes sure nothing leaks. Turn off the client’s system proxy and TUN mode so only one of them manages routes. More.

How is it different from Proxifier?

Proxifier also sends apps through a proxy by rules. Routekeeper adds a firewall with an ask window, recognizes apps by developer signature rather than file name, and shows leaks: DNS to your ISP, UDP and anything that went around the proxy. Proxy chains, like Proxifier has, aren’t there yet.

And from Clash Verge, Hiddify and similar clients?

They speak VLESS, Shadowsocks, Trojan and other protocols to the server themselves and handle subscriptions. Per-app rules, where they exist, are written in a config by process name. In Routekeeper you give an app its route with a click, the app is recognized by signature together with its helper processes, and the monitor and leak detector show what went where. Fewer protocols, but the two don’t get in each other’s way: you can run Routekeeper on top of such a client, as in the answer above.

How is it different from Little Snitch or LuLu?

They are firewalls: they answer “allow or not”. Routekeeper also answers “where to”: one rule can send an app through a specific proxy. Firewall, router and monitor in one window.

Do I need my own server?

For proxy routes, yes: Routekeeper doesn’t sell proxies and runs no servers. Any SOCKS5, HTTP or HTTPS proxy will do: a VPS abroad with an HTTPS proxy (Caddy with forwardproxy, for example), a work proxy, one you pay for, or the local port of a VLESS client. If you only need the firewall, you need no server at all. To set up your own HTTPS proxy on a VPS, follow the 15-minute guide.

Can I route an app through Tor?

Yes. While it’s running, Tor Browser opens a local SOCKS5 port, 127.0.0.1:9150; the tor service from Homebrew uses 127.0.0.1:9050. Add it to Routekeeper as a SOCKS5 proxy, and the apps you choose will go through Tor, with Tor resolving site names. Keep in mind that Tor is much slower than a regular proxy, and many sites greet its addresses with a CAPTCHA.

How do I check that nothing leaks?

The menu bar shows the external IP your apps use through the proxy. The monitor shows every connection and its route, and the Leaks section flags what went past the proxy for apps routed entirely through it: DNS queries to your ISP, UDP and QUIC, processes with no rule. Each leak comes with a hint on how to close it: for browsers, for example, turning on DNS over HTTPS. The Overview screen brings it together: the most serious problem first, each proxy’s health and what is going through the proxy right now. How to check, and what isn’t caught.

What if the proxy server is down?

By default that app’s connections don’t go direct past the proxy; they fail with an error you can see in the monitor. That way nothing leaks silently. If you prefer, you can let them go direct in Settings. Overview and the menu bar show right away which proxy isn’t answering, and you can move its routes to another proxy, with undo if you change your mind. How to move routes.

Do calls and UDP work?

Routekeeper carries TCP through the proxy. UDP and QUIC are closed for proxied apps so traffic can’t slip past; browsers simply fall back to TCP. Calls need UDP, so keep calling apps on a direct route.

Can Routekeeper see my traffic?

Traffic passes through the network extension on your Mac and goes where you sent it. Routekeeper doesn’t decrypt connections and sends nothing to its developer: no analytics, no list of sites. It goes online on its own for only three things: checking for updates at getroutekeeper.app, downloading the service catalog from there every 6 hours, and, to show your external IP, asking ipinfo.io for it through your proxy. More in the privacy policy.

Why does macOS ask me to allow something?

Routekeeper runs as an Apple system network extension. macOS only turns those on with the owner’s explicit consent, so on first launch it asks three times: turn on the extension (System Settings → General → Login Items & Extensions on macOS 15 and later, System Settings → Privacy & Security on macOS 14), allow network content filtering, and allow the proxy configuration. You only do this once. Step by step.

What if I close the Routekeeper window?

Your rules keep working: the extension enforces them, and the window is only for editing rules and watching the monitor.

The lantern is lit

Public beta for macOS 14 Sonoma and later. Open the DMG and drag Routekeeper to Applications: the build is signed with Developer ID and notarized by Apple, and it keeps itself up to date.

First run · Docs · Privacy