Overview

Cryptlex provides client libraries (SDKs) and REST APIs to integrate licensing into your app. Which one you need depends on the licensing model you are implementing:

• LexActivator for node-locked, hosted floating, named-user licenses, and trials. It also supports offline activations.
• LexFloatClient with LexFloatServer for floating licenses inside an air-gapped or otherwise restricted customer network.
• Web API for integration and automation, such as creating licenses and users or processing orders.

LexActivator

LexActivator is the main Cryptlex client library, used to implement node-locked, hosted floating, and named-user licenses, as well as trials. It validates licenses against the Cryptlex servers and handles HTTPS, response signature verification, encrypted local storage, machine fingerprinting, virtual machine detection, time tampering detection, periodic server sync, and offline activations for you.

It is available for Windows, macOS, Linux, Android, and iOS, with bindings for almost every major programming language. See Using LexActivator.

LexFloatClient & LexFloatServer

When a client application needs floating licenses but runs in an air-gapped, secured, or otherwise restricted network, it cannot reach the Cryptlex servers directly. For this, Cryptlex provides an on-premise floating license server, LexFloatServer, that your customer runs inside their own network. Your app requests and releases leases from LexFloatServer using the LexFloatClient library, and never contacts Cryptlex itself. LexFloatServer, in turn, may run connected to the Cryptlex servers or fully offline, depending on how it is configured.

Web API

Everything in Cryptlex is available through the REST Web API. You can use it in two ways:

• In your app, as an alternative to LexActivator, to activate and validate licenses directly, though this is not recommended. Use LexActivator wherever it is available for your platform.
• On your server, to automate license creation, user management, and order fulfillment, typically with personal access tokens.

While integrating, you can work against a sandbox environment to keep test data out of production.

Minimum requirements

LexActivator and LexFloatClient

The two client libraries you embed in your app share the same platform support.

^* Building the Android library requires NDK r29e or later.

LexFloatServer

The on-premise floating license server your customer runs on their own network.

Whichever path you choose, review the best practices before shipping.