Zoo lic manager for issuers

Zoo
1

Dear All,

we are interested in trying Zoo Cloud for licensing our plugins.

We went through your tutorials about how to integrate the mechanism within our products.

  1. For what I understood we have to provide api at our server backend and these api are invoked only when a license is created, deleted or detected for the firs time whereas Zoo Cloud takes care of any lic check when the user runs our plugins. Is that right?
  2. I suppose the user can launch as many concurrent executions of our plugins as the number of Rhinoceros licenses they have, is that correct? If it is the case, can we somehow limit the overall number of licenses for our plugin and make independent form the number of Rhinoceros licenses the user has?

Many thanks in advance

2

@will - can you help?

3

Hi @gm_user,

  1. Correct! A request is made to your “issuer server” when you or one of your users add/remove a license to/from Cloud Zoo. Once the licenses are in Cloud Zoo, all communication is only between your plug-in and Cloud Zoo. Cloud Zoo ensures that the number of concurrent sessions of your plug-in do not exceed the number of seats provided by the licenses in Cloud Zoo.
  2. Your plug-in’s license and Rhino’s licence are separate! The user will of course require a Rhino license but they will also need a license for your plug-in. Usage and seat availability are tracked independently.