Licensing Models

Cryptolens Software Licensing API supports a wide range of licensing models, allowing you to easily implement and migrate between them at any time.

Try and Buy

This model enables you to securely distribute trial versions of your product, which your customer can easily upgrade. Once they have upgraded, you can either grant them unlimited use (perpetual) or set up a subscription with monthly payments (read more).


A subscription is when your customers need to pay on continuously (eg. once a month) to keep using the product or some of its features. Alternatively, you can grant perpetual use of the product but require a subscription to obtain updates and support (read more).

Pay per Use

Usage-based licensing is when you charge for usage of specific features. For example, if you have an accounting software, you can charge per created yearly report. This model allows you to acquire more customers by providing an alternative way of paying for the software, for those customers that use the software rarely (read more).


Instead of node-locking licenses to specific machines, floating licenses allow you to restrict the number of users that can use the app at the same time. For example, your customers can install the software on 100 computers but only be able to use it on 10 of them at once (read more).

Fits: Desktop apps

Fits: Desktop apps

Fits: Desktop apps

Fits: Desktop apps

Node Locking

Node-locking ensures only a selected number of machines can use a license. Once the limit is reached, no more machines will be permitted. The benefit of this model is that you retain control of all instances of your software (read more).

Feature Locking

Feature locking makes it possible to create differenent packages of your product with different sets of features (eg. Lite and Pro versions). This is useful because you can focus on developing one product and then turn features on and off depending on customer needs.

Pay per Install

Charging per install is useful when there is no need to track each individual instance of your product, and when you instead need an approximate number of users. This model is recommended when licensing SDKs (read more).

User Account

Instead of granting users with a license key, you can allow them to use a user account instead. Cryptolens has developed a secure protocol for authenticating users inside an app. Moreover, your users also get acccess to a customer portal where they can manage all their subscriptions.

Fits: Desktop apps, SDKs

Fits: Desktop apps, SDKs

Fits: SDKs

Fits: Desktop apps