Search
Close this search box.
Try RLM for Free
Search
Close this search box.

RLMTeams

How RLMTeams Works

  1. Setup: define the types of licenses to be delivered with RLMTeams, either node-locked uncounted, or node-locked single-user.
  2. Upon purchase, create an entitlement for your customer.
  3. RLMTeams and RLM do the hard stuff. Your customer logs in, transfers part of the entitlement to other user(s) and/or fulfills the entitlement on their computer. RLMTeams records the transaction in your database, and the license is ready for use.
  4. You make a standard RLM rlm_checkout() call, check the return status from the API and decide to run or not.

How is RLMTeams different from Activation Pro?

  1. With Activation Pro, you have to create and deliver activation keys to your customers which are later redeemed for a license. The license gets tied to the user’s physical machine and is stored there. The license remains until it is revoked or expires. Your application must be programmed to allow the license to be activated and revoked.
  2. With RLMTeams, users have accounts on the RLM Teams portal. They log in from their local machines to fulfill their licenses. As the vendor, you get to decide how long the resulting license can be used before it must be refreshed. If a user wants to move his license to a different machine, he logs into RLM Teams from the new machine, deletes the prior fulfillment, and fulfills again.
  3. RLMTeams accounts are either “admin” users or “regular” users. Regular users can fulfill licenses for themselves, or transfer their license entitlements to someone else on the system. After transferring, they can later “reclaim” the entitlements for themselves. “Admin” users have the additional privilege of managing user accounts.

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.