Before you install

The desktop app needs to change local trust and proxy settings to route supported HTTPS traffic through STATIC. Read what those changes mean before approving an operating-system prompt.

Check your platform

The current desktop offering lists the builds available to install. The existing desktop guide describes Windows and macOS paths. Windows uses WSL2 for the managed 404 Rose distribution; allow room for its downloaded archive and imported filesystem, and ensure WSL2 is available. macOS runs a native STATIC path. For a direct Linux setup, start with the Linux CLI guide; the older desktop guide does not give a complete Linux app installation procedure.

Understand the trust prompt

STATIC generates a local CA key and public root certificate. When you approve trust for the public root, applications using that trust store can accept site certificates issued by this STATIC instance when their traffic is routed through it. The private signing key belongs to STATIC and should not be imported into a host trust store or shared. CA and trust covers generation, platform stores, and removal.

The app may request administrator privileges for host trust, proxy settings, or WSL operations. You can disable routing in the app when not using 404. Do not leave a browser or system proxy pointing at a stopped engine.

Read the product terms

The desktop and any account-backed service are governed by the current Privacy Policy, Terms of Service, and EULA. The open-source STATIC components have their own AGPLv3 license when used through the self-hosted path. Review the current terms and available product build before downloading.

Continue with Getting started for setup and daily use.