Watch more videos about how to license your software and increase revenues
1000s of software companies have used Zentitle to launch new software products faster and control their entitlements easily, many going from startup to IPO on our cloud software license management solutions
Zentitle - the Enterprise-Class Software Monetization Platform
Transactions / Month
Uptime SLA for 10 Years+
Zentitle supports 100M's users 24x7x365 for the world's leading SaaS, Software and IoT companies
Your long-term partner for software business growth
Zentitle meets the standards for scale, security and operational excellence demanded by enterprise-class software companies
From startup to $1Bn in ARR partnering with Nalpeiron
Partner for 8 years
From startup to VC funding to IPO for millions of users, all on Zentitle
Partner for 14 years
The concept of a floating feature kinda layers on top of the concept of a concurrent or floating license seat. And so, for example, in a given application, you may have a 10-seat license.
And so that will allow any ten people in that end-customer organization to access the application at any point in time. So that's great. However, there may be some add-on functionality, let's say some sort of advanced reporting or some sort of pro mode or something else. And the customer, the end customer wants to be able to dynamically switch into that additional functionality on demand, but maybe they don't need it across all ten users. So what floating features allows you to do, and you can have as many of these floating feature pools as you want is you might sell five seats of some add-on feature.
And so what that then allows. Any of those ten customers to do is they'll activate, they'll get a session with that application. And then through some gesture in your in your application, you'll attempt to check out a seat of that add-on floating feature that represents this advanced functionality of whatever you choose to to mean it to be. And then if they get access to that floating feature seat. They'll you'll unlock that capability within the application. They'll make use of it, and they can then check that feature back in when they're done with it, allowing that same seat of that feature to be used by the other ten users in that environment.