Brick proxyYour proxy, as a VPN.
Brick proxy sends every connection on your Mac through a SOCKS5, HTTP or HTTPS proxy that you supply. Enter it once, click Connect, and every app goes through it.
macOS 14 or later
Apple silicon and Intel
brew install --cask NotSoSmartDev/tap/brick-proxy
How it works
Every connection, one proxy
macOS hands the app raw packets. A network stack inside it turns them back into connections and opens each one through your proxy — CONNECT for TCP, UDP ASSOCIATE for UDP.
Names, not addresses
The app answers DNS itself and hands your proxy the site’s name, so the proxy resolves it and your network never sees which sites you open.
Check before you connect
The globe on the proxy card shows its exit address, country and whether it carries UDP — through the proxy itself, before any traffic does.
What goes through
- TCP — always, through SOCKS5 or HTTP CONNECT.
- UDP — SOCKS5 only, and only if the proxy answers UDP ASSOCIATE. Many refuse. An HTTP proxy carries TCP only.
- DNS — intercepted, and resolved by your proxy rather than by your Mac. Apps with their own DoH or DoT, and connections straight to an IP address, go through as addresses.
Paste a whole proxy string — socks5://user:pass@host:port — and the fields fill themselves. Keep a profile per proxy and switch in one click. The B icon in the menu bar shows whether you are connected and disconnects without opening the window; quitting the app disconnects too.
Your data
No account, no ads, no analytics, and no servers of ours in the path: your traffic goes only to the proxy you set up. Proxy addresses and passwords stay in your iCloud Keychain. The app checks for updates only if you allow it, and sends nothing about you when it does.