September 15, 2026 Kelly Nguyen

How to Render Houdini on a Cloud GPU Server (2026): Licenses, Packages, Paths and husk, Step by Step

Executive SummaryKey Takeaways: Houdini on a Cloud GPU Server
Houdini / Karma / Redshift / Octane

What it takes to render a Houdini project on a remote GPU machine, based on SideFX documentation and FAQs:

  • Prepare before the server starts: note the Houdini and renderer builds, make paths relative to $HIP or $JOB, cache simulations and upload everything first.
  • Licensing is yours: login-based licensing lets a machine use sidefx.com as the license server; locked licenses are tied to hardware and computer name and must be returned before moving.
  • Install renderers with packages: a .json package file in a packages folder sets HOUDINI_PATH and other variables, with no houdini.env edits.
  • Render without the UI: husk renders a USD file with Karma or another Hydra delegate; hrender renders a ROP from a .hip file.
  • On iRender: install Houdini once on your server; the image is saved between sessions, so the next render starts in minutes.

A cloud GPU server is easiest to use for Houdini when you treat it as a second workstation: the same Houdini build, the same plugins, the same project folder, only more GPUs. Most failed renders on another machine come from licensing, plugin setup or file paths, not from the GPUs.

This guide walks through the whole setup: what to prepare before the server starts, how to license Houdini on another machine, how to install renderers with packages, how to keep paths working, and how to render with husk or hrender. It follows the SideFX documentation and licensing FAQ.

Checked against the SideFX Houdini documentation and FAQs, November 2026.

1. What do you need before rendering Houdini on a cloud GPU server?

Before the server starts, note your exact Houdini, renderer and plugin builds, make every file path relative to $HIP or $JOB, cache simulations to disk, and upload the whole project folder. None of this needs GPUs, so doing it first keeps paid machine time for setup checks and rendering only.

The figure shows the full workflow, split into what you do once and what you repeat for every render.

iRender
Rendering Houdini on a cloud GPU server: what happens when
HOUDINI
On your own computerno rental time✓ note builds✓ paths to $HIP / $JOB✓ cache sims to diskiRender Driveupload the whole project, freeYour iRender serverserver imagekept between sessionsPaid sessionsfirst sessioninstall + license + testlater sessionsrenderlater sessionsrenderBilled per minute only while the server runsShut down between jobs and billing stopsHoudini, packages and plugins stay installed
Render sessionsOne-time setupSaved server image
Session lengths are illustrative

On iRender the one-time part really is one time: your server image, including Houdini, packages and plugins, is saved between sessions.

2. How do you license Houdini on another machine?

The simplest way is login-based licensing, which lets the machine use sidefx.com as the license server: open the License Administrator and choose Use SideFX Servers. SideFX notes that the machine needs hserver 18.5 or later, and that a workstation license moved to login-based licensing is valid for one user on one computer at a time (SideFX: login-based licensing).

Locked licenses are registered to both the computer hardware and the computer name, so uninstalling Houdini is not enough to move them; you return them to your SideFX account and install them on the new machine (SideFX: moving licenses). The table lists the options.

LicensingHoudini on another machine

Ways to license Houdini on a cloud server

From the SideFX licensing FAQ.

OptionHow it worksGood to know
Login-based licensingThe machine uses sidefx.com as the license server; set it in the License Administrator with Use SideFX ServersNeeds hserver 18.5 or later; a moved workstation license is valid for one user, on one computer at a time
Move a locked licenseReturn the license to your SideFX account, then install it on the new machine with the License AdministratorLocked licenses are tied to hardware and computer name; uninstalling Houdini is not enough
Network license serverThe server points hserver at your studio license serverhserver talks to the license server (sesinetd); ports 1714 and 1715 must be open
Houdini IndieLocked to the machine; a subscription includes a supplementary license for a second computerA license set is 1 Indie, 1 Renderer and 1 Karma-Renderer
Simplest pathFor a single artist, login-based licensing avoids returning and reinstalling licenses each time you move between machines.

3. How do you install renderers and plugins so Houdini finds them? (step by step)

Install renderers and plugins with package files: .json files in a packages folder that tell Houdini how to change HOUDINI_PATH and other variables, so you do not edit houdini.env (SideFX: packages). Put one package per renderer in $HOUDINI_USER_PREF_DIR/packages, and if a plugin does not load, set HOUDINI_PACKAGE_VERBOSE=1 and run hconfig to read the package log (SideFX forum).

