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.

The Licensing of Sub-Licensed Tool Kits

How Do ISVs License Their Products in Library Form?

Many independent software vendors (ISVs) who sell their products as complete applications also sell them as re-linkable libraries. Licensing the applications is pretty straightforward, but what about the libraries? How do ISVs tackle licensing of libraries?


Most of the companies that we’ve talked to who have libraries to license want to use a license manager to enforce their pricing models. They also want to have the flexibility to turn on and off certain features within the library. ISVs who ship software development toolkits (SDKs) that are designed to be incorporated by your customers into sub-licensed products usually do not want licenses to be required in the derivative applications. However, they may still want a way to enable each sub-licensee with a unique license key.


License “In-A-String” Concept

The Reprise License Manager (RLM) addresses licensing of SDKs by supporting a license “in-a-string” concept. This approach allows ISVs to sell licenses in the form of digitally signed text strings that are passed as parameters into their library’s initialization routine. During initialization, the license is then passed as a parameter into RLM’s initialization routine for validation. This means that only products that are built with a valid license string will successfully initialize the library. Often, ISVs will also include the customer’s name or contract number in the license for identification purposes.


Since the initialized library has access to the contents of the key internally, the library can call RLM as it would normally to check out feature licenses, without the need for a separate disk based license file.


Keep it Simple

An important additional benefit of this approach is the simplification of back office administration, since the same methods and tools that you use to create licenses for your standard licensed applications can also be used for your licensed libraries.


Please feel free to contact us to discuss your situation further.

Other Posts

Floating Licensing Explained: A Practical Guide to Efficient Software Management

Software licensing can be complex, but understanding different models can help organizations manage their resources more effectively. This guide focuses on floating licensing, a flexible approach that can optimize software usage and reduce costs for many businesses.   What is a Floating License?   A

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

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.