Floating license

Business model

Floating targets organizations that buy concurrent capacity rather than named users or installs—classic CAD, PLM, and license-server economics at scale.

• Enterprise concurrent deal — “100 simultaneous users” for entire company.
• Site license + cap — one key for a campus; server enforces concurrency.
• Department pool — issued-to org label; IT shares one key internally.
• High churn usage — users open/close app often; seats recycle on disconnect.

Benefits

• For vendors — sell higher concurrent tiers; accurate real-time usage via Sessions page.
• For customers — fewer keys to manage; pay for peak concurrency not headcount.
• For enforcement — session heartbeats free seats within seconds of app exit (vs long-lived activation rows).

Logic of use (how seats work)

LicenPro counts live SDK sessions against max active users. When a user starts the app, validation opens a session; heartbeat keeps it alive. When the app exits or heartbeat stops, the seat returns to the pool.

Activations tab is hidden for floating—seats are not tracked via device activation count. Use Sessions tab and /dashboard/sessions for operations.

This differs from Concurrent, which enforces seats on device activations instead of live sessions.

Example lifecycle

Lifecycle stages

1. Issue — type Floating + max active users.
2. Distribute — single org-wide key (+ optional license.bin).
3. Connect — each running app holds one session seat.
4. Heartbeat — maintains seat while app runs.
5. Disconnect — app exit or operator disconnect frees seat.
6. Revoke — entire pool disabled from license Overview.

Dashboard workflow

• Create → Floating → set max active users.
• Monitor /dashboard/sessions and license Sessions tab.
• Disconnect stale sessions; no Activations tab for seat math.

Floating vs Concurrent

• Floating — seat limit on live sessions; always online; best for fast seat turnover.
• Concurrent — seat limit on device activations; sessions show who is online but activations hold seats.