Server setup checklist (copy or follow line by line):

Server setup checklist
Houdini
Build → the same build as your workstation
License → License Administrator › Use SideFX Servers (login-based)
$HOUDINI_USER_PREF_DIR/packages → undefined
renderer.json → sets HOUDINI_PATH and PATH for Redshift or Octane
Debug → HOUDINI_PACKAGE_VERBOSE=1, then hconfig
$JOB = project root, files relative to $HIP / $JOB → undefined
.bgeo.sc / .vdb written to disk before rendering → undefined
NVIDIA driver 570 or later for Karma XPU → undefined
Render
Karma / Hydra → husk -f 1001 -n 100 -o render.$F4.exr shot.usd
ROP in a .hip → hrender -e -d /out/rop1 -f 1001 1100 shot.hip

Step 1: Install the same Houdini build

Use the exact build from your workstation, not simply the newest one. Renderer plugins are compiled for specific Houdini builds.

Step 2: Set up licensing

Sign in to the License Administrator and choose Use SideFX Servers, or point hserver at your studio license server. If Houdini reports that no license was found, check that hserver is running and that ports 1714 and 1715 are not blocked (SideFX licensing FAQ).

Step 3: Add the renderer packages

Install Redshift or Octane with the plugin build that matches your Houdini build, then add or copy its package file into the packages folder and sign in with your Maxon or OTOY license.

Step 4: Restore the project

Copy the project with the same folder structure, set $JOB to the project root, and open the scene. Check the console for missing HDAs, textures or caches before rendering anything.

Step 5: Test one frame

Render one frame to disk and compare it with your local render. Check the log for the device list, missing files and warnings.

Quick check: if the frame looks different from your workstation, compare the Houdini and plugin builds first. Version differences cause more surprises than hardware.

4. Why does a Houdini render fail or look different on another machine?

A Houdini render usually fails or looks different on another machine because the environment differs: no license is found, a renderer package does not load, file paths point to folders that do not exist, or the NVIDIA driver is too old. For Karma XPU, SideFX requires driver 570 or later (SideFX: Karma XPU).

The figure puts the four layers side by side; check them in this order before you suspect the GPUs.

iRender
Why a Houdini render fails on another machine: four layers that must match
HOUDINI
Your workstationFresh render serverLicenselicense foundLicenseno license foundhserver · 1714/1715Renderer packageRedshift / Octane ROPRenderer packageROP missingPACKAGE_VERBOSE=1File paths$HIP/tex/wood.exrFile pathsD:/tex/wood.exr$HIP / $JOBGPU driverNVIDIA 570+GPU driverold driver: XPU on CPUSideFX: 570 or laterMost failures are environment differences, not GPU problems: match these four first
Works locallyTypical first-run gapWhat to check
From SideFX docs and FAQ

For licensing errors, SideFX lists three usual causes: the license server (sesinetd) is not running, the license client (hserver) is not running, or a firewall blocks ports 1714 and 1715 (SideFX licensing FAQ).

5. How do you render: in the Houdini UI, with husk or with hrender?

For Solaris scenes, export USD and render with husk, the SideFX command-line tool that renders a USD file with Karma or another Hydra delegate. For ROPs inside a .hip file, such as Redshift or Octane in /out, use hrender. Use the Houdini UI for test frames. Command-line rendering keeps the viewport from using GPU memory during the render.

husk takes the USD file, an output image and frame options; for example -f sets the start frame and -n the number of frames (SideFX: husk). hrender renders a ROP with -d and a frame range with -f start end (SideFX: hrender). The table compares the three.

CompareWays to render

Houdini UI, husk or hrender?

From the SideFX husk and hrender references.

What it rendersWhen to use it
Houdini UIRender to Disk from a ROP or LOP nodeInteractive checks, small frame ranges
huskA USD file with Karma or another Hydra delegate (husk [options] usd_file -o image_file)Solaris scenes, long sequences, several processes on one machine
hrenderA ROP or COP network inside a .hip file (-d for the ROP, -f start end)Non-Solaris ROPs such as Redshift or Octane in /out
TipRendering from the command line keeps the viewport from competing for GPU memory while frames render.

