Loading...
Loading...
Urban Planning
Masterplans are rendered for audiences — planning committees, public consultations, investor reviews — on dates fixed by someone else. KinoCloud renders city-scale Blender scenes and flythroughs on cloud GPUs, with every job estimated up front and settled at no more than the quote you approved.
City models are big in a particular way: enormous repetition — street furniture, façade modules, block after block of context massing — which instancing renders far more cheaply than the raw polygon count implies. Rather than promise that any model of any weight will fly, the platform makes the real answer cheap to obtain: upload the scene with its dependencies, get the estimate, render one test frame. That single frame answers "will this be a problem?" before a consultation date depends on it, and the approved estimate caps the cost regardless.
A flythrough is the classic render-farm workload: ninety seconds at 25 frames per second is 2,250 frames, which is weeks of evenings on a workstation and a parallel batch on a farm. The estimate multiplies your per-frame time out to hours and dollars before you approve it, settlement is capped at that approved figure, and frames land while the team keeps working. When the consultation is over there is no idle hardware — the capacity simply stops costing anything.
Masterplan work is multi-party by default. Accounts are per person, so a practice, its visualisation consultant and a sub-consultant each carry their own budget and their own usage trail; organisations can put sign-in behind SAML single sign-on. Sessions live in the operating system keyring rather than in shared config files, and the REST and Python APIs let an option matrix — every massing variant, every time of day — be submitted as a scripted batch instead of by hand.
Frame count times per-frame time is the whole cost model — set both and see the indicative figure. The in-plugin estimate is the one that caps what you pay.
Estimated Total
*Pricing may not be accurate at the time of rendering
FAQ
Blender with the Cycles renderer, via the downloadable KinoCloud add-on. Full production qualification of that lane is still in progress — plan a consultation date with that in mind, and trial the scene early. Other applications appear here only once downloadable and provisioned.
Scale is a property of the scene, not a tier we sell, so the workflow is designed to answer the question cheaply: upload the model with its dependencies, estimate, and render one test frame before the sequence. Instancing keeps repeated urban fabric far cheaper than its polygon count suggests, and the estimate you approve is the ceiling on cost either way.
Each option — massing A against massing B, with or without the tower — is its own job from its own scene state. Options render in parallel and each carries its own approved estimate, so producing a like-for-like comparison set for a review does not queue on one workstation overnight.
Yes, and they price differently: a board still is one long frame with its cost quoted up front, while a flythrough is a frame sequence that parallelises across GPUs. Both come back through the add-on panel or the API.
The budget model is deliberately fixed-number-friendly: a hard USD cap on the account, an optional auto-stop threshold, per-job estimates approved before anything runs, and settlement capped at those estimates. Render spend for a bid or consultation cycle is a figure you set in advance.
No — Cycles ships with Blender at no cost. GPU time, estimated and capped per job, is the only render spend.