Loading...
Loading...
Landscape Architecture
Planting is what makes landscape scenes heavy: thousands of instanced trees, grasses and groundcover that push geometry and memory harder than any building shell. KinoCloud renders those scenes on cloud GPUs, with every job estimated before it runs and settled at no more than the quote you approved.
The honest answer is a workflow, not a slogan. Scatter systems and particle planting are standard Cycles work and instancing keeps their memory cost far below what the polygon count suggests — but planting density is still where render surprises live. So the platform is built around finding out cheaply: upload the scene with its dependencies, estimate the job, and trial one frame before committing the set. The estimate is quoted in hours and dollars and settlement is capped at it, which means the question "will this scene be a problem?" costs one test frame to answer instead of one blown evening.
Landscape work is presented in variants: the same courtyard at 9am, noon and golden hour; the same planting plan in spring and autumn. Rendered locally those variants queue — each one waits for the last. Submitted here, each variant is its own job with its own quote, and they render in parallel, so the whole study comes back together and its total cost was visible before the first frame started. The arithmetic stays legible: five lighting conditions is five estimates you approved, not one invoice you reconstruct.
Most landscape studios are small teams where render spend competes with billable hours. Three controls stack: every job is estimated and approved before it runs; settlement can never exceed the approved quote; and the account carries an optional hard USD budget with an auto-stop threshold that pauses new tasks at a chosen percentage. Sign-in is a browser login stored in the operating system keyring — no shared API key on the studio NAS — and practices that need it can put accounts behind SAML single sign-on.
Set the GPU class, frame count and expected per-frame time to see an indicative cost for a variant set. The in-plugin estimate is the one that caps settlement.
Estimated Total
*Pricing may not be accurate at the time of rendering
FAQ
Blender with the Cycles renderer, submitted through the downloadable KinoCloud add-on. The lane is still completing full production qualification, which is worth knowing before a submission deadline. Other applications and engines are listed on this page only once they are downloadable and provisioned.
Instanced geometry is standard Cycles territory, but planting density is exactly where render weight surprises live, so we will not promise "any scene renders" from a marketing page. The honest workflow is built in: estimate the job first, trial a single frame, and only then commit the batch. The estimate is also the ceiling on what you pay.
Yes. Each time of day — 9am, noon, golden hour — is its own job from the same scene, submitted together and rendered in parallel, each with its own approved estimate. The same pattern covers seasonal planting variants: spring and autumn are two jobs, not two afternoons.
Yes — an animation is a frame sequence, and sequences parallelise across GPUs instead of queuing on a workstation. For city-scale option studies specifically, the urban planning page covers that use in more depth.
No. Cycles ships with Blender at no cost, so the only spend is GPU time — and that is estimated and capped per job.
Settlement is capped at the quote you approved, so a long frame cannot bill past its estimate. Underneath that, the account can carry a hard USD budget with an optional auto-stop threshold, which pauses new tasks before a batch can drain a project allocation.