Skip to content

Air-Gapped Deployments

Air-gapped instances never phone home. Instead of registering with the platform over HTTPS, they verify a long-lived, signed offline license token locally against the bundled public key.

Your approval email includes an offline license token in addition to the license key. Follow your platform’s steps to provide that token to the instance. It’s a signed license the server verifies locally with the bundled license-public.pem — the same verify-only public key that ships with every bundle. It can never mint a license, only check the signature on the one issued to you.

Image updates for air-gapped sites are delivered out-of-band rather than pulled from the platform. Load the new server image into the host’s Docker engine and recreate the server container; the migration-boundary rules still apply — apply required intermediate releases in order.