What is a floating license?
A floating license (also called a concurrent license) lets multiple users share a limited pool of licenses. Instead of tying a license to a specific person or machine, you buy a certain number of "seats" that anyone in your organization can use; just not all at the same time.
Think of it like a co-working space with 20 desks. You might have 50 members, but only 20 can work at once. That's fine because not everyone shows up on the same day. Floating licenses work the same way: 50 people might have the software installed, but only 20 can use it simultaneously.
How floating licenses work
Here's the typical flow:
- Your company buys 10 floating licenses for a piece of software
- Users across the company install the software on their machines (could be 30, 50, or 100 installations)
- When someone launches the app, it "checks out" a license from the pool
- If all 10 licenses are in use, the 11th person sees a "no licenses available" message
- When someone closes the app, their license returns to the pool for others to use
This happens automatically through a license server that tracks active sessions. The server can be cloud-hosted (like LicenseSeat) or installed on-premise in your company's network.
The technical details
Behind the scenes, floating license systems use several mechanisms to manage the license pool:
Heartbeat monitoring – The client application sends periodic signals (every 30-60 seconds typically) to confirm it's still active. If the server stops receiving heartbeats, it knows something happened.
Automatic release on timeout – If a user's computer crashes or loses network connectivity, their heartbeats stop. After a configurable timeout period (say, 5 minutes), the license automatically returns to the pool.
Grace periods – Brief network interruptions shouldn't kick users out. A grace period (typically 1-2 minutes) allows for temporary connectivity issues without releasing the license.
Session tracking – The server maintains real-time records of who has which license, when they checked it out, and from what device.
Floating license vs node-locked license
The main alternative to floating licenses is node-locked (or machine-locked) licensing, where each license is permanently tied to a specific computer.
| Aspect | Floating license | Node-locked license |
|---|---|---|
| Tied to | Pool of concurrent users | Specific machine or device |
| Installation limit | Unlimited installations | One installation per license |
| Cost efficiency | High when users don't overlap | 1:1 ratio with machines |
| Administration | Requires license server | Simple one-time activation |
| Network requirement | Needs connectivity to license server | Can work fully offline |
| Hardware changes | No impact on licenses | Requires deactivation/reactivation |
| Best for | Teams, shifts, occasional use | Individual users, always-on systems |
When floating licenses make sense
Floating licenses are ideal when:
- Users don't all need the software simultaneously
- You have shift workers or teams in different time zones
- The software is used occasionally, not continuously throughout the day
- You want to minimize license costs for large organizations
- Users work from multiple devices and locations
When node-locked licenses make sense
Node-locked licenses work better when:
- Each user needs guaranteed, dedicated access
- You're licensing to individuals rather than organizations
- The software runs continuously on specific machines (servers, render farms)
- Offline operation is essential
- You want simpler administration without a license server
Advantages of floating licenses
Significant cost savings – A company with 50 employees might only need 15 floating licenses if peak concurrent usage never exceeds 15. That's 70% savings compared to buying 50 individual licenses.
Access from anywhere – Users can launch the software from any device. Work from the office, home, or a laptop while traveling; as long as there's a license available, you're in.
Simplified onboarding – New employees don't need individual licenses purchased and assigned. They just install the software and use the shared pool.
Flexibility for changing teams – As teams grow, shrink, or reorganize, you don't need to reassign licenses. The pool automatically accommodates whoever needs it.
Usage visibility – License servers provide analytics on actual usage patterns, peak times, and utilization rates. This data helps right-size your license count.
Challenges of floating licenses
Peak capacity conflicts – If everyone needs the software at the same time (quarterly reports, deadline crunches), some users will be locked out. This requires either buying more licenses or coordinating usage.
Network dependency – Users need network connectivity to the license server. Fully offline work isn't possible with standard floating licenses (though some systems offer temporary offline checkout).
Potential workflow disruption – Being told "no licenses available" in the middle of a workday is frustrating. Good capacity planning minimizes this, but it's still a risk.
License server infrastructure – Someone needs to run and maintain the license server. Cloud-hosted solutions like LicenseSeat eliminate this burden, but on-premise servers require IT resources.
Floating license vs standalone license
Some vendors use "standalone license" to mean a license tied to a specific user (rather than a machine). Here's how that compares:
| Aspect | Floating license | Standalone (user-based) license |
|---|---|---|
| Assignment | Shared pool | Assigned to specific user |
| Concurrent use | Limited by pool size | One user, potentially multiple devices |
| Cost model | Pay for peak concurrent users | Pay for total user count |
| Administration | Monitor pool utilization | Manage user assignments |
A standalone license is like a reserved seat at a restaurant; it's yours whether you show up or not. A floating license is like a first-come-first-served café; you get a seat when one is available.
How many floating licenses do you need?
This is the key question, and the answer depends on your usage patterns. Here's how to figure it out:
Track actual concurrent usage – Before switching to floating licenses, monitor how many users actively use the software at the same time. Most organizations find peak concurrent usage is 20-40% of total potential users.
Consider usage patterns – If users need the software for quick tasks (10-15 minutes), fewer licenses work. If users keep it open all day, you'll need more.
Account for time zones – Global teams with users in different time zones naturally spread out usage, reducing the licenses needed.
Plan for peaks – Identify busy periods (month-end, project deadlines) and ensure you have enough licenses. Some vendors allow temporary license increases for predictable peaks.
Start conservative, then adjust – It's better to start with slightly more licenses than you think you need. Running out frustrates users. You can always reduce later once you have usage data.
Rule of thumb – For occasional-use software, start with licenses equal to 25-30% of your user count. For daily-use software, start at 40-50%. Adjust based on actual utilization data.
Implementing floating licenses with LicenseSeat
LicenseSeat handles floating license management automatically through our cloud-hosted license server. Here's what you get:
Real-time seat tracking – Our license server tracks active sessions as they happen. When a user opens your app, it checks out a seat. When they close it, the seat returns to the pool instantly.
Configurable seat limits – Set how many concurrent users each license tier allows. Sell a 5-seat license to small teams, a 25-seat license to mid-size companies, and enterprise tiers for larger organizations.
Heartbeat monitoring – The LicenseSeat SDK sends periodic heartbeats to confirm users are still active. If someone's computer crashes or they forget to close the app, the seat automatically releases after your configured timeout.
Customizable grace periods – Network hiccups happen. Configure how long to wait before considering a user disconnected, so brief interruptions don't boot anyone out.
Queue handling options – When all seats are taken, you decide what happens. Show a "try again later" message, display estimated wait time, or implement your own queuing logic.
Usage analytics – See peak usage times, average concurrent users, and utilization rates in your dashboard. Share these insights with customers so they can right-size their purchases.
No on-premise server needed – LicenseSeat is fully cloud-hosted. Your customers don't need to install or maintain license server infrastructure.
Offline considerations for floating licenses
Standard floating licenses require network connectivity. But some scenarios need offline support:
Temporary offline checkout – Some systems let users "borrow" a license for offline use. The license is reserved for that user for a set period (hours or days), then must be returned. LicenseSeat supports configurable checkout periods.
Hybrid approaches – Combine floating licenses for office users with node-locked licenses for field workers who need guaranteed offline access.
Offline grace periods – If a user loses connectivity briefly, the grace period keeps their session alive. Extended offline work requires either license checkout or a different license type.
Common questions about floating licenses
What happens if a user's computer crashes?
The license server uses heartbeat monitoring. When heartbeats stop, it waits for the configured timeout (typically 2-10 minutes), then automatically releases the seat back to the pool. No manual intervention needed.
Can someone hog a license all day?
You can configure maximum session durations or idle timeouts. If someone checks out a license and doesn't actively use the software for an hour, you can automatically release it. This prevents license hoarding.
Can I mix floating and node-locked licenses?
Absolutely. Many organizations buy node-locked licenses for power users who need guaranteed access, plus a pool of floating licenses for occasional users. LicenseSeat supports both models for the same product.
How do users know if licenses are available?
Your application can check availability before users start working and display current usage. Some implementations show "X of Y licenses in use" so users know the current state.
What about different license tiers with different features?
You can create multiple floating pools with different capabilities. A "Basic" pool might have 20 seats with core features, while a "Pro" pool has 5 seats with advanced features. Users check out from the appropriate pool based on what they need.
Do floating licenses work for SaaS applications?
Yes, though the implementation differs slightly. Instead of checking out licenses when the desktop app launches, you track concurrent active sessions in your web application. The same pool concept applies.
The bottom line
Floating licenses optimize software spending for organizations. Instead of buying a license for everyone who might ever use the software, they buy enough for everyone who uses it at the same time. The result is significant cost savings with minimal workflow disruption.
For vendors, floating licensing opens enterprise sales opportunities. Large organizations are far more likely to buy when they can share licenses across teams rather than justify individual licenses for occasional users.
If you're building software for teams, agencies, or enterprises, floating licenses should be part of your licensing strategy. Combined with node-locked options for individual users, you can serve the full spectrum of customer needs.
LicenseSeat makes floating license implementation straightforward with our cloud-hosted license server, real-time seat tracking, and configurable policies. You focus on building great software; we handle the infrastructure.
For a broader overview of licensing options, see our complete guide to software licensing.