Licensing models and floating licenses
Device-bound keys, floating seats, subscriptions and perpetual access explained
Software licensing has separate decisions: who may run the product, on how many devices, for how long, and whether a connection is required. A subscription can be device-bound; a perpetual license can use a shared pool. Choose each rule deliberately instead of treating every model as interchangeable.
License models compared
| Model | What it limits | Example |
|---|---|---|
| Node-locked / HWID-bound | Authorized devices | One purchased key belongs to one workstation. |
| Named user / seat | Assigned people or accounts | A team purchases access for five named members. |
| Floating / concurrent | Simultaneous use from a shared pool | Twenty employees share five concurrent seats. |
| Time-limited / subscription | Duration of access | Access ends after the paid period unless renewed. |
| Perpetual | Usually a purchased version or defined entitlement | Use has no scheduled expiry; updates and support may have separate terms. |
How floating licenses work
A floating license service maintains a pool with a concurrency limit. When a program starts, it requests a seat. The service grants one if capacity remains. The program renews its lease while in use and returns the seat when it exits; a timeout recovers seats after crashes or lost connections.
- A company purchases five concurrent seats.
- Five employees check them out and begin work.
- A sixth request waits or is refused according to the product's policy.
- One employee exits and releases a seat.
- The next employee can now start without buying a sixth seat.
This differs from allowing five registered devices. A device allowance counts machines that have been bound to a key; a floating pool counts active leases. Closing an application does not necessarily remove its device binding.
What PWF Auth supports today
PWF Auth offers keys bound to one or more machines, with a configured allowance of up to 100 devices per key. It also supports customer accounts, time-limited keys and lifetime keys. The duration of an unused key starts on its first sign-in. See license key management and customer accounts.
The SDK maintains an online session with periodic heartbeats. You handle its session-ended event to stop protected work after a refusal. A brief network interruption follows the SDK's retry policy; it does not turn an online key into a permanent offline license. See session and heartbeat behavior.
Choose the model your customers can understand
- Independent desktop customers: a device-bound key with a clear reset policy is straightforward. Explain what happens after a PC replacement.
- Shared workstations or shift teams: ask whether the customer needs a floating pool, named seats or simply more authorized devices.
- Restricted networks: establish how long the software must run without contacting your service and whether a local license server is necessary.
- Subscription products: define renewals, grace periods and cancellation behavior separately from payment collection.
- Perpetual products: explain whether the purchase includes future versions and support. A lifetime key alone does not define those commercial terms.
Common questions
Is a seat the same thing as a device?
Not necessarily. A seat may refer to a named person or a concurrent user. Specify the counting rule in your product and sales terms rather than relying on the label.
Does allowing several PCs create a floating license?
No. In PWF Auth, the key retains its bound machines until a reset or unbinding action. That is different from automatically returning a concurrent seat when a session ends.
Does lifetime mean the app never needs a server?
No. Lifetime describes the key's expiry. PWF Auth's lifetime keys still use the online authentication and heartbeat flow.
Next: design the device reset experience, integrate the licensing API, or compare build and integration costs.
Something missing or unclear? Tell us on Telegram