Node License Explained for 3D Rendering: Corona, V-Ray, Arnold

What is a Node License?

A "node license" in 3D rendering refers to a software license that allows rendering on a specific computer (or node) in a render farm. It's distinct from a workstation license, which is tied to a single user or machine for interactive work. Understanding the difference is crucial for setting up efficient rendering infrastructure.

In this guide, we break down the three main licensing models, explain how they work on render farms, and show you how to choose the right license type for your studio setup. We've deployed thousands of render licenses across our farm infrastructure, and the costs—and capabilities—differ significantly based on which model you choose.

The Three Main License Types

1. Workstation (Nodelocked) License

A workstation license is tied to a specific computer or user. It allows rendering on that machine only and typically includes full software features, including interactive work, modeling, and rendering.

Characteristics:

• Single-machine binding: License is locked to one physical computer (by MAC address, hard drive ID, or license server).
• User-tied: Often linked to a specific user account.
• Full feature set: Includes all rendering features, UI, and plugins.
• Non-transferable: Cannot be easily moved to another machine.
• Cost: Mid-range (typically $200–$2,500 per year, depending on software and tier).

When to use:

• Your primary workstation where you do modeling, animation, and interactive work.
• Small studios with 1–3 machines.

Limitations:

• Cannot use on multiple machines without re-licensing.
• Not suitable for render farms, where you need to render on many nodes.

2. Floating License

A floating license is managed by a central license server. Multiple machines (up to the number of licenses purchased) can check out a license from the server when needed and return it when finished. It's the most flexible model for medium-to-large studios.

Characteristics:

• Centrally managed: License server (e.g., RLM or VendorID) distributes licenses.
• Concurrent usage: N floating licenses allow N simultaneous renders across N machines.
• Flexible assignment: Any machine on the network can use an available license.
• Transferable: Licenses can be redistributed as needed without hardware binding.
• Cost: Higher per-license ($300–$5,000+), but cost-effective at scale.

How it works:

1. You set up a license server (a dedicated machine or cloud instance).
2. Install license files on the server.
3. Render nodes and workstations connect to the server and request a license.
4. When rendering completes, the license is returned to the pool.
5. If all licenses are in use, subsequent render requests queue or fail.

When to use:

• Studios with 5+ machines and mixed workstation/render farm setups.
• Environments where render node count varies (add/remove nodes dynamically).
• Multi-studio or distributed rendering across offices.

Limitations:

• Requires a stable license server and network connectivity.
• Server downtime means no renders can start.
• More complex to set up and maintain.

3. Render Node License

A render node license (sometimes called a "headless license" or "node license") is specifically designed for rendering only on farm nodes. It's cheaper than workstation licenses because it excludes interactive features (UI, modeling, animation).

Characteristics:

• Headless rendering only: No UI, no interactive features—just command-line rendering.
• Machine-locked or floating: Can be bound to a specific node or issued via a license server.
• Render-optimized: Includes only render features; excludes features you don't need on a render node.
• Reduced cost: Significantly cheaper than workstation licenses (often 30–50% of workstation cost).
• Infinite concurrent rendering: On some vendors' models (e.g., Corona), a single node license allows unlimited concurrent renders on that node.

When to use:

• Render farm nodes (the majority of your farm infrastructure).
• Headless rendering servers with no interactive work.
• Cost-conscious studios optimizing rendering budgets.

Limitations:

• Cannot be used for interactive work or modeling.
• May have feature restrictions compared to workstation licenses.
• Vendor-specific: Corona, V-Ray, and Arnold implement node licenses differently.

Licensing Models by Renderer

Corona Renderer Licensing

Corona uses a straightforward node licensing model.

License Types:

1. Workstation License (Corona):

   • Tied to a single machine.
   • Includes full feature set.
   • Cost: ~$300–$400/year.

2. Node License (Corona):

   • Tied to a specific render node or floating on a license server.
   • Allows unlimited concurrent renders on that node.
   • Cost: ~$100–$150/year (roughly 1/3 workstation cost).
   • Floating version: Available via RLM license server.

Corona on Render Farms:

Corona node licenses are ideal for farms. You purchase one node license per render node, and that node can render unlimited Corona jobs. There's no per-render cost or per-frame fee.

Example Setup:

• Workstation: 1 Corona Workstation license ($350/year)
• Render Farm: 20 nodes × 1 Corona Node license each ($100/year each = $2,000/year)
• Total annual cost: $2,350

Features:

• Node licenses support the same renderers and features as workstation licenses (no degradation).
• Full access to Corona plugins, denoiser, AOVs, and scripting.

V-Ray Licensing

