Skip to content

macOS

This is the direct STATIC path for macOS.

The recommended release assets are packaged operator bundles. Each zip includes the binary, the release manifest files, and the profile catalog you need to start STATIC directly on macOS.

Download for macOS Apple Silicon Download for macOS Intel

Each macOS operator bundle includes:

  • 404-runtime/static_proxy
  • 404-runtime/config/static.example.toml
  • 404-runtime/static_proxy-release-manifest.json
  • 404-runtime/static_proxy-release-manifest.json.sig
  • 404-runtime/static_proxy-release-manifest.json.pem
  • 404-runtime/profiles/manifest.json
  • 404-runtime/profiles/firefox-windows.json
  • 404-runtime/profiles/chrome-windows.json
  • 404-runtime/profiles/edge-windows.json

Extract the zip that matches your machine into your home folder, then keep using that same home-folder path in the commands below.

Before you start

  • Apple Silicon uses static_proxy-macos-aarch64
  • Intel uses static_proxy-macos-x86_64
  • the public profile catalog is chrome-windows, edge-windows, and firefox-windows
  • this walkthrough defaults to firefox-windows
  • if you use Chrome, swap firefox-windows for chrome-windows
  • if you use Edge, swap firefox-windows for edge-windows
  • the bundled config listens on 127.0.0.1:4040
  • the local control plane uses 127.0.0.1:4042

For the current release page, use the latest GitHub release.

1. Verify the binary appears in the release manifest

Run this in Terminal:

cat "$HOME/404-runtime/static_proxy-release-manifest.json"

If you extracted the zip into a different folder, read the manifest from that location instead.

2. Extract the bundle into your home folder

If you use Finder:

  1. double-click the zip file to unpack it
  2. drag the extracted 404-runtime folder into your home folder
  3. confirm the final path is $HOME/404-runtime

If you want to do it from Terminal, run this:

ditto -x -k "$HOME/Downloads/404-macos-aarch64.zip" "$HOME"
chmod +x "$HOME/404-runtime/static_proxy"

If you are on Intel, replace 404-macos-aarch64.zip with 404-macos-x64.zip.

Working directory

The Terminal commands below assume the bundle lives at $HOME/404-runtime.

Start each session with:

cd "$HOME/404-runtime"

3. Inspect the profile catalog and start STATIC

List the available profiles:

cd "$HOME/404-runtime"
./static_proxy --config ./config/static.example.toml --list-profiles

Start STATIC with the profile that matches your browser family:

cd "$HOME/404-runtime"
./static_proxy --config ./config/static.example.toml --profile firefox-windows

Use chrome-windows for Chrome or edge-windows for Edge.

4. Trust the generated CA

Ask the local control plane where the CA lives:

curl -s http://127.0.0.1:4042/ca/status

Then trust the static-ca.crt path it reports:

sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain /path/to/static-ca.crt

If you use Firefox, import the same certificate in Firefox under Settings → Privacy & Security → Certificates → View Certificates → Authorities.

5. Route browser traffic through STATIC

The bundled config listens on 127.0.0.1:4040.

For Chrome or Edge:

  • System Settings → Network → your active interface → Details → Proxies
  • enable the local proxy path that fits your setup and point it at 127.0.0.1:4040

For Firefox:

  • Settings → Network Settings → Manual proxy configuration
  • HTTP Proxy: 127.0.0.1
  • Port: 4040
  • enable Also use this proxy for HTTPS

If you launch STATIC with a custom port, route the browser to that port instead.