Cloud rendering credits turn GPU cost into a metered utility bill

The picture

KeyShot's own Cloud Rendering page, retrieved 16 September 2026, states one KeyShot Credit equals one GigaSample of render compute, calculated as width times height times samples per pixel times frames, divided by one billion, sold in prepaid packs where larger packs lower the per-credit cost, and available to KeyShot Studio subscribers from version 2026.2. Chaos's own cloud page sells a parallel system it calls Chaos Credits, structured as three monthly-refreshing prepaid tiers - Starter at 250 credits, a mid tier at 1,000, and an upper tier at 3,000 - shared across a floating licence and, per the page's own feature lists, spent on both rendering and AI-generation outputs.

What the documents show

KeyShot's page states a checkable formula for what a credit buys; this retrieval could confirm that definition directly from the page's own text. Chaos's page states credit volumes and tier structure but loads its dollar-per-credit and per-tier prices through a script this retrieval could not execute, so no figure for Chaos Credits is asserted here - a living-document limitation worth flagging rather than papering over with a number from elsewhere. Both vendors' pages describe cloud rendering as supplementary: KeyShot's page frames it as a way to "keep your local machine free" rather than a replacement for local rendering.

What it is allowed to decide

A billing mechanism is a procurement decision, not a technical authority; neither page's credit system changes whether a render's lighting or physics is correct. What credit-based pricing does support, per KeyShot's own documented formula, is a genuine capacity substitute for owning a GPU-heavy workstation - a studio can rent exactly the GigaSamples a job needs rather than provisioning peak hardware year-round. Whether that substitute is cheaper than ownership depends on utilization neither vendor's page quantifies for a specific studio, so this entry does not assert cloud credits are cheaper in general; that would extend the sources beyond what they state.

The disclosure label

A render billed through cloud credits, disclosed as of 16 September 2026, should state which service and credit definition were used, and, where a dollar figure is quoted, whether it came from the vendor's own published rate or an unverified secondary estimate. A studio's production manager tracking render spend would be the plausible party asserting that disclosure.

• Does the studio's actual render volume make prepaid credits cheaper than the hardware they replace, or is that unverified?
• Is the quoted per-credit price drawn from the vendor's own page, or estimated from a tier name alone?
• Are rendering credits and AI-generation credits being tracked as the same budget line, when they buy different things?

Credit-based cloud rendering is real and documented, but only as detailed as each vendor's own page discloses; where that disclosure stops short of a dollar figure, as it does here for Chaos, the honest record stops there too.