Render Farm Software Licensing: How V-Ray, Redshift, Arnold, and Corona Work on Farm

Introduction

Rendering a single frame on your workstation is straightforward — you have one license, one machine, one renderer. But the moment you distribute that workload across multiple machines, licensing gets complicated fast.

Licensing questions come up constantly in studio forums and support channels. Studios build or rent render nodes, only to discover that their render engine license doesn't cover farm use — or that the per-node cost they budgeted was based on outdated pricing that changed mid-year.

This guide breaks down exactly how licensing works for every major render engine when used on a render farm — whether that's your own hardware, rented GPU instances, or a fully managed cloud farm. It covers the mechanics of each model, the gotchas that catch studios off guard, and how different farm types handle the licensing burden.

If you're evaluating the full cost picture beyond licensing, the render farm build vs. cloud total cost comparison covers hardware, electricity, IT labor, and TCO analysis. This guide focuses specifically on the software licensing layer.

All pricing in this guide reflects publicly available rates as of early 2026. Vendor pricing changes frequently — verify current rates at the linked vendor pages before making purchasing decisions.

Why Render Farm Licensing Is Different from Workstation Licensing

A workstation license covers interactive use — you open your DCC application, load a scene, hit render. That's one seat, one machine, one user. Render farm licensing exists because farm nodes operate differently: they run headless (no monitor, no user interaction), execute batch rendering commands, and often need to spin up and tear down sessions across dozens or hundreds of machines.

Most render engine vendors distinguish between these use cases with separate license types:

License Type	Use Case	Typical Cost Model
Workstation/Interactive	Artist working in viewport, IPR, lookdev	Per-seat annual subscription
Render Node	Headless batch rendering on farm machines	Per-node annual subscription or floating
Floating/Server	Pool of licenses shared across machines	Concurrent-use licensing via license server
Command-Line Rendering (CLR)	DCC's built-in renderer via command line	Often free (3ds Max, Maya) or requires separate license (Cinema 4D)

The distinction matters because many studios assume their workstation license covers farm rendering. It usually doesn't — and running unlicensed render nodes can result in watermarked output, failed jobs, or license compliance issues.

V-Ray on Render Farms

V-Ray (by Chaos) is the most widely used render engine in architectural visualization, particularly with 3ds Max. Its licensing for farm use has several layers.

V-Ray Distributed Rendering (DR)

V-Ray's built-in DR mode spreads a single frame across multiple machines. It uses a spawner service (vrayspawner) running on each worker node. DR requires:

• A V-Ray workstation license on the submitting machine
• The vrayspawner service running on every worker node
• All worker nodes must have network access to the Chaos license server (default port configuration — check Chaos documentation for current port requirements)
• Identical V-Ray builds on submitter and all workers — even minor version differences (e.g., 6.20.01 vs 6.20.03) cause silent failures

For CPU rendering, DR is included with a V-Ray subscription at no extra per-node cost — worker nodes use the spawner service without checking out additional licenses. However, V-Ray GPU DR works differently: each participating GPU node must check out its own V-Ray GPU render license. This distinction catches studios that assume GPU distributed rendering is also free because their CPU DR works without extra licenses.

V-Ray with Deadline or Other Farm Managers

When rendering through Thinkbox Deadline or similar farm management software, each node renders complete frames independently rather than splitting single frames. In this mode:

• Each active render node checks out a V-Ray render node license
• Chaos sells single render node licenses at $208/year per node, with volume discounts available for multi-node packs (check Chaos pricing for current volume rates)
• A license server (on-premises or Chaos Cloud-hosted) manages the pool
• Unused licenses return to the pool when a node finishes its job

At the single-node rate, a 10-node local farm costs $2,080/year in V-Ray licensing alone — before hardware, electricity, or DCC application costs. Volume packs reduce this, but the exact discount depends on pack size and current Chaos pricing.

V-Ray on Managed Cloud Farms

On a fully managed render farm, V-Ray licensing is bundled into the per-hour rendering cost. Studios don't purchase, install, or manage V-Ray licenses — the farm provider maintains current builds across all nodes, handles license server infrastructure, and ensures version consistency. This eliminates what is arguably the single most common V-Ray farm failure: version mismatch between submitter and workers.

Managed farms that hold official Chaos render partner status maintain commercial licenses covering their entire fleet. The studio's only licensing requirement is their own workstation license for scene preparation.

Redshift on Render Farms

Redshift (by Maxon) is one of the most popular GPU render engines, primarily used with Cinema 4D and Houdini. Its licensing model changed significantly in 2025–2026, and the shift has caused real frustration among small studios.

The Maxon Teams Pricing Change