6. SaaS or IaaS render farm for Houdini?

A SaaS render farm renders the Houdini builds, renderers and plugins it supports, which suits finished scenes that match its list. An IaaS server is a whole machine you set up yourself: your Houdini build, your packages and plugins, your license, and the same folder structure as at home, so the scene opens and renders as it does on your workstation.

A simple rule: if your setup is on the farm’s supported list and the shot is approved, a SaaS farm is a good fit. If you depend on a specific build, custom HDAs or plugins, use an IaaS server.

A test workflow on an iRender server

iRender
How iRender works: your computer controls your own multi-GPU server
IaaS render farm
Your PC or MacNo powerful GPU neededRemote desktopLive screen1:1 like your PCYOUR OWN GPU SERVERbare-metal · not sharedGPUGPUGPUGPUGPUGPUGPUGPU1, 2, 4 or 8 × RTX 5090 (32 GB) or RTX 4090 (24 GB)Threadripper PRO · 256 GB ECC RAM · 2 TB NVMe SSDFull admin access · your setup is saved between sessions1Register, top upFirst $50+ top-up doubled2Upload your projectiRender Drive, free3Start and connectRemote desktop, any OS4Render, shut downBilling stops, per minute✓ Your workstation, just more GPUs: no queue to wait, no farm plugin, no job submission, no settings changed
Your mouse and keyboardServer screen streamed back
Schematic, not to scale
  1. Upload the project, caches and textures to iRender Drive before you start the server; uploading is free and does not use rental time.
  2. Start a 4x RTX 5090 server, install your Houdini build and renderer plugins, and sign in with your own licenses. Your server image is saved between sessions. Billing is per minute.
  3. Render one test frame from the command line and compare it with your local render.
  4. Render the sequence, then shut the server down so billing stops.

Frequently asked questions

1. Can I render Houdini on a cloud GPU with my own license?

Yes. The simplest way for one artist is login-based licensing, which lets the machine use sidefx.com as the license server. Locked licenses can also be moved by returning them to your SideFX account and installing them on the new machine.

2. Which Houdini version should I install on the cloud server?

The same build you use on your workstation. Third-party renderers such as Redshift and Octane are built for specific Houdini builds, so a different build can stop the plugin from loading or change the result.

3. How do I install Redshift or Octane for Houdini on a new machine?

Use a package file: a .json file in a packages folder, such as $HOUDINI_USER_PREF_DIR/packages, that sets HOUDINI_PATH and other variables for the plugin. If it does not load, set HOUDINI_PACKAGE_VERBOSE=1 and run hconfig to see the package log.

4. Why are my textures pink or caches missing on the server?

The paths point to folders that do not exist on the new machine. Make paths relative to $HIP or $JOB, upload the whole project folder with the same structure, and check the render log for missing files.

5. What is husk?

husk is the SideFX command-line tool that renders a USD file with Karma or another Hydra delegate. You give it the USD file, an output image and frame options such as -f (start frame) and -n (frame count).

6. Do I need to keep the Houdini UI open while rendering?

No. You can render USD scenes with husk and ROPs in a .hip file with hrender from a command prompt, which also keeps the viewport from using GPU memory during the render.

7. Is Houdini pre-installed on iRender servers?

No. You install Houdini once and sign in with your own SideFX license. Your server image is saved between sessions, so Houdini, your packages and plugins are still there next time.

Render your Houdini Karma XPU scenes on iRender

iRender is an IaaS GPU render farm: you rent a bare-metal server with 4x NVIDIA RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. You install Houdini and use your own SideFX license; your server image is saved between sessions, so Houdini, your packages and the Karma XPU kernel cache stay installed. For Karma XPU we recommend the 4-GPU servers.

Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.

This video walks through rendering a Houdini Karma XPU scene on an iRender server in five steps:

New users get a 100% bonus on the first top-up (minimum $50). See the Karma XPU render farm page for server options, or download the iRender GPU app.

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by 4x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
, , , , , , ,

Kelly Nguyen

Kelly Nguyen is a customer support specialist at iRender who helps artists render Houdini, Blender and Cinema 4D projects on multi-GPU servers, and writes practical GPU rendering guides for the iRender blog.
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →