Start free trial

Floating and concurrent licenses for desktop software

A floating license is a pool of seats a team shares: the license sets how many copies may run at the same time, and anyone may take a seat until the pool is full. Carcha Seal issues a short-lived, signed seat token the app holds while it runs and gives back when it closes, so the next person can take the seat. It works against your hosted account or a server you run yourself.

Reading time
6 min
Updated
11 November 2026
Sections
7
On this page
What a floating license isWhat one seat isHow a seat is heldManaging the poolWhat version 1 does not doHosted or self-hostedQuestions

What a floating license is

A floating, or concurrent, license is a pool. The seat count is how many copies may be in use at the same moment, not how many computers are installed. A node-locked license is the other model: there a seat is one fixed computer. A policy is one model or the other, and the seat count is read the right way for each.

  • Seats. A number, or unlimited. The pool allows that many concurrent uses; the next request waits until a seat frees.
  • Shared across the team. Any machine may take a seat; nobody is tied to one. This fits a shared workstation, a lab, or a floating pool across an office.
  • The same license, features and dates. Expiry, features, the maintenance window, the virtual-machine rule and the license status all apply to a floating license as they do to a node-locked one.

What one seat is

You choose what the pool counts, so a seat matches how your product is used.

Counted byOne seat isGood for
MachineOne computer in use at a timeThe default: a desktop tool used one person at a time.
Running copyOne running instanceA tool a user may open several times, each counting.
UserOne named user, on any machineA person who roams between computers but uses one seat.
User on a machineOne user on one machineShared machines where each user-and-machine pair is a seat.

A user name is sent only as a salted hash, so the pool counts people without the server keeping their names in the clear.

How a seat is held

  1. On start, the app checks out a seat. The server returns a seat token: a short-lived, Ed25519-signed token, like the lease, naming the pool and the seat.
  2. The app renews the seat about halfway through its life. A seat's lifetime is set by the policy, from a minute up to a day, ten minutes by default.
  3. On close, the app releases the seat and it is free at once for the next user.

A seat token lives in memory only, never on disk, and its life is measured on a monotonic clock, so moving the device clock cannot stretch it. An app that crashes or loses the network sends nothing; its seat frees itself when the token expires, so a seat is never stuck on a machine that has gone away. There is no stored fallback and no offline grace for a seat: that is what keeps the concurrent count honest.

Managing the pool

  • See who is in. The console shows the seats in use now, and keeps the highest number in use each day, so you can see your real peak against the pool size.
  • Free a seat. Free any seat from the console; the machine holding it loses it at its next renewal.
  • Full pool. When every seat is in use, a checkout is refused with the number in use, the total, and the seconds until the earliest seat frees, so the app can wait and retry.
  • Stop sharing. A seat can be tied to the device with a key it proves it holds on every renewal, so one license key cannot be run on more machines at once than the pool allows; a copied or replayed token is caught.

What version 1 does not do, stated plainly

Floating is a concurrent-use model, and it is online by nature. We say what it does not cover so there is no surprise:

  • A floating seat needs the server. A seat is held only while the app can reach the server to renew it. Unlike a node-locked lease, which keeps working through a grace period with no network, a floating seat has no offline grace: lose the connection past the token's life and the seat is released.
  • No floating server at your customer's site yet. Version 1 has no license server that runs inside an air-gapped or offline network to lend floating seats, and no seat borrowing for laptops taken off the network. Machines with no connection use a node-locked license activated by file instead.

If offline or air-gapped concurrency is a hard requirement today, node-locked offline activation is the model that fits; floating suits teams whose machines reach the server while they work.

Hosted or self-hosted

Floating works the same way whether the pool lives on your hosted Carcha Seal account or on a server you run yourself. The seat tokens are signed with your own key, and the pool, the counts and the daily peak are yours. The SDKs for Electron and Node.js, .NET and C++ all take and renew floating seats.

Questions

How many copies can run at once?

As many as the pool has seats. The seat count is the number of concurrent uses, set per license; it can be a fixed number or unlimited.

What is a seat counted by?

By machine, by running copy, by user, or by user on a machine. You choose it on the policy.

What happens if an app crashes?

Its seat frees itself when the seat token expires, because a crashed app stops renewing. Nobody has to free it by hand.

Does floating work offline?

No. A floating seat needs the server to renew it and has no offline grace. A machine with no network uses a node-locked license activated by file instead.

Can one key be shared across many machines?

Only up to the seat count, and you can tie a seat to its device so a key cannot run on more machines at once than the pool allows.

Software license types · What an entitlement holds · Self-hosted license server

Sources

What floating licenses do in Carcha Seal is taken from its server code, the floating-license specification and documentation, checked on 11 November 2026.

Give your team a pool of seats.

14-day trial, no card. Floating or node-locked, hosted or on your own server, from the first minute.