Air-Gapped Licensing
Air-gapped sites cannot (or must not) keep a continuous Host→cloud HTTPS session. Operators move signed packages between cloud and site — export, carry, import — instead of relying on always-on sync.
Air-gap complements Local Relay continuous sync; it does not replace Relay for sites that can sync outbound. It is also distinct from single-device offline request/response issuance.
Directions
| Direction | Idea |
|---|---|
| Cloud → site | Export signed entitlements / revocation (± offline material); import and apply on the site (often via Relay.Host) |
| Site → cloud | Export usage / status / receipts (no private keys); import on the cloud for reconciliation |
Packages are fail-closed: bad signature, digest mismatch, or wrong tenant/audience → reject the whole apply. Re-import of the same package id is idempotent (no duplicate seat or usage side effects).
When to use
- True air-gap or scheduled sneakernet transfers.
- Policy forbids continuous outbound from the site.
- You still need occasional capacity / revocation updates without opening a permanent tunnel.
Related
- Continuous on-prem sync: Local Relay
- Per-device signed windows: Offline
- Shared seats that may be granted offline: Floating
- Mode map: Licensing Models
- Integrators: API Reference · Errors