Choosing the right licence model for your product is one of the most important business decisions you are going to ever make. Because it is so key, it is not something that should be defined or constrained by a licensing engine.
Instead, that engine should support whatever licence model you want to deploy. Up until now, device-based licensing typically shoehorned businesses into choosing a licence model that 'kind of works', but isn't optimal.
In today's online, multi-app, multi-device world, you need to ensure your applications are backed by a licensing engine that can support the licence model that you think is going to maximise your revenue. It also needs to be able to be flexed or adjusted dynamically, on the fly, in order to help keep your products relevant in today's fast-changing world.
Is your South American sales team telling you that you need to give a key customer a 60-day trial licence? Do you want to test the impact of an aggregate use time licence model with a new customer who isn't sure just how much they are going to use your application?
You'll need a licensing engine that can support this kind of flexibility to stay competitive.
A single user FDL will allow the customer to use the licensed software for a determined period of time.
A perpetual licence model will allow the customer to use the licensed software indefinitely. Perpetual licences contain the date of purchase.
Company ABC buys a 1-year Product X licence. Multiple authorised employees can use the licence on several different machines, but Product X will only run on one machine at a time.
Company ABC buys 365 days of Product X to use over a 1-year period. The agreement includes a minimum and maximum licence duration an employee is allowed to take at a time.
A licensee can access a particular application a certain number of times before their access is throttled and they are asked to subscribe/licence.
A user can check-out a licence for a defined period of time and not required online access.
A specific set of users can access a product based on a defined whitelist. Ideal for product testing with select users.
A limited number of licenses for a software application are shared among a larger number of users over time. When an authorized user wishes to run the application they request a license from a central pool.
A licensee licences a total amount of time that can be spent using a product. This time allocation can be consumed by any number of users, but when it runs out, access to the licensed applications ends.
The main license can be purchased by a customer from the licensor and then entitlements to access the licensed application can, in turn, be granted by the licensee on to project team members, even if they are part of a different company or organisation.
If you'd like to learn more or have a licence model in mind that's not listed below and are wondering if we support it, or you're just not sure what licence model would work best for you, please get in touch.
Choosing the right licence model is one of the most important business decisions you are ever going to make, and it should not be defined or constrained by a licensing engine.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.