Three licence types
Choose Full Offline, Full Online, or Hybrid per product, then preserve the selected type in every signed licence.
Features
Everything your application needs to enforce a licence.
DYCRYPT connects the commercial rules you define with a signed result your application can verify and act on.
Machine binding
Bind a licence before issue or on first online activation. Release the machine when a legitimate hardware move is needed.
Privacy-conscious fingerprints
Match stable, one-way hashes from the machine. Raw identifiers and IP addresses are not part of the fingerprint.
Products and typed claims
Define editions, features, limits, dates, and other application parameters once, then collect valid values at issue time.
Licence lifecycle
Issue, download, renew, revoke, reinstate, inspect, and track licences without losing their signed history.
Java, Node.js, and Python
Verify signatures, enforce machine binding, schedule online checks, and read typed claims with consistent SDK behavior.
Modern signing choices
Use Ed25519, RSA, or elliptic-curve signing with public keys, X.509 certificates, keystores, or supported hardware options.
Team access
Invite users into standard roles, protect sign-in with passkeys, and keep sensitive actions with the right people.
Scoped API tokens
Automate product, customer, and licence workflows with tokens limited to the resources and actions your integration needs.
Application-level control
Return a status your code can explain.
The SDK distinguishes active, grace, pending, expired, stale, revoked, invalid, and unknown licences so your application can show the right recovery path.
Design a helpful enforcement flow
- Warn during grace without deleting customer data.
- Tell a stale installation to reconnect.
- Explain a machine mismatch instead of reporting a generic failure.
- Gate new usage before disrupting existing data.
See it in context