V-Ray's licensing is more complex because it's offered across multiple 3D packages (3ds Max, Maya, Blender) with different models per package.

License Types:

1. Workstation License (V-Ray):

   • Per-package (e.g., V-Ray for 3ds Max, V-Ray for Maya).
   • Tied to a single user or machine.
   • Cost: ~$400–$700/year per package.

2. Render Node License (V-Ray):

   • Available for 3ds Max and Maya.
   • Tied to a specific machine or floating license server.
   • Cost: ~$200–$350/year per node (roughly 50% workstation cost).

3. V-Ray with Chaos Cloud:

   • Subscription model ($30–$50/month) that includes cloud rendering credits.
   • No per-node licensing; you pay for render credits instead.

V-Ray on Render Farms:

V-Ray render node licenses are per-node. You cannot render on an unlimited number of nodes with a single license. Instead, each farm node requires its own render node license (unless using Chaos Cloud for distributed rendering).

Example Setup (Traditional):

• Workstation: 1 V-Ray for 3ds Max license ($500/year)
• Render Farm: 20 nodes × 1 V-Ray Node license each ($250/year each = $5,000/year)
• Total annual cost: $5,500/year

Example Setup (With Chaos Cloud):

• Workstation: 1 V-Ray for 3ds Max license ($500/year)
• Cloud rendering: $50/month = $600/year
• Total annual cost: $1,100/year (assuming you render < 10,000 frames/month)

Floating Licenses:

V-Ray supports floating licenses via a Chaos license server. A single floating V-Ray license can be shared across multiple machines (up to the count of licenses).

Arnold Licensing

Arnold (by Autodesk) uses a different model than Corona or V-Ray, primarily because it's often bundled with Maya or 3ds Max.

License Types:

1. Studio License (Arnold via Maya or 3ds Max):

   • Tied to a Maya or 3ds Max subscription.
   • Includes Arnold rendering as part of the subscription.
   • Cost: $85–$680/month (depending on plan and bundling).

2. Standalone Arnold Render License:

   • For headless rendering without Maya or 3ds Max.
   • Not as commonly purchased independently.
   • Cost: Varies (often bundled with Autodesk packages).

3. Autodesk Subscription for Render Nodes:

   • Some studios purchase Maya or 3ds Max subscriptions for render nodes.
   • Cost: $680/month (Subscription Plus tier) for full features.

Arnold on Render Farms:

Arnold licensing depends on your deployment model:

• If rendering via Maya/3ds Max: Each render node needs a Maya or 3ds Max subscription (most common for studios already on Autodesk products).
• If rendering standalone: Licensing is simpler but standalone Arnold isn't widely deployed in studios.

Example Setup:

• Workstation: 1 Maya Subscription ($680/month = $8,160/year)
• Render Farm: 20 nodes, assuming you already have Maya subscriptions shared or use a floating license server.
• Total cost depends on subscription structure: Typically $8,160–$16,320/year for workstations + farm setup.

Arnold on Cloud Farms:

Many cloud render farms include Arnold via built-in Maya subscriptions. When you submit to our farm, you don't need to worry about individual Arnold licenses; the farm covers it as part of the service.

Comparing Node License Costs

Here's a cost comparison for a small studio with 1 workstation and 10 render nodes:

Renderer	Workstation Cost/Year	Node Cost/Year	10 Nodes Cost/Year	Total Cost
Corona	$350	$100	$1,000	$1,350
V-Ray (Traditional)	$500	$250	$2,500	$3,000
V-Ray (Chaos Cloud)	$500	N/A	$600 (credits)	$1,100
Arnold (Maya Sub)	$8,160	$8,160*	$81,600*	$89,760

*Assumes per-node Maya subscriptions; actual costs vary with licensing agreements.

Key Takeaway: Corona is the most cost-effective for small-to-medium render farms. V-Ray is mid-range, especially if using Chaos Cloud. Arnold is expensive for dedicated render nodes unless you already have a site license.

Setting Up Node Licenses on a Render Farm

Step 1: Decide on Licensing Model

• Single-machine node licenses: Suited for small farms (1–10 nodes). Each node gets a dedicated license.
• Floating licenses: Better for medium-to-large farms (10+ nodes). Uses a central license server.

Step 2: Install License Server (Floating Model)

If using floating licenses:

1. Choose a license server machine: A stable, always-on server (VM or physical) with a static IP.
2. Install license server software: Corona uses its built-in license manager, V-Ray uses RLM, Arnold uses Autodesk License Server.
3. Configure license server IP: On all render nodes, point to the license server's IP in the renderer's settings.
4. Test connectivity: Ensure all render nodes can reach the license server over the network.

Step 3: Deploy Node Licenses

