Offline Licensing
Use offline when a product must enforce rights for a limited window without a continuous cloud round-trip. The product presents a signed request; the platform issues a signed response (lease / entitlement window) that the client verifies and applies locally.
Offline is not the same as air-gapped handoff (operator-carried packages) or continuous Local Relay sync. Modes can combine — for example a node-locked license with an offline grace window.
What you get
| Piece | Role |
|---|---|
| Offline request | Device / site asks for a time-bounded entitlement or lease window |
| Offline response | Signed issuer decision the product can enforce until expiry |
| Policy clamps | Validity is bounded by product policy (grace / lease rules) — not by client hints alone |
Payloads must not carry private keys, raw long-lived secrets, or refresh tokens. Treat offline material like any other signed Runtime artifact: verify audience, expiry, and trust before granting features.
The ProductId supplied through the historical offline-request compatibility input is ignored. Product identity comes only from the current verified License runtime snapshot; missing or mismatched snapshot identity fails closed. See the Wave 74.15 cutover guide.
When to use
- Intermittent connectivity, but occasional online issuance is possible.
- You need a cached enforce window, not a full site isolation workflow.
- True no-outbound sites → prefer Air-gapped (± Relay).
Related
- Mode map: Licensing Models
- Vocabulary: Core Concepts (Runtime lease)
- Seats over shared capacity: Floating
- Integrators: API Reference · Error catalog · SDKs
Next steps
- New here? Getting Started
- Human key for online Runtime calls: License Keys