How it works
The vendor sets a number, say 10. Any number of people may have the software installed, but an eleventh simultaneous session is refused. The count is enforced by something that sees all sessions at once: a license server on the customer’s network, or the vendor’s own service for a web app.
What counts as a session is a policy choice that the vendor has to state: the app being open, a document being open, or a user being active in the last N minutes. Two windows on one computer might be one session or two. Say which, in the license terms and in the error message.
Floating and concurrent
In practice the two words are used almost interchangeably, and you will find both on the same price list. If you want a distinction, it is this. Concurrent is about the cap metric: simultaneous sessions. Floating is about delivery: the seat is not locked to one machine, so it floats between them. Most floating licenses are concurrent, and a web app can enforce a concurrent cap on named user accounts without any floating machinery. See floating license for how checkout and heartbeats work. The difference is one of usage, not of law.
Worked example: 50 employees, peak of 10
A company has 50 employees who may need the tool. Over four weeks of logs the highest number using it at once is 10. They buy 12, which is the peak plus 20 percent headroom. All numbers are an example.
- Named seats: 50
- Concurrent seats: 12
- Break-even price: 50 / 12 = 4.17
A concurrent seat is worth buying as long as it costs less than about 4.2 times a named seat. Above that, the 50 named seats are cheaper. The same arithmetic shows the seller’s risk: a company with a low peak pays little, so concurrent seats are priced higher per seat than named ones.
Concurrent versus a device limit
A device limit counts installs that have activated. It does not care how many run together. A concurrent license does the opposite: it ignores installs and counts running sessions. The two answer different questions, so a seller sometimes uses both, a concurrent cap for the team and a device limit per user.
How Clavem handles it
Clavem does not offer concurrent licenses. The License API has no session, checkout or heartbeat, and it does not know whether an activated device is running. Its limit is activation_limit, the number of devices that may be active on a key at once, and an activation stays until someone removes it. See activation.
If your customers are companies who want to cap simultaneous use, a purpose-built license manager fits better. If they only want one price for many people, see site license and seat.
Questions
Is a concurrent license the same as a floating license?
Vendors use the two words for the same thing most of the time. Strictly, concurrent names the cap on simultaneous use and floating names the fact that the seat is not tied to one machine.
How do I decide how many concurrent seats to buy?
Measure the peak number of simultaneous users over a few busy weeks, then add some headroom. Buying for the average leaves people waiting at peak.