Close this search box.

Reprise Blog

Reprise Software Blog – Your Hub for Licensing Solutions Insights
Stay informed about our products including Reprise License Manager (RLM), RLM Cloud, and Activation Pro. 


Learn from our customer success stories, understand the intricacies of different licensing models, and keep up with our ongoing service upgrades.

Licensing and Pricing Strategies for “Short Duration” Applications

Short Duration Apps

Many valuable software tools that require floating licensing run for only a short time. These include various solvers, development and design tools, and other specialty software products designed to perform specific tasks quickly. Unlike typical interactive or desktop applications, these short-burst applications typically do not have a GUI of their own, but are often launched by other applications within a product suite. 


Licensing Challenge

The licensing challenge is based on the fact that a floating license is a shared license. When a floating license is used it is unavailable until it is returned. But, short duration tools consume licenses for only a short time, so a single license could potentially be shared by a large number of users.


The licensing challenge is really a pricing challenge. How do you set a price for a single floating license that is low enough for small sites to afford while at the same time scaling your pricing so that larger sites that use more of your software pay you more for that use? How do you prevent large sites from satisfying their requirements by licensing only a single floating copy of your software?



An outdated approach would be to revert to node-locked licenses tied to each workstation or user. Although this would solve the problem, the vendor and end customer would be inconvenienced by having to create, install and manage N licenses for N users. This is very inefficient.


Customers prefer to float licenses to users who need them.


Extra Hold Time

stopwatchOne way to handle this problem is to implement an extra hold time on the floating license. This holds the license for an extra number of seconds after it is released, regardless of how long the license was actually used. So, for example, if the application uses the license for 20 seconds, upon termination of the program the license is held for an additional 300 seconds, say, for a total of 320 seconds. The effect is that the floating license can be shared by fewer users because it is “busy” for a longer period of time each time it is used. This encourages customers to order more licenses to satisfy their user population. But, some customers may object to the license being unavailable for such a long time.


Minimum Checkout Time

Another similar method is to enforce a minimum license checkout duration. Instead of extra time being added to the end of a licensing session as in the above example, a license would be held for at least a specified minimum amount of time. So, a license with the minimum checkout time set to 300 seconds would add 280 extra seconds to a license that was in use for only 20 seconds. Licenses used for more than 300 seconds would not be affected.


Both extra hold time and minimum checkout time should be specified in the license file, external to the application, so that the same executable can use either method without modification to the source code.


Post-use Billing

Since the ultimate goal is for the vendor to get paid an amount that is proportional to the value derived from the customer’s use of the software, you may want to introduce a metered or pay-per-use approach based on actual usage time. A post-use billing model allows a customer to use as much or as little of the software as he wished, with no artificial licensing constraints. The vendor and customer would agree not on a per copy price, but on a per hour price. Periodically, say once a month, the user submits a report generated from the license manager’s transaction log file that summarizes usage time. The user can add their own constraints to the licenses to prevent exceeding a certain budget, but both the customer and the vendor would be satisfied.


RLM can handle these approaches, so please contact Reprise Software to discuss your needs in more detail.

Other Posts

Guide on How To Create Software Licenses With Reprise License Manager

Managing and distributing software licenses can be challenging. But with the right tools and guidance, it can become a streamlined part of your distribution process. This comprehensive guide will walk you through how to create software licenses with Reprise and direct you towards the rich

A Complete Guide to Metered Licensing with RLM

Understanding metered licensing through Reprise License Manager (RLM) can significantly improve the way you manage and pay for software. This guide offers a clear, step-by-step breakdown, making the implementation of metered licensing straightforward and accessible.   What is a Metered License? A metered license is

New RLM Release (v16.0)

The latest major release of RLM is finally here! Version 16.0 brings an all new web interface with many enhancements over the previous interface, and fixes multiple vulnerabilities related to the web interface.     New Features Include: All-new Redesigned UI/UX Most server functions now

Comprehensive Guide on Commercial License Types for Software Publishers

As a software publisher, managing your product licenses is crucial to ensuring revenue and protecting your intellectual property. Commercial license managers, such as Reprise License Manager (RLM), provide you with the tools to control the use of your software licenses through various license types.  

Upgrading Our Service: Transitioning to Amazon Web Services

As part of Reprise Software’s ongoing commitment to providing top-tier service and experiences, we are excited to announce a significant upgrade to our hosting infrastructure. In our constant quest for improvement, we have decided to migrate our hosted services to Amazon Web Services (AWS), a

New RLM Release (v15.2)

We are excited to announce the release of RLM v15.2! Version 15.2 adds new platform support and fixes a number of bugs. We have also introduced a new online documentation platform on our website.   Added platform support ensures your customers can run RLM on

RLM Maintenance Release (v15.1BL2) 

We have released a maintenance update to RLM v15.1BL2. This release primarily addresses a critical security vulnerability in the Mongoose web server.   If you have already updated to v15.1, we strongly recommend updating to v15.1BL2.   In addition to addressing this vulnerability we have

Activation Pro

What’s the difference?

Reprise License Manager (RLM)

Software License Manager

RLM provides runtime checking that verifies that your application is licensed to run and that the current usage of your application is within the limits you have ser every time your application runs.

As a Software publisher, you integrate RLM into your product, and RLM keeps track at runtime of who is using the licenses of your software.

RLM can do this entirely within the client library (linked into your application), or, more commonly, your application makes a request of the RLM Lincese Server to check out a license.

The lincese server runs either on your customers network, or in the cloud if you are using our RLMCloud™ service.

RLM provides runtime checking that verifies that your application is licensed to run and that the current usage of your application is within the limits you have ser every time your application runs.

RLM Activation Pro

Software Activation Manager

Activation Pro is
used once when your customer purchases your software in order to retrieve the license which is specific to that customer.

Software Activation’s purpose in life is to get the licenses for your product to your customers with a minimum of fuss.

Activation Pro also has a server component wich we call the activation server.

Your application contacts the activation server and supplies a short text activation key, and in exchange, the activation server returns the license which enables your product.

Generally, this is done once, right after your customer purchases your software, not every time your software is invoked.