Blender Render Farm

How cloud rendering works with Blender

Install the KinoCloud add-on and sign in from inside Blender. Sign-in is a normal browser login and the session is kept in your operating system keyring, so there is no API key to paste into a preferences field or commit to a project repository. The add-on adds a Kino Cloud panel under Properties → Render.

Before anything runs you get an estimate for the job as configured — estimated hours and dollars. You approve that estimate, the scene and its dependencies upload, and the job is dispatched to KinoCloud GPUs. Settlement is capped at the quote you approved, so the estimate is a ceiling rather than an opening bid.

While the job runs the panel polls its status, so you can watch frames complete, cancel a job that has gone wrong and download finished output without leaving Blender. Every one of those operations is also available from the add-on’s Python API when you would rather drive it from a pipeline script.

Why Blender artists render on KinoCloud

Cycles is the target renderer and no third-party render licence is involved — there is nothing to bring, buy or float beyond Blender itself, which is not true of most commercial engines on a render farm.

Cost control is enforced rather than advisory. Every job is estimated before it runs and capped at that estimate on settlement, and an account can carry a hard USD budget with an optional auto-stop threshold that pauses new tasks at a chosen percentage of the cap.

Worth knowing before you commit a fixed delivery date: Blender is our only provisioned render candidate and its lane is still completing full production qualification. We would rather say that here than let you find out on a deadline.