Historically, Redshift offered affordable node-locked licenses. In 2025, Maxon restructured pricing and introduced "Teams" licensing for multi-seat setups. As of early 2026:

• Individual license: $289/year (node-locked to one machine)
• Teams license: $329/year per seat (minimum 3 seats, floating)
• Studios with 3+ machines are pushed toward Teams pricing

The per-seat increase from Individual to Teams pricing — roughly 14% more per seat — adds up at scale. A studio with 5 GPU render nodes pays $1,645/year ($329 × 5) on Teams. For a 10-node GPU farm, that's $3,290/year — just for Redshift, before hardware or DCC application costs.

The larger issue isn't the price itself — it's the forced migration. Studios that bought node-locked licenses expecting long-term pricing stability found themselves required to switch models when Maxon restructured their licensing tiers. This has created real budgeting headaches for small archviz and motion design studios running 5–10 render nodes.

Redshift Command-Line Rendering

Redshift's command-line renderer (redshiftCmdLine) requires a valid license on each machine. Unlike some CPU renderers where the DCC application's command-line mode is free, Redshift always requires a license check — whether rendering interactively or in batch mode.

Redshift on Managed Cloud Farms

On managed cloud farms, Redshift licensing is included in the GPU rendering rate. Studios upload their Cinema 4D, Houdini, or 3ds Max scenes and render without dealing with Redshift licensing at all.

This is particularly relevant for studios frustrated by the Teams pricing change — on a managed farm, the licensing model is invisible. You pay per render hour, and whether Maxon changes their pricing structure next quarter doesn't affect your project budget.

Arnold on Render Farms

Arnold (by Autodesk) uses a different licensing approach that's more generous for small farms but more complex for large deployments.

Arnold's Bundled Render Nodes

An Arnold subscription ($415/year) bundles 5 render node licenses. This means a small studio can run a 5-node farm for Arnold rendering with just one subscription — a significant cost advantage over V-Ray or Redshift for small-scale farm use.

Additional render nodes beyond the bundled 5 can be purchased, but pricing varies by volume and agreement type. Autodesk's licensing uses RLM (Reprise License Manager), and each worker node must have network access to the RLM server to check out a license before rendering.

Arnold's kick Standalone Renderer

For farm rendering, Arnold typically uses kick — its standalone renderer that reads .ass (Arnold Scene Source) files exported from Maya, 3ds Max, or other DCCs. Key requirements:

• kick.exe (or kick on Linux) must be installed on every worker node
• The kick version must exactly match the Arnold plugin version used to export the .ass files
• All .ass file paths must be UNC-accessible (network paths, not local drive letters)
• RLM license server must be reachable from all worker nodes

Version mismatch between kick and the DCC plugin is one of the most common Arnold farm failures. Unlike V-Ray, where version mismatch produces an obvious error, Arnold mismatches sometimes produce subtle rendering differences — changed shading, missing AOVs — that aren't caught until final review.

Arnold on Managed Cloud Farms

On managed cloud farms, Arnold licensing works the same as other engines — included in the per-hour rendering cost. The farm provider maintains matching kick versions for each supported DCC version and validates .ass file compatibility during scene analysis before rendering begins.

Corona on Render Farms

Corona (by Chaos) shares some licensing infrastructure with V-Ray but has its own farm-specific considerations.

Corona Team Render

Corona's native distributed rendering system uses a client-server model:

• A Corona DR Server runs on the submitting machine
• Worker nodes connect to the server via Corona's default DR port
• Each worker node needs either a render node license or coverage under your existing subscription

Corona render node licenses are available as single-node subscriptions or in volume packs at reduced rates — check Chaos Corona pricing for current per-node rates. In general, Corona node licensing runs slightly cheaper than V-Ray.

Corona with Deadline

For larger productions, most studios use Corona through Deadline rather than the native Team Render system. Deadline handles node failures and job requeuing more reliably for long animation jobs. The licensing requirements are the same — each active worker checks out a Corona render node license.

Corona on Managed Cloud Farms

On managed cloud farms, Corona licensing is bundled into the CPU rendering rate. Farms with official Chaos partner status maintain current Corona builds and handle license distribution across their fleet. Corona's CPU-only architecture means it runs on standard CPU farm infrastructure with no GPU dependency.

Cycles (Blender) on Render Farms

Blender's Cycles renderer is open-source and free — including for commercial and farm use. There are no per-node licenses, no license servers, no subscription fees.

This makes Cycles the simplest engine to deploy on a render farm from a licensing perspective. The gotchas are operational rather than financial:

• Blender versions must match exactly between the submission workstation and all farm nodes — Blender doesn't guarantee .blend file compatibility across minor versions
• Add-ons and custom Python scripts need to be installed on every node
• CUDA/OptiX drivers must be consistent across GPU nodes for Cycles GPU rendering

