Cloud Zoo License Management Available in Rhino 6

@KlikOSx no, you may not add educational lab licenses owned by different schools to your account since you do not own those licenses. Additionally, if the two labs are owned by two different schools they should not be in the same account.

I am including my colleagues in Barcelona on this topic so you can inquire with them if you need to purchase licenses. @carlosperez @delia @Rodri

It sounds to me like you are perhaps talking about 10-20 students away from the EDU institution over the course of a year, but only one (or maybe 2-3) at a time?

From Jodie’s response it sounds to me like you need to have the students (and perhaps yourself as a teacher, if you don’t have a Rhino license yourself) be authorized to check out a copy from the EDU institution’s Zoo.

Just trying to re-phrase the question and answer here. If I’m way off-base I’m sure the people with the right answers will clarify.

Thank you very much for your clear replies Andrès & Jody.

If understood well the rules I have 3 options :

1 Use the NFR license I own to manage all teams with one single account.
Is this is authorized by McNeel for EDU purposes.

2 Manage all accounts individually with the authorization of the EDU institutions.
This mean that the emails associated to the accounts must be individuals.

3 In case the NFR lic can’t be used, buy another Lab license through my company and dedicate it to the reverse pedagogy I want to setup in the context of the EDU landscape.

I already own a Single User Rhino for Mac EDU license but it can’t be used for that purpose I think.

Best regards.

If any of you want to clarify few points regarding my activities, feel free to contact me any time.
R. Santos.

