Licentry vs Cryptlex

Cryptlex is an established licensing platform built around LexActivator, a native SDK you link into your application. It covers node-locked, named-user, floating and offline licensing, and it can be deployed on your own servers. It is aimed at desktop software vendors who want a mature SDK rather than a bare API.

Choose Licentry

Pick Licentry if you want an HTTP-based integration with signed responses and device-bound sessions at a lower listed starting price.

Free trial, then 19 dollars a month. Studio is 59. Prices exclude VAT, which is added at checkout where it applies.
Choose Cryptlex

Pick Cryptlex if you sell into enterprise networks that need floating licences or air-gapped activation.

Starter listed at 100 dollars a month for 1,000 activations and 3 products, at the time of writing.

Figures about Cryptlex were checked in July 2026 against their own published pages, or, where they do not publish a figure, against the public listings named alongside the price above. Pricing changes. Ours is in the pricing section, and if anything here is out of date we want to know at [email protected].

Where Licentry is different

These features help you control access to your software and investigate licence sharing.

Lower listed starting price

Cryptlex Starter was listed at 100 dollars a month when checked. Licentry starts at 19 dollars a month.

HTTP-based integration

Licentry uses five HTTPS endpoints. You can integrate from Rust, Go, Delphi, AutoLISP, Unity or Python without a platform-specific Licentry SDK.

Shows evidence of licence sharing

Review a licence's device, IP and location history in the dashboard when you suspect sharing. Watermarked Windows downloads can also help identify the account behind a leaked build.

Side by side

A tick means the feature is supported. If Cryptlex does not describe a feature in its documentation, we mark it "not advertised"; that does not mean it is unavailable.

Capability Cryptlex Licentry
Starts under 20 dollars a month –Listed from 100 ✓19
Integrates through HTTP ~Platform-specific SDK ✓Five HTTPS calls
Can bind tokens to a device ~Not advertised ✓DPoP, RFC 9449
Your app checks signed responses ~Not advertised ✓Signed, P-256
Trace a leaked build to the account that downloaded it ~Not advertised ✓Windows watermarks
Ties a licence to one machine ✓ ✓Limits enforced by the server
Start without talking to a salesperson ✓ ✓
Floating licences on a customer LAN ✓ ~Session limits
Built for long offline and air-gapped use ✓ ~Signed offline token
Native SDK you link into the app ✓LexActivator –HTTPS only

✓ does it  ~ partly, depends on the tier, or not advertised  – not what it is for

When Cryptlex is the better choice

Consider Cryptlex if these requirements matter to your project.

You need floating licences on a customer network

Cryptlex supports floating licences served from a customer's machine across their network. Licentry limits concurrent sessions per licence; it does not provide the same local licence-server model.

Your customers work offline for long stretches

Cryptlex supports activation on air-gapped systems and extended offline use. Licentry provides a limited offline grace period using an ES256-signed token and requires a network connection outside that period.

You want a native SDK you link and call

LexActivator provides a native licensing library for C, C++ and .NET desktop applications. Choose it if your team prefers calling a library to writing an HTTP integration.

The short version

We recommend Cryptlex for floating licences and offline activation on restricted networks. Consider Licentry for signed HTTP sessions and proof-of-possession checks, with a lower listed starting price.

Test the five-endpoint HTTP integration on the free dev trial.