Floating Licenses vs Node-Locked: Which Model Fits Your Software in 2026?

Choosing between floating and node-locked licenses can make or break your software's adoption in enterprise environments. Floating licenses let multiple users share a pool of concurrent seats, while node-locked licenses bind to specific machines. Each model has distinct advantages — and getting it wrong costs both revenue and customer satisfaction.

What Is a Floating License?

A floating license (also called a concurrent license) allows a fixed number of simultaneous users to access the software from any machine. When a user finishes, their seat returns to the pool for the next user.

• Example: A company buys 10 floating licenses for a design tool. Any of their 50 designers can use it, but only 10 at once.
• How it works: A license server tracks active sessions and grants or denies access based on available seats.
• Typical ratio: Companies purchase 1 floating license for every 3-5 potential users.

What Is a Node-Locked License?

A node-locked license binds the software to a specific device — identified by hardware fingerprint, MAC address, or domain. Only that device can run the software.

• Example: A developer buys a node-locked license for their workstation. They cannot use it on their laptop without a separate license.
• How it works: During activation, the software captures a hardware fingerprint and validates it on every launch.
• Variant: Domain-locked licenses bind to a specific domain rather than hardware, ideal for web applications.

Comparison: Floating vs Node-Locked

Factor	Floating License	Node-Locked License
User Flexibility	High — any machine	Low — one device
Cost per User	Lower (shared seats)	Higher (1:1 mapping)
Infrastructure	Requires license server	Self-contained
Offline Support	Limited (server check)	Full offline capability
Enterprise Appeal	Very high	Moderate
Unauthorized Usage Risk	Low (server-validated)	Higher (local validation)
Implementation	Complex	Simple
Revenue per Seat	Higher (premium pricing)	Lower (per-device pricing)

When to Use Floating Licenses

Floating licenses excel in these scenarios:

• Large teams with shift workers — call centers, manufacturing, hospitals where not everyone works simultaneously
• Expensive professional software — CAD, simulation, analytics tools where per-seat cost is high
• Enterprise procurement — IT departments prefer floating licenses because they optimize spend
• Multi-office deployments — global teams across time zones naturally share seats

When to Use Node-Locked Licenses

Node-locked licenses work best for:

• Individual developers and freelancers — one person, one machine, simple setup
• Offline-first software — no need for server connectivity
• Embedded systems — software running on specific hardware (kiosks, appliances)
• Lower-priced software — the overhead of a license server isn't justified

Implementation: Floating License Server

Modern floating license implementations use cloud-based license servers rather than on-premise FlexLM-style daemons:

// Check out a floating license seat
const checkout = await to.validate({
  licenseKey: orgKey,
  type: 'floating',
  userId: currentUser.id,  // Track who has the seat
  timeout: 3600            // Auto-release after 1 hour idle
})

if (checkout.valid) {
  // Seat acquired — user can work
  startApplication()
} else if (checkout.error === 'seats_exhausted') {
  // All seats in use — show waitlist
  showWaitlistUI(checkout.activeUsers)
}

Hybrid Approach: The Best of Both Worlds

Many vendors combine both models:

• Floating for teams — enterprise plans with shared seats
• Node-locked for individuals — personal plans with device binding
• Overflow seats — allow temporary extra seats at a higher per-hour rate
• Offline checkout — let users "borrow" a floating seat for offline work (24-72 hours)

Pricing Strategies

Your license model directly affects pricing:

• Floating licenses typically cost 2-3x more per seat than node-locked, but enterprises buy fewer seats total
• Node-locked prices lower per seat but require 1:1 user-to-license mapping
• Usage-based hybrid: base floating pool + per-hour overage charges
• Annual true-up: analyze peak concurrent usage and adjust seat count yearly