Hosted Floating Licenses

With hosted floating licenses, Cryptlex's servers act as the license server, so your app leases seats directly from Cryptlex and you only need LexActivator. For how floating licensing works in general, see the Floating Licenses overview.

Creating a hosted floating license

When creating the license, configure it as follows:

Set the license type to hosted-floating.
Set the lease duration to how long you want each seat leased.
Keep the server sync interval shorter than the lease duration by at least 30 seconds, since server sync is what renews the lease.

The lease duration is a tradeoff. A long lease holds a seat for its full duration after an app crashes, so stale seats come back slowly. A short lease reclaims them sooner, but forces more frequent syncs and a higher volume of API requests.

Adding floating licensing to your app

You implement hosted floating licenses the same way as node-locked licenses with LexActivator, with a difference in how you activate and release seats: validate the license first, activate only when needed, and release the seat on exit so it does not become a zombie. For the implementation and code sample, see hosted floating licenses.

Borrowing for offline use

To let a user work offline, lease the license for a longer duration by calling SetActivationLeaseDuration() before activating, so the app keeps working while disconnected and the seat is freed automatically when the lease expires. This requires enabling the license's allow client lease duration property. For on-premise deployments, borrowing works differently, through offline floating licenses.

A borrowed seat is not a free seat. It stays counted against the license for the whole lease duration even though the user is offline, so a few users borrowing for weeks at a time reduces the concurrent seats available to everyone else. Account for it when deciding how many seats to sell.

Overview On-Premise Floating Licenses

Last updated: 8/5/2026