Reprise License Manager
von Reprise Software
Wer nutzt diese Software?
Softwarehersteller, die Software- und Hardwareprodukte verkaufen, die ihre Lizenzierungsrichtlinien mithilfe eines Toolkits eines renommierten Lösungsanbieters durchsetzen müssen.
Durchschnittliche Bewertung42 Bewertungen
- Gesamt 5 / 5
- Benutzerfreundlichkeit 4.5 / 5
- Kundenservice 5 / 5
- Kostenlose Version Ja
- Kostenlose Testversion Ja
Installiert - Mac
Cloud, SaaS, Web
Installiert - Windows
Support während der Geschäftszeiten
Angaben zum Hersteller
- Reprise Software
- Gegründet 2006
Über Reprise License Manager
Der Reprise License Manager (RLM) ist ein Softwarelizenzierungssystem, das unabhängige Software-Anbieter
(ISVs) in ihre Produkte integrieren, um zu steuern, wie ihre Nutzer ihre Software kaufen und verwenden. RLM steuert
auf welche Funktionen oder Optionen zugegriffen wird, auf welcher Hardware die Software ausgeführt werden kann und wie viele
gleichzeitige Kopien der Software zu einer gegebenen Zeit aktiv sein können. RLM erzwingt Lizenzablaufdaten,
wenn notwendig. RLM stellt sicher, dass nur Kunden mit gültigen Lizenzen Lizenzprodukte verwenden können.
Reprise License Manager Funktionen
- Verwaltung von Knoten(punkten)
Die hilfreichsten Reviews für Reprise License Manager
Bewertet am 18.2.2016
RLM works well in all our current products, and gets few complaints from customers
Kommentare: We have been selling connectivity software since 1989, and were using our own license enforcement until late 2010, when a customer recommended RLM as an improvement over our clumsy ad-hoc system. We sell to all size companies, from 1 user to 1000's of users, and RLM works well for all sizes. Pros: RLM is fairly easy to install: Simply download the package, follow the instructions, and link the resulting library into your application. The license files are text and rather compact, and one format supports both node-locked and license server models. The API has simple calls, but also more advanced ones. Using the simple calls, you pass the name of your application and its version number, and it returns a yes or no. If no, you can go into a demo or evaluation mode. Reprise is very good at customer service. They usually answer tech questions the same day. Cons: When we first signed up (in 2010), the RLM activation server was primitive and not usable, so we wrote our own. (An activation server distributes an license file with the customers hostid from a sales database when given an activation key.) Since then, they have released "Activation Pro", but we had already written our own, so I can't review that. We don't use their free product, but their paid product requires an additional annual fee for each architecture, and "Windows 32-bit" is a different architecture from "Windows 64-bit". If your customer runs your application on one architecture and wishes to run their license server on a different architecture, you have to purchase both. There is not a good API for querying license use, but there is a good web interface to the RLM license server. The Linux startup script for the license server (/etc/init.d/rlm) did not work well. It can easily shut down the wrong server if it's not configured correctly. We ended up making major changes to the Linux startup script. However, the Windows RLM license server starts up very well.
Bewertet am 18.2.2016
Flexible, adaptable and transparent
We've been using Reprise for our products' licensing for more than 6 years now. Their solution client-side is in the form of a library, and it is very transparent what it does and how it works. It is in a form that is highly flexible, so that when we have requirements or processes that are unique for us, it is possible to adapt. The transparency has also allowed us to develop much of our own back-office processes and automation, from license generation to activation, to salesforce integration, around the Reprise toolset. They have a diverse set of licensing options, only a subset of which we make use of, but we are able to offer our customers floating (site) licenses as well as individual licenses.
I've interacted with Bob many times, from advice on how to approach issues or client-specific problems, to addressing bugs, to implementation problems on my end. He's the expert, and I like being able to get right to the deep technical details immediately.
Because the client-side is essentially a library, much of the onus for the customer experience falls on us -- how our product's UI presents licensing interactions to the user. This is less turn-key than some other options, but as I said, it gives us total flexibility. I often feel that we could do a better job on our end. Where there are areas where ERs on their end can help, I know I have a receptive ear, and have seen several of my requests implemented over the years.