Loading...
Loading...
Product Design
Product work is repetition at quality: one hero shot becomes twelve colourways, four angles and a turntable. KinoCloud renders those batches from Blender on cloud GPUs — scripted through the API or submitted from the viewport, estimated before they run, and settled at no more than the quote you approved.
This is the page's real subject, because it is where product rendering differs from every other visual field: the unit of work is rarely one image, it is a matrix. Nine finishes, three angles, two backdrops — fifty-four renders that are identical except for one variable. Through the REST API or the add-on's Python API, that matrix is a loop: estimate, submit, poll, fetch, each job quoted individually and all of them rendering in parallel instead of monopolising a workstation for a week. The person who wrote the loop approves the total before it runs.
A hero still is one frame of GPU time, quoted before it renders. A turntable is that arithmetic multiplied: a 360-degree rotation at 120 frames costs 120 times the per-frame time, and the estimate turns that into hours and dollars for approval before the first frame starts. Settlement is capped at the approved figure, so an e-commerce set or a launch turntable is a known cost at the moment it is commissioned — not when the invoice lands.
One-offs go through the viewport: the add-on submits the open scene with its dependencies, shows progress in a panel, and hands frames back without leaving Blender. Volume goes through the script: the same estimate-submit-poll-fetch cycle over REST, keyed by API keys, slotting into whatever automation already builds your product assets. Sign-in is a browser login held in the operating system keyring, teams can sit behind SAML single sign-on, and each account carries its own budget cap — so an agency's client work and a staff designer's experiments stay separately bounded.
Frames times per-frame time is the whole model — set both, pick a GPU class, and read the indicative figure. The in-plugin estimate is the one that caps settlement.
Estimated Total
*Pricing may not be accurate at the time of rendering
FAQ
Blender, rendering with Cycles, through the downloadable KinoCloud add-on — with full production qualification still in progress. KeyShot and CAD-native renderers are not supported; if your pipeline lives in one of those, we are not your farm today and would rather say so than waste your evaluation.
Yes — this is the workload the API exists for. Estimate, submit, poll and fetch are all available over REST with API keys, and from the add-on’s Python API, so "the same product in nine finishes against three backdrops" is a loop in a script, not twenty-seven manual submissions. Each job carries its own approved estimate.
A turntable is a frame sequence — a 360-degree rotation at, say, 120 frames — and sequences are what the farm parallelises. The estimate multiplies frames by per-frame time into a quoted cost before you approve it, and the finished frames come back through the panel or the API.
Jobs render your scene exactly as configured — same camera, same lighting rig, same colour management every time. Consistency across a catalogue comes from your scene template, and the farm’s job is to not touch it: nothing is restyled, relit or post-processed on our side.
No — Cycles ships free with Blender. The only render spend is GPU time, estimated per job and capped at the approved quote.
Per-job estimates are approved before anything runs and settlement cannot exceed them; the account can also carry a hard USD budget with an optional auto-stop threshold. A catalogue run for a client becomes a pre-approved figure, not a variable you explain afterwards.