Licensing built for your application

Ship software.
Control every licence.

Create signed licences, bind them to one machine, and choose exactly how your application checks them—Full Offline, Full Online, or Hybrid.

SaaS or on-premisesMachine-boundJava · Node · Python
DYCRYPT / APPLICATION FLOW
01
Define your productClaims · validity · signing method
02
Choose a licence typeFull Offline · Full Online · Hybrid
03
Issue a signed licenceCustomer · machine · application limits
SDK
Enforce it in your applicationVerify · check status · read typed claims
ACTIVE · BOUND TO ONE MACHINE
3licence enforcement modes
3application SDKs
6supported signing algorithms
1machine per bound licence

Built for developers and application owners

Your licensing model, enforced.

Define what your licence grants, issue it to a customer, and let your application make a clear decision from a verified result.

OFF

Full Offline

Pre-bind a signed licence to one machine and verify it locally without any network dependency.

ON

Full Online

Bind on first use, check on your schedule, and apply revocation or machine release immediately.

HYB

Hybrid

Keep local verification fast while preserving revocation and visibility within a signed offline window.

CLM

Typed licence claims

Model editions, features, dates, lists, booleans, and usage limits as claims your SDK reads safely.

LIF

Complete lifecycle

Issue, renew, revoke, reinstate, download, and release a machine binding from one workspace.

DEV

Developer-ready SDKs

Integrate Java, Node.js, or Python with product-specific examples and an AI-ready brief.

Use it your way

SaaS simplicity or on-premises control.

Start with the hosted service, or choose an Enterprise on-premises deployment when your security or compliance requirements demand it.

SaaS

Ready when your team is

Use DYCRYPT without operating licensing infrastructure. Create your organisation, configure a product, and integrate the SDK.

Enterprise

On-premises deployment

Run DYCRYPT in your environment and add custom HSM or PKCS#11 integration when private keys need hardware-backed protection.

Quick start

From product to verified licence.

Create your SaaS organisation, configure a product, and add licence enforcement to your application with an SDK.

Read the Quick Start Guide →

The integration path

  1. Create your DYCRYPT organisation.
  2. Define a product, licence type, and typed parameters.
  3. Issue and deliver the signed licence.
  4. Verify it from your application with Java, Node.js, or Python.

Start with the Free plan

Build your integration before you take it to production.

Use every core workflow with one user and Ed25519 signing, then move to a production plan when your application is ready.