Repository map

404 spans multiple codebases and a delivery service. The boundaries matter when following a feature from a profile through the running proxy to the Windows host.

Open-source core

The un-nf/404 repository (also mirrored at Codeberg) contains src/STATIC_proxy/, its profile catalog, src/ebpf/, distro/, build scripts, and the distro release workflow. The STATIC overview and Rose overview trace those pieces. Profile files live under src/STATIC_proxy/profiles/; the Linux classifier is src/ebpf/ttl_editor.c.

Desktop application

The separate desktop product has a Tauri host layer and React UI. The published desktop guide describes host trust installation, proxy settings, updater behavior, and Windows management of the WSL2 distribution. Desktop platform notes separate the documented behavior from the verified open-source proxy implementation. The application repository is separate from un-nf/404; this reference does not treat the app’s private code as independently verified.

Documentation and delivery

This Markdown documentation is built by the Astro project in un-nf/Website. The legacy 404-docs repository records the earlier MkDocs text during migration.

The worker-backed update service delivers account and licensing routes, authenticated product downloads and desktop updater payloads, and the public distro routes: /distro/manifest.json, /distro/manifest.json.sig, and versioned /distro/<tag>/404-distro.tar.gz, manifest.json, and manifest.json.sig. The release contract explains signing, hashes, and caching. This delivery boundary is distinct from STATIC’s local control API.