Hybrid

Hybrid verifies locally on every start and checks with DYCRYPT on a schedule. It is the recommended default for most desktop and server applications.

Why use Hybrid

• Local verification keeps startup fast and resilient.
• Scheduled checks carry revocation and installation visibility back to the application.
• The signed maximum offline window prevents indefinite disconnected use.
• A temporary network failure does not stop the application immediately.

When the offline window closes without a successful check, the SDK returns STALE until it reconnects.

Choose activation per licence

• Online activation: the first successful check binds the licence. This is the normal path and requires no fingerprint during issuance.
• Offline activation: the customer sends you a fingerprint first and the licence ships pre-bound. Use this when the install machine cannot reach DYCRYPT during setup.

Offline activation changes only the first binding. The application must still perform later checks within the signed window.

Application integration

Call check() on startup when possible and on the signed interval afterward. If your user experience starts with local verify(), schedule check() immediately in the background and do not ignore STALE.

Test these paths before production:

1. online activation on the intended machine;
2. copying the licence to a second machine;
3. temporary network failure inside the offline window;
4. STALE after the window;
5. reconnection and recovery;
6. revocation and machine release.