Frequently asked questions
Common questions about Antify: what it is, what it costs, which proxies it supports, and why it needs a system extension.
What is Antify?
A per-app proxy tool for macOS. You choose which apps go through which proxy; everything else connects normally, with no system-wide proxy and no TUN mode in your proxy app.
What does it cost?
Free to use.
Does Antify provide a proxy server?
No. Antify routes the traffic of the apps you choose to a proxy you already have: a working SOCKS5, HTTP, or HTTPS server.
Which proxy protocols are supported?
SOCKS5, HTTP, and HTTPS. SOCKS5 carries both TCP and UDP; HTTP and HTTPS carry TCP only.
Is Antify open source? What is the GitHub repository?
Antify itself is not open source. The public repository on GitHub is for feedback: bug reports and feature requests. The source code is not in it.
Is there an iPhone or Windows version?
No. macOS only, and it requires macOS 14.0 or later.
Why does it need a system extension?
Because routing per app means knowing which app opened each connection, and a system extension is the only way to learn that. It is also what separates this from turning on a system-wide proxy.
You approve the extension yourself in System Settings. Where that approval lives depends on your macOS version; the installation guide spells out each one.
Can Antify see my traffic?
Antify handles your traffic entirely on your Mac. The system extension reads a connection’s destination (domain or IP, and port) and the server name in the TLS handshake to match the rules you set; the traffic itself is relayed unchanged, never decrypted and never stored — Antify installs no root certificate.
The entries on the Connections screen live in memory only, at most 1,000 in the system extension and 1,000 in the app, and are gone once it quits. Antify does not write them to a file and does not send them to any server.
For anything not covered here, open an issue in the feedback repository on GitHub. GitHub