This is my first post on this forum.
Our development company has been intermittently using Cryptlex in our software for a few years, for node-locked subscription licenses only. We are happy with the functionality Cryptlex has provided so far.
We now are facing a new scenario. I now reach out to better understand whether hosted floating, node-locked multi-seat, or something else could be a good fit for us in this particular scenario.
Let’s say we are developing a custom software for a client organization with around 100 individual end users. Over a year, there may be an employee turnover of say 10 percent. All employees have internet access. Some work from home, and use VPN or similar to access centrally shared resources.
The organization will install our custom software to all end users centrally, via Azure, Windows Active Directory or similar. Same for software updating.
In this particular scenario, the client organization wants a super-easy way of consuming licenses or seats for their end users, and emphasizes that their typical end user is not tech savvy at all. The client organization does not want to make end users have to activate individual licenses by copy-pasting an emailed license key.
Since all software installation will be done centrally, I think it is acceptable to:
Agree one single common license period for all seats, typically 1 year from issue.
Ship a software with a built-in license key validation. At first-use button-click, the software will automatically activate and consume a seat, and keep it consumed for the entire license period.
We developers want to:
At any given time see how many seats have been consumed in the current license period, so we may bill the client organization per seats used.
Be able to seamlessly extend the license period, if the client organization wishes to renew the software, and thus make the current seat count reset.
Preferably receive an email in case the the number of consumed seats in the period reaches a set target, so we may manually add more seats.
At first, we thought that a floating license model with a lease period of say 365 days would be best. However, if the client organization does not want individual end users to validate by individual keys, and we only care for counting unique users during a period, and not concurrent users, then a multi-seat node-locked license may perhaps be simpler.
Cryptlex – What solution would you advise that we implement, and why?