Using Single license for Rhino compute service to run on AWS with instance scaling

Hi, I’m developing a web service on AWS using rhino compute based application.
What I want to achieve is scaling out AWS instances, and each instances have Rhino WIP installed.
Until now, I purchased Rhino license for each instances and using it for each Rhino WIP application installed in each instances.

But lately, I read about scaling on AWS with one license.

Does this instruction mean that I can use single license for multiple AWS instances(with Rhino WIP installed) if I follow above link instruction? In this way, can multiple Rhino apps run simultaneously with one license key?

I’m not sure if I understood correctly. Please answer. Thanks.

@stevebaer @will
I’ve mentioned some who seems to be related,(if not, sorry for the mention).
Could anyone please reply?

The best person for licensing would be @brian

@evan12 sorry we didn’t get to this right away!

Your Rhino license only covers running Rhino on one computer/VM at a time – see the EULA.

In the near future we will have a new time-based method of licensing Rhino when running on services like AWS, Azure, GCP, etc.

We’re still working on the details of how licensing will work for server-based instances of Rhino. Here’s our current strategy:

Option 1: Core-Hour Billing
Soon, you’ll be able to enable Core-Hour billing on a Cloud Zoo team, add a credit card on file, then add one or more service accounts to that team. When Rhino is logged in to a service account and is running on a Windows Server-based operating system, you will be billed $0.10 per core per hour that Rhino is running (pro-rated per minute).

This means that if you have Rhino running for 1 hour on a 32-core machine, you’ll be billed $1.60.

Billing is based on uptime, not on usage - we don’t track the activity of each core, just that you have one running with Rhino. You can scale your workloads up and down to optimize performance and cost to you.

**Option 2 - Perpetual Licensing** Ordinary Rhino 7 licenses will act as per-core licenses on Windows Server. If you have the same 32-core machine running on Windows Server, but licensed using the [Zoo](, Rhino will request 32 simultaneous licenses from the Zoo. If there are not 32 licenses in the Zoo, Rhino will fail to start. This extends our perpetual licensing for desktops using the same license key infrastructure. Your licenses can be licensed to servers in the Zoo, or to desktop clients in the Zoo, Cloud Zoo, or single-computer licensing.

Edit Oct 23,2019: We’re now considering removing the perpetual licensing model for server-based licenses.

Single computer licensing not supported on Windows Server
When running on Windows Server, it will not be possible to enter a license key to run as a single-computer license, as Rhino requires a license per core. That feature is only supported via core-hour billing or Zoo-based perpetual licensing, as described above.

1 Like

oooh, so I see that finally Rhino subscription licensing is here. So let me do some math to figure out regular use pricing…

If I get core-billing enable on my Could Zoo team for a designer working 40/h week on a 6-core machine it will cost me:

$0.05 * 6 cores * 40h * 48 (weeks) = $576/year subscription, or $48/month

If we add a RhinoIdleSaveAndQuit.rvb script to kill Rhino after 20 minutes idling, we can probably lower utilization by 35%…
so that’s a:

$374/year subscription, or $32/month.

Well played McNeel. Well played.

Core-hour billing is not available for desktop clients. Desktop computers that try to login to a core-hour billing team will not get a license to run. We don’t have plans for subscription licensing for human users.

1 Like

This is very specific to scenarios like compute.rhino3d running on servers. Can be considered a completely different product.

1 Like

@brian Thanks for reply!
I’ll look forward to using Core-Hour Billing.
Could you tell me when it will be available, roughly at least?
Because I really need this license pricing option for the stability of my service.