1. Purchase licenses: Buy render node licenses matching your node count.
2. Distribute license files: On each node (or on the license server for floating licenses), place the license file in the renderer's license folder.
3. Activate licenses: Some renderers require online activation; others use offline license files.
4. Verify installation: Test rendering on each node to confirm licenses are recognized.

Step 4: Monitor License Usage

Most renderers provide license usage reports:

• Corona License Manager: Shows active licenses per node.
• V-Ray RLM Dashboard: Shows floating licenses in use, available licenses, and usage history.
• Arnold License Server: Tracks license checkouts and availability.

Monitor these regularly to spot:

• License exhaustion (all licenses in use, rendering queued).
• License server downtime.
• Nodes with persistent license issues.

Recommended Approaches for Render Farm Licensing

1. Right-Size Your License Count:

Track render farm queue depth. If you consistently have 20 jobs waiting for a license with 10 node licenses, buy more licenses. Conversely, if licenses are idle 80% of the time, reduce your license count.

2. Use Floating Licenses for Flexibility:

Floating licenses allow you to scale render nodes without buying additional licenses per node. This is especially useful if your render node count varies seasonally.

3. Set Up License Server Redundancy:

For floating licenses, use a backup license server. If your primary server goes down, render nodes automatically fail over to the backup.

4. Monitor License Server Health:

• Ensure your license server has 99.9%+ uptime.
• Allocate sufficient disk space (license logs grow over time).
• Perform regular backups of license files.

5. Plan for Growth:

Buy node licenses slightly ahead of your projected render node growth (e.g., if planning 30 nodes, buy 35 node licenses). This avoids license bottlenecks during peak render times.

6. Track Licensing Costs:

Keep a spreadsheet of:

• Workstation licenses: Count and annual cost.
• Node licenses: Count and annual cost per node.
• License server maintenance costs.
• Annual total cost and cost-per-render-hour.

This helps justify licensing investments to management and identifies optimization opportunities.

FAQ

Q: What's the difference between a node license and a render node license? A: In most contexts, they're the same. "Node license" and "render node license" both refer to a license designed for rendering on a farm node. Some vendors use "node-locked" to mean tied to a specific machine, while "floating node license" means managed by a license server. Always check your vendor's terminology.

Q: Can I use a workstation license on a render node? A: Technically yes, but it's wasteful. Workstation licenses include features (UI, modeling) you don't need on a headless render node. You'd be overpaying. Use render node licenses for farm nodes; they're cheaper and sufficient.

Q: What if my render node licenses are all in use and a new job arrives? A: The job queues until a license becomes available. Some render managers (like Deadline or Thinkbox) prioritize by submission time or job importance. If queue times are consistently long, consider buying additional node licenses.

Q: Can I share a single workstation license across multiple render nodes? A: No, it's both technically and legally problematic. Workstation licenses are tied to a single machine and don't support concurrent rendering across multiple nodes. Use floating licenses or per-node render licenses instead.

Q: What if I don't have enough licenses for peak load? A: Use a cloud render farm like Super Renders Farm. You pay per-render-hour instead of buying licenses. This shifts licensing costs from capital (upfront license purchase) to operational (per-job cost). Calculate break-even: if your farm utilization is < 40%, cloud rendering is usually cheaper than owning licenses.

Q: Can I move a render node license to a different machine? A: Depends on the vendor. Corona and V-Ray node licenses tied to a specific machine (node-locked) require reactivation on a new machine. Floating licenses are transferable by default—no hardware binding. Always contact the vendor before moving licenses to avoid deactivation issues.

Q: Do I need different licenses for different renderers (Corona, V-Ray, Arnold) on the same node? A: Yes, each renderer has its own licensing. A node rendering Corona doesn't consume a V-Ray license. If your nodes render multiple renderers, buy licenses for all of them.

Q: What if my license server fails? Can I still render? A: Only if you're using node-locked licenses. Floating licenses depend on the server; if it's down, renders can't acquire licenses and will fail or queue indefinitely. This is why redundant license servers (primary + backup) are critical for render farms.

Related Articles

For more on render farm setup and optimization, see our comprehensive guide on building a cost-effective render farm infrastructure. We also cover managed vs DIY rendering in our fully managed render farm guide.

For cloud-based rendering, explore our render farm pricing guide to understand cost-per-hour models and compare them to on-premises licensing.

Additional Resources

• Corona Renderer Licensing Guide — Official Corona licensing documentation
• V-Ray Licensing and Floating Licenses — V-Ray documentation for licensing models
• Autodesk Arnold License Management — Arnold licensing reference
• RLM License Server Documentation — Reprise RLM for floating licenses