Hi @KlikOSx
Please send me your license keys (to and I can let you know how to manage these, but to summarize:

  • Edu single-user licenses cannot be shared, they are personal
  • Lab licenses: the school or university owning one of this might give access to their students via the Cloud Zoo, but never share the license key with them
  • NFR licenses: these can be used only by the reseller or partner owning them


And any type of license needs to be managed by its legal owner.

This is so much fun…

So I completely uninstalled my Rhino 6 and wiped out the registry and other entries (as per instructions here) in the hopes that it would fix the Osnap and SelectionFilter switching situation as suggested by these posts…

I also thought it would be a good time to put my license into my Rhino account in the “cloud” as the uninstall above also takes out all the licensing info.


Install the newly downloaded Beta. Then for the license, as prompted, I log in to my Rhino account and throw in the license key.

Surprise #1- I get this:

The above mentioned computer is of course my home workstation 30 Km away… The computer is off, but whatever. Didn’t think I was going to do this today, so was not prepared.

OK, well, I guess I’ll just add add back in the license locally as it was before, so I can work this afternoon, then remove it when I quit for the day and go home.

Then comes surprise #2-
Upon trying to enter my license key locally - after at least 3 message screens with warnings like "Are you SURE you want to add your license locally? You’ll only be able to use it on this machine…" - I finally get this:


And of course the link leads back to my Rhino account, where I can’t add the license…

And then surprise #3-


OK, glad I didn’t actually have to do any work this afternoon…

Finally a Beta which is unable to save actually opens, but without toolbars. _Toolbar is an unknown command, and there is no plug-ins section in Options. Close Rhino again and open it, toolbars finally appear and things look more or less normal (default)…

And funnily enough, I can save files. It doesn’t appear to have registered my previously existing license key, so I now have some sort of valid temp license I guess… who knows? I only hope that when I get home, I can remove the license from my home workstation and get it into my Rhino account without it throwing more roadblocks in the way…

Anyway, I predict that licensing questions are going to be the #1 support question for resellers/tech support for awhile…

EDIT: Addendum - after having saved one file with the file still open, I went into Options to load my custom toolbars. Having done that, Rhino went back to being an “expired Beta”. Closing and re-opening, it again opened without any toolbars (neither mine nor default) or plug-ins section. Plus the whole validation thing which fails of course. So NOW, everything is completely useless. I sure hope this won’t be a typical user experience.


So now I was able to get my license into my Rhino account from home - still more screens than I would have liked in between the Rhino license manager in options and the open Rhino account on the web page… Far from “automatic”. And, I have yet a third computer (my laptop) that also has the Beta installed as a fixed license yet the online license manager seems completely unaware of it…

But I still do not understand why this happened in the first place, I have an NFR license which should (theoretically) permit me to have the same fixed license on several computers and even use them simultaneously, like a lab license. So why all the c*** in this case?



I believe you have a beta license that precedes Cloud Zoo. In those days (before June 2017 or so), you were able to install a license on multiple machines, but our license policy has changed so that you may only install a license on ONE machine, or put it in the cloud.

Naturally there are many end users like you who had installed a beta license before and are understandably left in an incompatible state because the license had been installed on different machines at different points in time. What happened is you inadvertently kicked yourself out because of this inconsistency in our system, since our validation servers today will only accept a license that is not in use elsewhere.

Of course, in the commercial release of Rhino 6, this case should not occur because everyone starts from a clean state, so it should never be possible to have a license in multiple places at the same time.

I’m sure there will be issues, but I thought you’d like an explanation why you experienced so much pain.

If it’s only me, then there’s nothing to worry about… Maybe I’m totally out in left field, but I have a feeling there will be a number of people who are going to expect it to work like it used to with one license on several machines without setting up a Rhino account, and are going to try going that route first.

That’s also why I want to make sure all the info is in one place so we can get it to clients - @scottd preferably a PDF “how-to” that includes all the info about licenses currently on the Wiki that we simply can send to clients - in all languages. Because as resellers we are going to get a lot of questions…

So there are a couple issues here.

  1. There is a change in behavior here that is going to be hard. People expect that the license will work on several machines by installing stand-alone. That is not true with Rhino 6. Rhino accounts solves this problem and is the default licensing scheme, but you are right that it is a habit and expectation from existing users. We have been working to make the language clear on this, even in the installer.

  2. I agree with one place for information on licensing.

To make this more complicated there are different ways to present this information:

  1. What’s new with Rhino 6:
  2. And a concise explanation on how Rhino licensing works:

The concise explanation page needs additional links to how-to

1 Like

OK, thanks Scott. You mention “Rhino account” in the both places, plus “Cloud Zoo”. I think it needs to be made clearer that everyone is going to be required to create a Rhino account in order to use the Cloud Zoo service. I think that Rhino account should be mentioned first everywhere - i.e.

Cloud Zoo (New) - Make your licenses available anywhere in the world by logging into your Rhino account


There are now three ways to use your license:

  1. Create a Rhino account and use the Cloud Zoo”

And, I still would really like a PDF of all of that…


1 Like

Mitch -

We gone back and forth on the Rhino Account/Cloud Zoo terminology. I expect over time the Rhino Account term will gain a larger meaning then just and association with Cloud Zoo. So while much of it might seem interchangeable, that will change as time goes on.

@bobmcneel has some thoughts on that.

Exactly - it’s not interchangeable. The Rhino account concept is the most important to push, as we want (require comes later, I expect) every single user to have an account to manage everything that is Rhino related in one place. Many, many people will only have one license to manage, the concept of “Zoo” won’t mean a lot to them and may be confusing… (a zoo with one animal?)


1 Like

Hi @aj1 ,

Do you have any plan on making the Cloud Zoo available for third party plugin as well, as we are able to do with the Zoo?

That would be great!


Yes. @aj1, @brian, and @dale can tell you more.

@qlabrosse yes, we definitely do. It is technically already possible, as we designed the system to be used by third parties from the start. The spec is not final, but preliminary documentation for the server side is available here.

There are also some very minor changes that need to be done at the plugin level, which shouldn’t take more than a few minutes of programming work.

Great then, I will follow this!

Hi AJ,

I think that now CloudZoo being a production-ready licensing approach for a released version you should consider being logged in into your rhino account as a way to validate access to downloading installers, if your login gives you access to license usage.

Right now if I go to find the installer for Rhino WIP I encounter this:

That requires me to know the email and license key used. This is a bit of a hassle but of for my personal case. But anyone in my team of licenses will be prevented from downloading a version because they do not have this information. Another approach is that you let them in, if they go to the downloads page from their logged in page in Rhino3d/licenses.




@gustojunk yes, we are working to smooth this process out.


1 Like