Features and specifications

What Antify actually does: supported proxy types, what a rule can match, how traffic is handled, and the system requirements.

This page lists what the current version (downloadable below) can do, so you can tell whether it covers your case. Anything not listed is not there.

System requirements

macOS 14.0 or later.
The first run installs a system extension, which you approve in System Settings.
macOS only. There is no iOS, Windows, or Android version.

SOCKS5, HTTP, and HTTPS, with default ports 1080, 8080, and 8443.
Username and password authentication. Passwords are kept in the macOS Keychain, not in the app database.
Test one proxy or all of them at once; errors distinguish connection, handshake, and authentication failures.
Per proxy: whether a failed proxy may fall back to a direct connection (off by default), and whether it can reach private networks (off by default).
Antify does not provide a proxy service; you bring your own.

A rule can target a .app, a command-line executable, a script package, or a directory, or a Bundle ID prefix such as com.apple.*.
Three actions: Proxy, Direct, Block. Block needs no proxy server.
Rules can be narrowed by target host and port; hosts accept domain wildcards, IPs, IP ranges, and CIDR, and a leading - excludes an entry.
A rule can optionally cover the processes that app launches (off by default); XPC services always follow their host app rule.
Proxy and Block rules can turn on Kill Switch: while the Antify proxy is not running, the app is kept offline. It is enforced by a system content filter and stays in effect after you quit Antify or restart your Mac.
A rule stored on a symlink follows the link when a package manager repoints it on upgrade.

SOCKS5 carries TCP and UDP; HTTP and HTTPS carry TCP only, and UDP is not forwarded, so apps fall back to TCP.
Connections to localhost or to an address of this Mac always go direct, regardless of rules.
Private addresses go direct by default; a proxy can turn on Can reach private networks to send other private networks through it, while the network this Mac is on stays direct.
DNS queries from proxied apps are answered locally, with domain names handed to the proxy to resolve.
Rules are evaluated when a connection is opened; established connections are unaffected.

Multiple configurations, each with its own rule set and default behavior.
Configurations can switch automatically based on the Wi-Fi network in use.
A configuration can be exported to a file and imported on another Mac; passwords stay in the original Keychain.

Connection records show the action taken and which rule layer matched.
The activity log records proxy and rule changes, configuration switches, and warnings.
Discovery mode finds apps that have no rule yet.
Diagnostic logs can be collected in one step.

Interface language follows the system, or can be set to English or Simplified Chinese.
Optional launch at login and start the proxy on launch.
Built-in automatic updates.