Full Offline
Collect the customer’s machine fingerprint before issue and sign it into the licence. The application verifies locally and never contacts DYCRYPT.
Licence types
Every type uses the same signed licence and SDKs. The difference is when your application contacts DYCRYPT and when the licence binds to one machine.
Collect the customer’s machine fingerprint before issue and sign it into the licence. The application verifies locally and never contacts DYCRYPT.
The first successful check claims the licence for one machine. Your application continues checking on the signed schedule and becomes stale if it remains offline too long.
Verify locally on every start and confirm online in the background. Choose online or offline activation per licence and keep working inside the signed offline window.
At a glance
Use Hybrid for most desktop and server applications, Full Offline for truly disconnected machines, and Full Online when central enforcement must be immediate.
| Capability | Full Offline | Full Online | Hybrid |
|---|---|---|---|
| Works without a network | Always | Until the signed window closes | Within the signed window |
| One licence, one machine | Bound before issue | Bound on first check | Online or offline activation |
| Remote revocation | No | Yes | Within the check window |
| Installation visibility | No network telemetry | Yes | Yes |
| Best fit | Air-gapped environments | Strict central enforcement | Most applications |
Machine fingerprints
DYCRYPT hashes up to five machine signals separately and matches three by default. Replacing a network card or renaming a host does not automatically invalidate a legitimate installation.
Integration
The Java, Node.js, and Python guides cover fingerprint commands, local verification, online checks, and the `STALE` recovery path.
Open the integration guide →