Why Hybrid is the right default for most applications

Your application should be able to verify a licence immediately with a public key. You may also need to revoke that licence, see whether one machine is using it, and stop an installation that has stayed disconnected beyond an agreed window.

Hybrid combines those needs.

Start locally

On every start, the SDK checks the signature, product, dates, machine fingerprint when present, and application claims locally. The application can start promptly even when the network is temporarily unavailable.

Confirm on a signed schedule

The licence carries two signed values: how often the application should try to check, and the maximum time it may remain without a successful check. Your integration may use a stricter schedule, but cannot widen what the licence allows.

If the maximum window passes, the SDK reports STALE. That status tells your user to reconnect; it does not pretend the licence was forged or corrupted.

Choose activation per customer

Most Hybrid licences bind on their first successful online check. When a customer cannot connect during setup, issue that specific licence with offline activation after receiving its machine fingerprint. It still checks in afterward; only the initial binding changes.

Test startup, network loss, window expiry, reconnection, revocation, and hardware replacement before shipping your enforcement flow.