Air-gapped operation

Full air-gapped operation (zero outbound network calls, ever) is not a supported mode yet. It is on the same enterprise track as Kubernetes and SCIM. Here is what is already true today, and what is still missing.

Already true today

• No license key, ever. Proliferate is open source. There is no license server and nothing to validate online or offline; self-hosted instances are never gated on reaching Proliferate's infrastructure.
• Telemetry is one small POST, and you can turn it off. A self-managed install sends a single anonymous daily version heartbeat and nothing else. Set PROLIFERATE_ANONYMOUS_TELEMETRY_DISABLED=1 and that stops too. See Telemetry & privacy for the exact payload.
• Vendor telemetry never activates. Sentry and other vendor tooling are gated to Proliferate's own hosted product in code, not by configuration; a self-hosted server cannot turn them on even by setting the DSN.

What still needs the internet

A self-hosted deployment isn't zero-egress today:

• Pulling images. docker compose pull fetches the server (and, if you enable the model gateway, LiteLLM) images from ghcr.io. There is no offline image bundle yet; you can mirror the images to your own registry and point PROLIFERATE_SERVER_IMAGE at it, but that is a manual workaround, not a documented flow.
• Certificates. By default, Caddy requests a publicly trusted certificate from Let's Encrypt, which needs outbound access and a publicly resolvable domain. Bring your own certificate if your network can't do that.
• Desktop and runtime updates. Your server picks the version; the actual binaries and update manifests are served from Proliferate's CDN, so desktop apps and cloud runtimes need a path to the internet to update.