Create a ticket

Q100329: How do Collective licenses work?


This article explains how licenses for our Production Collective, Creation Collective and Education Collectives work.


We have released three Collectives, which are bundles of our products:
  • the Production Collective contains NukeStudio, Mari and Modo
  • the Education Collective contains NukeStudio, Mari, Modo, Katana and CaraVR
  • the Creation Collective contained Modo, Mari and HieroPlayer
A license for a collective entitles you to run all of the products in that collective e.g. if you purchase the Production Collective then you're able to run Modo, Mari and Nuke/NukeX/NukeStudio.
The way this works in terms of licenses depends upon what type of license you have, nodelocked or floating. Note: all Education Student Collective licenses are nodelocked.

Nodelocked licenses:
A nodelocked collective license consists of a nodelocked license for each product in the collective.  This allows a single machine to use any or all of the programs within that Collective. 
Floating licenses:
A floating collective license allows a set number of users/hostmachines to be able to run any or all of the programs in the collective.  For example, if you had 3 floating licenses for the Creation Collective then you could have up to 3 machines running any combination of Modo, Mari and HieroPlayer but you cannot have 3 machines running one product, e.g. Mari, and a 4th running a different product, e.g. Modo.
Floating Collective licenses use a special kind of RLM license called token-based licenses, which require another license to work.  A floating collective license therefore includes token licenses for each product in the collective which are token-locked to a primary license for the whole collective.  The example below is for one floating Creation Collective license:

The way this works when users run the programs is as follows:
  1. UserA user launches a product, e.g. Modo, which asks the server for a modo_i license
  2. Modo finds the valid modo_i license which is token locked to the foundry_creation_i license
  3. If the foundry_creation_i license is available it is checked out to UserA and Modo runs

  4. With Modo still running, UserA then launches Mari which asks the server for a mari_i license
  5. Mari finds the valid mari_i license which is token locked to the foundry_creation_i license
  6. UserA already has the foundry_creation_i license checked out so the Mari license request works and Mari runs.

  7. UserB launches a product, e.g. Mari, and asks for mari_i license
  8. Mari finds the valid mari_i license which is token locked to the foundry_creation_i license
  9. The foundry_creation_i license is not available so Mari will not run.

More information about some of the licensing topics mentioned above can be found in the following articles:
Was this article helpful?

We're sorry to hear that

Please tell us why
1 out of 1 found this helpful