Reprise’s RLM vs. Thales Sentinel Licensing

Pricing: Transparent Model vs. Quote-Based

Reprise uses a revenue-based pricing model. The pricing tier is based on annual revenue associated with the software products using RLM. Adding developers, customers, licenses, or deployments doesn’t by itself increase the fee. Reprise publishes how its revenue-based model works, but the pricing tier and actual price are determined through a custom quote.

Thales does not publish Sentinel pricing. Its quote depends on the products and services included, and professional services may be part of the deployment.

Both require a sales conversation to learn the actual price. Reprise’s published model gives buyers a clearer basis for understanding what drives its quote before that conversation.

Time to Production

RLM is a client library rather than a platform you need to stand up. You link the SDK into your build, call rlm_init(), and check out licenses from a license file or a lightweight vendor daemon. The core API is only eight powerful calls, and most teams finish the integration in days rather than weeks.

License policy lives in the license file instead of your application code. That means you can move a customer from node-locked to floating, add a feature, or adjust license terms without patching and recompiling your product.

Because the integration is a single library and license rules are kept outside your code, there are few components to set up before you can ship, and little to revisit when your licensing needs change. Sentinel’s broader monetization platform typically involves more components and more setup before it’s ready for production.

One Integration for Every Deployment

When your application calls rlm_init, the RLM client can look for licenses on the local machine, on a network license server, and in the cloud. A single customer can use a cloud license, an on-premises server, and a node-locked license at the same time, and can even overflow from a local server to the cloud when local licenses run out.

Your application only needs one set of licensing logic to support all of this, so there's no need to maintain separate code paths for on-premises and cloud customers.

Transparency and Data Portability

RLM’s usage report log uses a published, human-readable format. License administrators can review the data directly, process it with their own tools, or bring it into an existing BI or reporting system.

License terms are stored in the license file, where administrators can inspect them. Reprise also publishes RLM’s documentation and says the product has no ISV-specific back doors.

Identity-Based Entitlement

RLM Cloud supports user-level entitlement through ID Licensing. Rather than having everyone at a company share one set of credentials, you can provision individual users, assign them to servers, and control which products each person can access. Reprise’s own identity service and Microsoft Entra ID (formerly Azure AD) are available as identity providers; any identity provider supporting OIDC may also be used.

This gives publishers a way to tie entitlements to individual users instead of only to machines or servers.

Direct Access to the RLM Team

Reprise provides email support with a one-business-day response time. Questions go to people who work on RLM rather than into a tiered queue at a large organization, which usually means faster, more knowledgeable answers when something comes up.

Who Reprise Is a Good Fit For

• ISVs that want dependable license enforcement without the added complexity of a full monetization platform
• Engineering teams that want a quick licensing integration with a small footprint in the application
• Companies that prefer a published pricing model over a quote assembled from multiple products and services
• Teams that want their licensing data in an open, portable format
• Vendors supporting on-premises, cloud, and hybrid customers from a single integration
• Companies that would rather manage licensing in-house than rely on professional services