Loading...
Loading...
Media & Entertainment
KinoCloud is a GPU render farm you drive from inside Blender. Submit a scene, see the estimated hours and cost before anything runs, and pay no more than the quote you approved. There is no farm to provision, no render manager to license and no cloud account to wire up.
That is the whole point of renting frames instead of buying a workstation. Submit from Blender and the job runs on KinoCloud GPUs while your machine stays free for the next shot. The add-on polls progress in a panel next to your viewport, so you can watch a sequence land, cancel a job that has gone wrong and pull finished frames without leaving the application. When the deadline passes, the capacity goes away and so does the cost — there is no idle hardware to justify between projects.
Every job is estimated before it runs, in hours and dollars, and you confirm the estimate before a single frame starts. Settlement is capped at that quote: the number you approved is a ceiling, not an opening bid. On top of that you can set a budget — a hard USD cap — in the plugin, with an optional auto-stop threshold that pauses new tasks at, say, 90 per cent of the cap. For a small studio, that combination is the difference between experimenting with cloud rendering and being afraid of it: an unattended overnight render cannot spend more than you allowed it to.
Sign-in is a normal browser login and the session lives in your operating system keyring, so no API key ends up pasted into a scene file or committed to a show repository. For automation, the add-on exposes a Python API backed by the shared KinoCloud client, and the platform exposes REST endpoints with API keys — estimate, submit, poll status and fetch outputs can all be driven from your own pipeline tools. Studio accounts can use SAML single sign-on so artists do not manage separate credentials.
Set the shape of your job — GPU class, frame count and expected time per frame — to see an indicative cost. The estimate you get inside the plugin is the one that caps your settlement.
Estimated Total
*Pricing may not be accurate at the time of rendering
FAQ
Blender is the publicly available integration today — a downloadable add-on that submits Cycles renders straight from the viewport. It is our only provisioned render candidate and full production qualification is still in progress, so we describe it as available to try rather than production-certified. Further DCC integrations are listed here only once they are downloadable.
No. You sign in to KinoCloud through a normal browser login and the session is stored in your operating system keyring. Rendering is proxied through KinoCloud, so there are no cloud credentials, farm IDs or storage buckets to configure — and no API keys pasted into scene files.
Yes. Every job can be estimated first — estimated hours and dollars — and you confirm before anything starts. Settlement is capped at the quote, so the estimate you approved is the ceiling rather than an opening bid.
Set a budget — a USD cap — directly in the plugin, optionally with an auto-stop threshold such as pausing new tasks at 90 per cent. The panel shows live usage against the cap and warns as you approach it, so an unattended overnight render cannot quietly spend more than you allowed.
Cycles. Full production qualification must complete before we describe the lane as live, and we will say so on this page when it does.
Not for Blender — there is no third-party renderer licence to buy or bring. Commercial renderers that are licensed per node are a different question and are handled per render lane.
The plugin polls job status and shows progress in the panel. You can cancel a running job or download the outputs from that same panel, or drive both from the add-on’s Python API if you would rather do it from a pipeline tool.
Yes. The Blender add-on exposes a Python API backed by the shared KinoCloud client, and the platform offers REST endpoints with API keys so estimate, submit, poll and fetch can all be scripted from your own tooling.