Quick Start

This guide takes you from a new DYCRYPT SaaS organisation to a verified licence in your application.

1. Create your organisation

Open DYCRYPT, create your organisation, and invite the people who will manage products or issue licences. Business and Business Max include unlimited users with the standard roles; Enterprise can use customizable roles.

2. Define a product

Create a product with a stable product key. Choose its licence type, signing algorithm and certificate type, validity defaults, and only the parameters your application will enforce.

For most desktop and server applications, start with Hybrid. Choose a check interval and the maximum time the application may remain without a successful check.

For example, a product might define:

Claim	Type	Purpose
edition	ENUM	Select an application tier.
maxUsers	INTEGER	Limit new user creation.
features	STRING_LIST	Enable named capabilities.

3. Choose the activation path

• Full Offline: ask the customer to run your SDK-powered fingerprint command and send the resulting DYC1.… value before you issue.
• Full Online: no fingerprint is needed at issue; the first successful check binds the licence.
• Hybrid: choose online activation for the usual flow or offline activation when that customer cannot connect during setup.

4. Issue a licence

Open Issued licences from the product navigation, choose or create a customer, select the type and activation when applicable, set the term and parameter values, then issue. Download the resulting .lic file.

5. Open the product’s Quick Start Guide

The product-specific guide provides:

• the product key expected in the prd claim;
• the public key or certificate PEM to ship with the application;
• verification examples and an AI-ready brief;
• the issuer URL and organisation slug for Full Online and Hybrid checking;
• a fingerprint command for Full Offline and offline-activated Hybrid licences.

Never ship a private key, keystore password, HSM PIN, platform password, or API token with the application.

6. Integrate the SDK

Choose Java, Node.js, or Python. Build one verifier for the product, read the complete licence string, and call the method required by its type.

• Full Offline uses local verify().
• Full Online and Hybrid use check() on startup and on the signed schedule.
• Hybrid can also use verify() for immediate local startup, provided your application follows with scheduled online checks and enforces STALE.

Handle GRACE, PENDING, EXPIRED, STALE, REVOKED, INVALID, and UNKNOWN deliberately. Read product claims only from a signature-verified result.

Continue with Verify a licence.