Windows↗
Import the 404 distribution into WSL2, start STATIC, trust its local CA, and configure your browser.
Self-hosted / CLI
The self-hosted path lets you run STATIC and manage profiles yourself. It does not require the managed desktop application. Choose the guide for the operating system that will run the proxy.
Choose your platform
macOS↗
Run the packaged STATIC bundle on Apple Silicon or Intel, then configure certificate trust and your browser.
Linux↗
Run the published x86_64 binary with the profile catalog. Packet handling is an optional, separate step.
What the guides cover
Each platform guide follows the same order: prepare the machine, stage the release, choose a profile, start STATIC, trust the CA certificate it generates, route a browser through the local listener, and check that the connection works. Merely starting the proxy does not route your browser through it.
Use a profile from the same browser family as your browser: firefox-windows for Firefox, chrome-windows for Chrome or another Chromium-family browser, and edge-windows for Edge. These are the public profiles in the current release; the platform name in a profile is the identity presented to sites, not a requirement that your host computer run Windows.
Before you install
STATIC terminates HTTPS locally. Only trust the CA certificate generated by the instance you installed, keep its private key private, and remove its trust when you stop using the installation. The proxy does not change your public IP address or hide an account you sign into.
For source builds and distribution packaging, see Build from source. The latest 404 release contains the operator downloads referenced by these guides.