Single-computer licensing is not supported on Windows Server when running Rhino WIP 7.0.19260 (Sep 17 2019) or later. Licensing is unchanged when running on Windows 7, 8, 8.1, 10, or on MacOS desktop operating systems.
If you’re running Compute on AWS, Azure, GCP, in Docker containers, or on your own server infrastructure, you need to either use Cloud Zoo or Zoo to license Rhino. Read more about Zoo and Cloud zoo in our Licensing and Administration article.
Today, Rhino WIP uses one Rhino 6 license per instance per computer. In the future, Rhino 7 will use one license per processor core, as described in this thread.
Starting 15-Sep-2020, Rhino WIP will require a core-hour billing team when running on Windows Server or in a Docker container - whether it is running as Rhino, Rhino.Inside, or as Compute. You have until October 23, 2020 (when the 8-Sep-2020 WIP expires) to complete this transition.
During the WIP period, we will bill at most $0.10 per month (in order to verify that credit card payments are succeeding).
A core-hour is Rhino running on one core for an hour (or running on four cores for 1/4 hour).
Your core-hour billing rate (currently US$0.10 per core-hour) is set when you create enable core-hour billing on your team.
Your bill will be computed and charged monthly.
Core-hour billing is only available when running on Windows Server. If you run on desktop Windows, you must have a traditional Rhino license.
Core-hour billing applies regardless of where your server is running. You are free to run Windows Server on your favorite cloud service, your favorite Docker environment, or on your own hardware.
Please let me know how this transition goes, or if you have any questions.