Search
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.

A Kinder, Gentler Licensing Strategy

Provide your customers with the tools to stay compliant

For three decades, software vendors have relied on license managers to control their customers’ use of their high-value software applications to ensure compliance with their license agreements. Today enterprise software vendors view license management not so much as a service-denial mechanism, but as a valuable built-in tool. A tool that helps customers stay compliant and gain a more accurate understanding of their software usage.

 

Balancing vendors’ and customers’ needs

Software users just want to get their work done. Software vendors do not want to limit a user’s ability to access their software. At the same time, vendors expect fair compensation for that use. End-users generally do not want to exceed their license rights (especially now with tighter internal financial compliance rules in place). Unfortunately, end-users rarely know what those rights are, making it nearly impossible to stay compliant.

 

Some software vendors deploy a strict denial-of-service policy. When the license server is not accessible or is not running correctly, users may find their software unavailable. Fixing that situation may require costly intervention from the software vendor. Publishers can decide how strictly to enforce their licenses by the way that their software behaves when they are not available. But what strategy should vendors adopt to strike the right balance between their needs and those of their customers?

 

Letting Customers Police Themselves

The goal is an implementation strategy for license management that provides customers with all the licensing system components. These parts enable customers to control their software usage without burdening those customers who don’t. 

 

A strategy like this is a win for both end-customer and vendor alike because:

  • Your customers do not need 3rd party software to control usage – it’s built-in, lowering their total cost of ownership.
  • The transparency of the system makes clear to both customer and vendor what is meant by a “user” and a “license.”
  • Your customers have everything they need to comply with your license agreement, so they should never be out of compliance.
  • The “always available” license policy saves you from the care and feeding of the licensing system when your customers move/change license inventory or network.
  • Detailed license activity logs can be used to produce audit reports if necessary.

 

How is this strategy implemented in RLM?

It’s simple. When your software tries to check out a license, it runs as expected unless “all licenses in use” is selected. In that case, users may choose to continue using the software even if they exceed their company’s current license allotment. All other licensing failures should result in a message to the user, but allow the user to continue to run. So if the licensing system is not installed, or is not running at the time the user requests a license, they will be able to continue to run.

 

Is this licensing scheme for me?

Maybe, maybe not. This implementation works best for widely shared products, such as desktop productivity tools, utilities, framework, and collaboration products. Products with a higher “per seat” value might benefit more from the more common (stricter) licensing strategy.

 

No single licensing implementation works across all product categories, but a license manager, such as RLM, is the best tool to provide the flexibility to cover the full spectrum of license enforcement models – from “very strict” to “self-compliant,” as we have discussed here.

 

If you want to discuss which licensing strategies are best for your business, please contact the experts at Reprise Software.

Other Posts

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 available directly

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.  

Put Your License Servers in the Cloud with RLMCloud

Put Your License Servers in the Cloud with RLM Cloud

What if your customer doesn’t want his server in the cloud? No problem, because you can use any combination of RLMCloud-based servers and on-premise servers that you wish.
Peregrine Labs Moves to RLM to Build Better Products

Peregrine Labs Moves to RLM to Build Better Products

Peregrine developed a small toolset for tracking usage internally, but they needed help from a third-party solution so they could concentrate on building better products instead of trying to maintain licensing.
Lixoft Logo in front of an abstract medical background

Drug Development Company, Lixoft, Uses RLM

A drug development company, Lixoft, uses RLM Cloud for annual license renewals.

Dealing with Activation Read Timeouts (error -105)

On rare occasions, an activation request will get a read timeout status return (-105). There are several causes to the RLM_EH_NET_RERR (-105) error.   If you can activate from some systems, then the first cause (server down) is unlikely.   More likely is that there

How to Set Environment Variables

Environment variables are flags that you set outside an application that the application reacts to. Applications and libraries like RLM read environment variables that they define. Some RLM environment variables are RLM_ACT_TIMEOUT (adjusts the timeout to the activation server to the value supplied), RLM_QUEUE (enables

RLM and RLM
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.