Tag: rlmcloud

technology waves behind three icons of reprise solutions: rlmcloud, rlm teams and activator pro

Entitlement Management Software: How to Pick the Right Solution

Compare Reprise Activation Pro, RLMCloud, and RLM Teams

Reprise Software offers three entitlement management solutions. Each solution addresses similar requirements but in subtlety different ways.

This article outlines the functionality of each to help you decide which is best suited to your software policies and procedures.

Activation Pro

Regardless of the license types that you support—node-locked or floating—Activation Pro makes entitlement management and license distribution more efficient for you and your customers.

The RLM API integrates seamlessly with Activation Pro to enable activation from within your product. Customers enter an activation key to activate their license. The activated license is stored on the user’s computer. Users without an internet connection can obtain a license by using the same activation key on a simple web page to obtain a license.

Activation Pro supports:

  • Trials
  • Paid Licenses
  • Automatic Subscription Renewals
  • Customer-Directed License Re-Hosting

Customers can review their entitlements’ status through portal accounts. Furthermore, Activation Pro supports indirect sales channels via its reseller portal.

A REST-style web services API integrates Activation Pro into your CRM, order management, or e-commerce platforms. You can host Activation Pro on your web server, or Reprise Software can host it for you in the cloud.

RLMCloud

To minimize administrative overhead, software customers sometimes prefer their floating licenses served from the cloud. To address this, Reprise evolved RLM into RLMCloud, allowing customers to checkout software licenses over the internet.

RLMCloud uses standard RLM client and server components to support traditional on-premises license servers and cloud-based licenses within the same application release. RLMCloud is best suited for floating licenses.

Activation Pro delivers licenses directly to customers, but RLMCloud stores them in the cloud. For customers to securely connect to RLMCloud and check out their licenses, all they need is a username and password.

Since RLMCloud puts license servers under your direct control, you can support customers running in virtual machines, dockers, or containers, without the risk of license server cloning. You can also collect usage information for post-use billing and use software meters to tie your pricing to actual work done by your software. In addition, hot standby (failover) license servers are easy to set up on RLMCloud to maximize license availability.

A REST-style web services API integrates RLMCloud to your CRM, order management, or e-commerce platforms. RLMCloud is deployed in data centers in Asia, North America, and Europe.

RLM Teams

Reprise Software’s newest product, RLM Teams, extends licensing flexibility to collaborative groups, letting your customers assign and reassign licenses to themselves or their users from the RLM Teams portal.

With RLM Teams, you provision license entitlements to customer accounts. Customers fulfill their licenses on their computers or reassign them to their team members. Then, when users want to use your product, they log into RLM Teams where a license is generated and “soft-locked” to the user’s computer. Later, the user can log in on a different computer to move the license there.

You can host RLM Teams on your web server, or Reprise Software can host it for you in the cloud.

Below is a comparison table, highlighting the differences between the three solutions:

  Activation Pro RLMCloud RLM Teams
Trials and evals yes yes yes
Subscriptions yes yes yes
Uses HTTPS yes yes yes
Web services management API yes yes yes
On-premises licensing yes, after activation yes, temporary licenses yes, cached licenses
Rehosting yes, using RLM API yes yes
Use while disconnected yes, after activation yes, temporary licenses yes, cached licenses
Requires internet connection yes, initially yes, periodically yes, periodically
24x7x365 yes yes yes
Uses Standard rlm_checkout call yes, after activation yes yes
Uses activation keys yes no no
Floating licenses yes, on-premises yes no
Manage RLM license servers no yes, in the cloud no
License disablement yes, using RLM API yes yes
Personal licenses no yes no
Token-based licenses yes, with the RLM server yes no
Metered licenses no yes no
Post-use billing no yes no
RLM-embedded compatible yes no yes
Requires end-user accounts no no yes
Can be self-hosted by ISV yes no yes
Can use dongles yes no no