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.

Datamine Software Case Study

Interview with Joshua Knight, Software Developer, Datamine Software.

 

Challenge

For over 40 years, Datamine has delivered a wide range of integrated mining and exploration software solutions that improve and maintain quality data across the entire value chain. With local offices in 20 countries, their groundbreaking technology services customers from all over the world.

 

After relying on their own proprietary software licensing solution, they needed licensing software that provided flexibility and customization for their Discover product without all the headaches that come with it.

 

Decision Process

Joshua Knight, a software developer for Datamine was tasked with finding a simpler, more streamlined solution for Discover’s software licensing. They didn’t want to deal with calls from customers to troubleshoot their licensing issues. Knight added, “We need to be focused on delivering value to our customers instead of the licensing.”

 

Reprise software licensing seemed straightforward and transparent, while other competitors made the integration process more complex.

 

Other solutions forced their customers to do things their way. Datamine’s customers can be one-person enterprises or large, multi-national companies on a cloud server, so lack of flexibility was a major drawback.

 

“Sometimes we have people in the middle of the desert or a jungle in Africa, that can’t connect to the web,” Knight said, “Reprise made it easy to take things offline in those scenarios.”

 

Reprise’s excellent reviews and outstanding reputation made choosing them an easy decision.

 

Solution and Results

Implementation was straightforward and drama-free. Within a few weeks, Reprise was up and running.

 

In addition to flexibility, Datamine’s Discover team also appreciated Reprise’s ease of use, customer support, thorough documentation, and wide range of products.

 

Now they can focus on what they do best and let Reprise take care of the licensing for them.

Other Posts

Tecplot

Saving Time and Eliminating Frustration with RLM Activation Pro

One advantage of Reprise Software joining Vela Software’s STEM portfolio in late 2021 is our partnership with many sibling companies who utilize RLM. This relationship gives us the opportunity and obligation to use our own products in a number of different software licensing scenarios –

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.
UNH InterOperability lab logo over abstract communication background

UNH InterOperability Lab Values RLM for Software Licensing

RLM effortlessly allows software vendors and customers to change licensing models by simply changing the content of the license file itself. This allows software vendors to focus on usability and supporting the customer in configuring the floating license server itself.
U-RENDER logo over their rendering of a red sportscar

U-RENDER Accelerates Time to Market using Reprise License Management

RLM stood out as a hassle-free and flexible solution for node-locked and floating licenses. When U-RENDER started evaluating different solutions for their own software product, RLM was already at the top of the list.
Photo of fossil in a rock

StrataData Consolidates its Licensing Around RLM

Using RLM, StrataData migrated to a more flexible licensing model which seamlessly integrated their existing dongles for those that wanted to retain them, as well as provide all the benefits of floating, server-based licensing.
Futuristic green and blue technology background behind the InSync Technology logo

Reprise Licensing for InSync Technology Ltd

Case study: Short-duration licenses can be generated for demo versions of FrameFormer, allowing InSync customers to try out InSync's motion compensated standards conversion before they purchase the full license.

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.