Cryptlex Documentation
  • Welcome to Cryptlex!
  • Getting Started
    • Overview
    • Licensing Models
  • License Management
    • License Templates
    • Implementing License Models
    • Creating Licenses
    • License Subscriptions
    • Custom License Fields
    • Meter Attributes
    • Suspending Licenses
    • Revoking Licenses
    • Maintenance Policies
  • Feature Management
    • Overview
    • Features and Entitlement Sets
    • License Feature Entitlements
    • Accessing Feature Entitlements
    • Use Cases
  • User Management
    • Roles
    • Creating Users
    • Authenticating Users
    • Organizations
    • Resellers
    • Customer Portal
    • Reseller Portal
    • Google SSO
    • SAML SSO
  • Release Management
    • Overview
    • Creating Releases
    • Distributing Releases
  • Node Locked Licenses
    • Overview
    • Using LexActivator
      • Using LexActivator with C, C++ and Objective C
      • Using LexActivator with C#
      • Using LexActivator with VB.NET
      • Using LexActivator with Java
      • Using LexActivator with Delphi
      • Using LexActivator with Python
      • Using LexActivator with Go
      • Using LexActivator with Node.js
      • Using LexActivator with Ruby
      • Using LexActivator with Android
      • Using LexActivator with iOS
      • Using LexActivator with Flutter
    • Using Web API
    • Offline Activations
    • Proxies and Firewall
  • Floating Licenses
    • Overview
    • Hosted Floating License Server
    • On-Premise Floating Licenses
      • LexFloatServer
      • Using LexFloatClient
        • Using LexFloatClient with C, C++ & Objective C
        • Using LexFloatClient with C#
        • Using LexFloatClient with VB.NET
        • Using LexFloatClient with Java
        • Using LexFloatClient with Delphi
        • Using LexFloatClient with Python
        • Using LexFloatClient with Node.js
        • Using LexFloatClient with Go
        • Using LexFloatClient with Android
        • Using LexFloatClient with iOS
      • Offline Floating License
  • Named User Licenses
  • Timed Trials
    • Verified Trials
    • Unverified Trials
  • Licensing Docker Apps
  • Webhooks
  • Automated Emails
  • Web Integration
    • Personal Access Tokens
    • Using Web API
    • Using Zapier
    • Using FastSpring
    • Custom Development
  • Changelog
    • Web API
    • LexActivator
    • LexFloatClient
    • LexFloatServer
  • Legal
    • Terms of Service
    • Privacy Policy
    • Subprocessors
    • Data Processing Addendum
    • Service Level Agreement
    • Security, Privacy, and Compliance
    • Open Source Licenses
  • Cryptlex On-Premise
    • Overview
    • System Requirements
    • Server Layout
    • Installation Guide
      • Docker Compose
      • Kubernetes
    • Configuring Client Libraries
    • Monitoring and Error Reporting
Powered by GitBook
On this page
  • Perpetual licensing model
  • Metered licensing models
  • Subscriptions
  • Meter by usage
  • Seat based licensing models
  • Node locked licenses
  • Floating licenses
  • Which licensing model should I choose?
  • Need help
  1. Getting Started

Licensing Models

Perpetual licensing model

It refers to licenses which have lifetime validity. A user buys a license and can use your product for lifetime without any need of paying again.

Metered licensing models

Subscriptions

Licenses can be metered by time and they would expire after a certain amount of time period. Your customers would usually pay a monthly or a yearly subscription fees and when they renew, the license should also be renewed.

Meter by usage

Sometimes you want your customers to pay for what is actively used regardless of how long they possess your product. The usage can be defined as the amount of time for which your app is used, number of times it is run, number of specific operations etc. depending on your business requirements.

Seat based licensing models

Node locked licenses

A node locked license is bound to a machine on which the license was activated. It means that the license key cannot be used on any other machine (if license allows a single activation/seat).

If license allows multiple activations (multi-seat), then after all the activations are used, the license key cannot be used on other machines.

Floating licenses

A floating license is temporarily bound to a machine for a specific amount of time. When the time expires the activation (seat) is automatically freed up (if not renewed), so that any other machine can use the license.

So if your floating license allows for 100 activations (seats), then at any instant of time no more than 100 machines can use your application.

Which licensing model should I choose?

You will most of the time use node locked licenses which would be either perpetual or subscription based.

When licensing your product to any university or a big company which may require large number of license seats, you will usually opt for floating licenses as that is more economical for your customers.

Other than this you can add some other restrictions too like usage count or implement a completely custom licensing model using metadata fields which you can add to your licenses.

Need help

PreviousOverviewNextLicense Management

Last updated 10 months ago

In case you need help for implementing any of the above mentioned licensing models, we'll be glad to help you. You can either post your questions on our or can contact us through .

support forum
email