Rhino 3D is one of the most widely taught design software tools in UK universities — used across architecture, engineering, product design, and urban planning programmes. For IT managers and procurement teams responsible for deploying and maintaining software across teaching labs and studio spaces, understanding the licensing options available is essential to getting the right setup at the right cost. This guide explains the key decisions and how to approach them.
Educational Licensing: What's Available
McNeel (the developer of Rhino) offers educational licences at significantly reduced prices compared to commercial licences. These are available to:
- Registered students at accredited educational institutions
- Academic staff (teaching and research)
- University departments for lab and teaching room deployment
An important point that is often misunderstood: Rhino educational licences can be used for commercial work. There is no restriction on using an educational licence for paid projects, client work, or research with commercial applications. This makes educational licences genuinely useful beyond the classroom — for student practices, university spin-outs, and research consultancies operating out of university facilities.
Lab Deployment: The Key Licensing Options
For university teaching labs, there are two primary deployment models:
Node-Locked (Single-User) Licences
A node-locked licence is tied to a specific machine. Each computer in the lab requires its own licence. This is straightforward to manage but can be expensive at scale, and licences are wasted when machines are unused.
Node-locked licences are best suited to smaller deployments (fewer than ten machines) or situations where each machine has a dedicated, consistent user.
Floating Licences via LAN Zoo
LAN Zoo is McNeel's free licence server software. It allows a pool of Rhino licences to be shared across a network — so a lab of thirty machines might only need twenty licences if peak concurrent usage is typically below that threshold.
For university labs, floating licences are almost always the more cost-effective option. Key points:
- LAN Zoo is free to download and install — there is no additional cost for the licence server software
- It runs on a Windows server or workstation on the same network as the client machines
- Licences are checked out when Rhino launches and returned when it closes — the process is transparent to the user
- Usage can be monitored to inform future licence purchasing decisions
- LAN Zoo requires network connectivity — machines must be able to reach the licence server. It is not suitable for offline or air-gapped deployments without additional configuration.
Cloud Zoo
McNeel also offers Cloud Zoo, a cloud-based licence management system. Licences are associated with a McNeel account rather than a specific machine or local server, allowing users to access their licence from any machine with an internet connection.
Cloud Zoo is well suited to students accessing Rhino on personal laptops or from home. It is less suited to managed lab environments where IT teams prefer not to require individual user accounts for software access.
Deployment Considerations for IT Teams
When planning a university Rhino deployment, IT teams should consider:
- Network architecture: LAN Zoo requires a server accessible to all client machines. Consider whether this needs to span multiple buildings or campuses, and whether VPN access is required for off-campus use.
- Installation and updates: Rhino can be deployed via standard software management tools (SCCM, Intune, etc.). Silent installation is supported. Updates should be tested before deployment to avoid disrupting teaching.
- Plug-in management: If the department uses Rhino plug-ins (Grasshopper plug-ins, rendering tools, specialist add-ons), these need to be licensed and deployed separately. Confirm plug-in compatibility with your Rhino version before purchasing.
- macOS vs Windows: If the lab includes Mac hardware, confirm that all required plug-ins are macOS-compatible. Several widely used Rhino plug-ins are Windows-only.
- Concurrent usage modelling: Before purchasing floating licences, model expected peak concurrent usage. Timetable data and historical software usage logs (if available) can inform this. It's better to start with a conservative estimate and add licences than to over-purchase.
Procurement Process
University procurement teams typically require:
- A formal quote on headed paper, including unit prices, total cost, and VAT treatment
- Confirmation of educational pricing eligibility
- Licence documentation suitable for asset registers
- A purchase order process rather than credit card payment
CADWAX can accommodate all of these requirements. We supply Rhino licences to UK universities and can provide quotes, pro forma invoices, and licence documentation to support your procurement process. Educational institutions are VAT-exempt on certain software purchases — contact us to confirm the applicable treatment for your institution.
Ongoing Licence Management
Once deployed, Rhino licences require relatively little ongoing management. Key tasks include:
- Monitoring LAN Zoo usage to identify whether additional licences are needed
- Managing version upgrades when new Rhino versions are released (typically every four to five years)
- Updating plug-in licences in line with Rhino version upgrades
- Managing student access for Cloud Zoo deployments (adding and removing users as cohorts change)
Talk to CADWAX About Your University Deployment
CADWAX supplies Rhino 3D educational licences to UK universities, further education colleges, and research institutions. We have experience with both small departmental deployments and large multi-site lab configurations, and we can advise on the right licence model for your institution's needs.
Procuring for your institution?
CADWAX supplies Rhino 3D lab and academic licences for UK universities and colleges.
Contact us directly to discuss your deployment requirements and request a formal quote.
View Lab Licence DetailsContact Us