Managed cloud farms typically maintain multiple Blender versions simultaneously so studios can render with their exact production version. The Blender cloud render farm pricing is generally comparable to licensed engines despite Cycles having zero licensing cost — the operational overhead of maintaining Blender infrastructure (version management, add-on support, GPU driver testing) is significant.

Octane on Render Farms

Octane (by OTOY) has the most limited farm licensing options among major render engines:

• Octane Studio (check OTOY's current pricing) covers 2 GPUs on a single machine
• Octane Enterprise (custom pricing) is required for any multi-machine or farm deployment
• There is no per-node render license option — Enterprise is the only path to farm use

This pricing model means that small studios looking to deploy Octane on their own render farms face a higher barrier to entry compared to engines like V-Ray or Redshift, where per-node licensing is straightforward. Enterprise licensing negotiations are typically oriented toward studios with 10+ GPU nodes and annual commitments.

On managed cloud farms, Octane licensing is bundled — but the Enterprise cost is typically reflected in the GPU rendering rate. Studios benefit from Enterprise-tier licensing without the minimum commitment or negotiation process.

The Three Farm Models: How Licensing Differs

Understanding render engine licensing requires understanding what type of farm you're using, because the licensing burden shifts depending on the model:

Model 1: Local (On-Premises) Farm

You own the hardware, you manage everything. Licensing is entirely your responsibility:

• Purchase render node licenses for every engine you use
• Install and maintain a license server (RLM, Chaos License Server, etc.)
• Keep all nodes on identical software versions
• Handle license renewals, migrations, and vendor pricing changes
• Budget for annual license cost increases (vendors frequently adjust pricing)

Typical licensing cost for a 10-node farm: $2,080–$3,290/year per render engine (V-Ray to Redshift Teams range), plus DCC application licenses where required.

Model 2: IaaS (GPU/CPU Rental)

You rent virtual machines or bare-metal servers from a provider (AWS, Google Cloud, or specialized GPU rental services). The hardware is theirs; the software is your problem:

• You still need render node licenses — most IaaS providers don't include them
• You install the DCC application and render engine on each rented machine
• License server must be accessible from the cloud (VPN or cloud-hosted license server)
• You manage version consistency across rented nodes
• Some providers offer "marketplace" images with pre-installed software, but licensing is still separate

IaaS eliminates hardware costs but retains all the licensing complexity and operational overhead of a local farm. It's not uncommon for studios to switch from IaaS to managed farms specifically because of licensing frustration — they expected "cloud" to mean "everything included," but IaaS is really just remote hardware.

Model 3: Fully Managed Cloud Farm

The farm provider handles everything — hardware, software installation, licensing, version management, job queuing, and output delivery. From the studio's perspective:

• Upload scene file → wait → download rendered frames
• Zero licensing cost beyond your own workstation license
• No license server to manage
• No version mismatch issues (the farm validates compatibility before rendering)
• Pricing is per render hour (CPU) or per GPU-hour — all licensing is embedded

This is the model that farms like Super Renders Farm operate — commercial partnerships with vendors like Chaos and Maxon cover licensing across the entire fleet. When Maxon changes Redshift pricing, or Chaos adjusts V-Ray node licensing, the per-hour rate absorbs it.

The trade-off: managed farms give you less control. You can't choose specific hardware configurations, you're limited to the software versions the farm supports, and per-hour rates include the farm's margin on top of raw compute costs. For studios with predictable, high-volume rendering needs, a local farm with owned licenses may be more cost-effective long-term. Managed farms make the most financial sense for variable workloads and studios that don't want to maintain rendering infrastructure.

Licensing Comparison Table: All Engines on All Farm Types

Engine	Local Farm (per node/year)	IaaS (your license)	Managed Cloud Farm
V-Ray CPU	$208 single (volume discounts available)	Same	Included
V-Ray GPU	$208 single (volume discounts available)	Same	Included
Redshift	$289 individual / $329 Teams	Same	Included
Arnold	Bundled (5 nodes with subscription), then custom	Same	Included
Corona	Per-node subscription (volume discounts available)	Same	Included
Cycles (Blender)	Free	Free	Included
Octane	Enterprise (custom)	Enterprise (custom)	Included

The "Included" column for managed farms is the key takeaway. Every engine, regardless of its vendor pricing model, becomes a single line item (render hours) on a managed farm. Studios rendering with multiple engines — say V-Ray for archviz and Redshift for motion design — avoid stacking license costs across engines.

Common Licensing Mistakes Studios Make

These are the licensing mistakes that cost studios the most time and money:

1. Assuming workstation licenses cover farm nodes. Most render engine workstation licenses explicitly exclude batch/farm rendering. Running farm jobs on workstation licenses may produce watermarked output or trigger compliance flags.

2. Forgetting DCC command-line licensing. 3ds Max and Maya allow free command-line rendering (no additional license needed for farm nodes). Cinema 4D does not — each farm node needs a Team Render Client license or a full Cinema 4D license. This catches studios migrating from Max/Maya workflows to C4D.

3. Running mismatched versions across nodes. Not strictly a licensing issue, but version mismatch is the most common farm rendering failure, and it's directly caused by the operational burden of managing software across multiple machines. On a local farm with 10 nodes, updating V-Ray means touching 10 machines and verifying each one. One missed node means inconsistent rendering.

4. Not budgeting for annual price increases. Render engine vendors adjust pricing regularly. Maxon's 2025 Teams migration, Chaos's volume pack restructuring, and Autodesk's subscription-only shift all changed per-node economics within the past two years. Studios that budgeted based on 2023 pricing are paying 10–20% more than expected.

5. Ignoring license server infrastructure. License servers need to be highly available — if your RLM or Chaos license server goes down, your entire farm stops rendering. Redundancy, monitoring, and maintenance of license infrastructure is an operational cost that rarely appears in TCO calculations.

How to Evaluate Licensing When Choosing a Render Farm

When comparing render farm options, ask these questions about licensing:

• Is render engine licensing included in the price? If not, calculate the per-node annual cost for every engine you use and add it to the quoted rate.
• Who manages the license server? On IaaS platforms, you typically manage this yourself. On managed farms, it's handled for you.
• What happens when a vendor changes pricing? On a local farm or IaaS, pricing changes hit your budget directly. On a managed farm, the provider absorbs vendor pricing changes.
• Are all your DCC versions and render engine versions supported? Version coverage matters — if the farm doesn't support your specific Redshift build, you can't render.
• Is there a minimum commitment? Some IaaS providers require minimum monthly spend. Most managed farms operate on pure pay-per-use — render when you need to, pay nothing when you don't.

For a deeper look at how per-hour and per-frame pricing models compare across farm types, see the render farm pricing guide.

FAQ

Q: Do I need a separate render engine license for each farm node? A: On a local farm or IaaS setup, yes — each node that actively renders needs its own render node license (or coverage from a floating license pool). On a fully managed cloud farm, render engine licenses are included in the per-hour rate, so you don't purchase or manage them separately.

Q: Is Blender Cycles really free to use on a render farm? A: Yes. Blender and Cycles are open-source under the GPL license, which permits commercial and farm use with no per-node fees. The costs on a render farm are purely operational — hardware, electricity, version management — not licensing.

Q: How much does V-Ray licensing cost for a 10-node render farm? A: V-Ray render node licenses cost $208 per node per year at the single-node rate, with volume discounts available for multi-node packs. At the single-node rate, a 10-node farm runs $2,080 annually in V-Ray licensing alone. On a managed cloud farm, this cost is embedded in the per-hour rendering rate.

Q: Why did Maxon change Redshift pricing to Teams? A: Maxon introduced Teams pricing ($329/year per seat, minimum 3 seats) to replace node-locked licenses for multi-seat setups. The change moves Redshift toward a floating license model, which gives studios more flexibility in how licenses are assigned but increases per-seat cost compared to individual node-locked pricing ($289/year).

Q: What's the difference between IaaS GPU rental and a managed render farm for licensing? A: On IaaS (like renting GPU VMs from AWS or specialized providers), you rent hardware but manage software and licensing yourself — you need your own render node licenses, install software on each machine, and maintain a license server. A managed render farm handles all of this: software installation, licensing, version management, and job execution are all included in the service.

Q: Can I use my existing V-Ray workstation license on a cloud render farm? A: Not for farm rendering. V-Ray workstation licenses cover interactive use on one machine. Farm rendering (batch processing across multiple nodes) requires render node licenses. On a managed cloud farm, the farm's own commercial licenses cover rendering — your workstation license stays on your local machine for scene preparation.

Q: Does Arnold really include 5 render nodes with a subscription? A: Yes. An Arnold subscription ($415/year) bundles 5 render node licenses managed through Autodesk's RLM system. For studios with small farms (5 nodes or fewer), this makes Arnold one of the most cost-effective engines for distributed rendering. Beyond 5 nodes, additional licenses are available at custom pricing.

Q: What happens if my license server goes down during a farm render? A: On a local farm, nodes that can't reach the license server will stop rendering — jobs fail or queue until the server is restored. This is why license server redundancy is critical for local farm operations. On a managed cloud farm, the provider maintains highly available license infrastructure, so individual server failures don't interrupt rendering.