How it works
A floating license needs three parts: a pool, a server and a client.
- The organization buys N seats. The license server holds the pool.
- When a user starts the app, the client asks the server for a seat. The server grants a lease, which is a seat reserved for a limited time.
- While the app runs, the client sends a heartbeat every few minutes to renew the lease.
- On a clean exit the client returns the seat. If it crashes or loses power, the heartbeat stops and the lease runs out, freeing the seat.
The seat belongs to nobody in particular. That is the point, and also what makes it more work to build than a key check.
Worked example: 20 engineers, 8 seats
An engineering team has 20 people who use a simulation tool. A log of when they run it shows that at most 8 people use it at once. The team buys 8 floating seats instead of 20 named ones. All figures here are an example.
Lease settings: a 15-minute lease, renewed by a heartbeat every 5 minutes.
| Time | Event | Seats used |
|---|---|---|
| 10:00 | 8 engineers start the tool | 8 of 8 |
| 10:02 | A 9th engineer starts it | refused, 8 of 8 |
| 10:02 | One engineer’s laptop crashes | 8 of 8, lease still held |
| 10:17 | The crashed lease expires | 7 of 8 |
| 10:18 | The 9th engineer retries | 8 of 8 |
The crash row is the failure mode to design for. A shorter lease frees seats faster but sends more heartbeats and fails sooner when the network drops. Whatever you choose, tell users how long a crashed seat stays blocked.
Floating versus node-locked and device limits
A node-locked license is tied to one machine. A device limit counts how many machines have been activated, whether or not they are running. A floating license counts running sessions and ignores which machine runs them. Concurrent license describes the same cap from the pricing side.
How Clavem handles it
Clavem does not offer floating licenses. It has no checkout, heartbeat or lease. Its device limit counts activated devices, not simultaneous use: with a limit of 8, a 9th computer cannot activate while 8 are activated, even if all 8 are idle, until someone frees a seat with deactivate or on the device page at /licenses/manage.
For a small team that is sometimes enough. Create one license with activation_limit set to the number of machines and let people move seats by hand. If your customers need real checkout and return, a dedicated license manager, or a server you build yourself, fits better. See license server and seat.
Questions
What happens when all floating seats are in use?
The next user is refused or queued. The app shows a message such as "no seats available" until someone quits or their lease expires.
Does a floating license work offline?
Not by default, because the seat is checked out from a server. Vendors that support offline work add a borrow period, where a seat is held by one machine for a fixed number of days.