L I C E N S I N G
Subscriptions , Courtesy of CodeMeter
More and more software developers are reaching out to Wibu-Systems with their vision to offer their software by subscription . This sounds straightforward , but a quick conversation often reveals that people have very different ideas about how a subscription system should work and how their existing sales systems might affect its eventual character . The good news is that CodeMeter offers an effective solution for any type of subscription model we have encountered to date .
The Technical Underpinnings A look at the technology behind a subscription model shows that it can indeed be a simple and elegant solution if CodeMeter is given an opportunity to work its magic . In essence , CodeMeter simply has to be integrated into the software , and CodeMeter Runtime takes care of everything else . It does not matter whether CodeMeter was integrated automatically using CodeMeter Protection Suite or manually via our Core API .
A typical subscription model uses a time-limited license , i . e . the end users need to get their licenses renewed to continue using their software , which they can either do by buying an extension to their subscription or by having a contract in place to do so in the background . Licenses can be set to expire by configuring an expiration date in the license options . As long as that date is still in the future , the license can be used ; when the expiration date arrives , it cannot . Software can , of course , include a mechanism for checking the expiration date and either starting an automatic renewal process or reminding the user to do so manually .
Technically , subscriptions end when the expiration date is not re-set and the license automatically becomes invalid at the end of the active date .
Unlimited Licenses ? An alternative to temporary , regularly renewed licenses is offered by unlimited licenses : The users can use their licenses for as long as their subscription is active , without having to update their license . Only when they cancel their subscription would the license be turned into a temporary version that expires with the end of their contract .
The advantage of this approach is that it avoids all possible disruptions relating to the regular license renewals . But it also comes with drawbacks : Users might find a way to stop their licenses from being turned into temporary , expiring licenses to keep using their software even after their subscription ends . Subscrip- tions based on temporary licenses also make life easier if there are any hardware problems . If a license is lost in this way , the vendor can simply re-issue it and does not have to worry about fraud and malfeasance , because only allegedly lost licenses that a user wants to keep using illegitimately would expire soon enough . The risk is far greater with unlimited licenses , which might be in use for a long time after their purported “ loss ”.
The Users ’ Perspective The most convenient way to renew temporary licenses is a simple activation mechanism that works in the background , e . g . every time the software is launched . This requires the system to be online . If there is no way for the software to automatically check for updates and renewals over the Internet , push updates are an alternative , as they need little input from the user : The vendor can create a license update for the users ’ CmContainers , which is emailed to the users . They simply have to download it and can continue to enjoy their software . Alternatively , the files required
9