Skip to content
Cindergrid

Who renders here, and how much

Three studios that agreed to share numbers from real productions in 2026.

Tidewater Frames

Animated series, Gothenburg. 22 artists. Plan: Pipeline.

Episode 4 of a 13-part series had 38 minutes of hair-heavy animation and a deadline that fell on a bank holiday. Tidewater submitted 54,720 frames from Maya with Arnold on Kiln C128 nodes, peaking at 1,920 nodes in eu-north.

11 days
wall time instead of 7 weeks
212 TB
of EXR passes downloaded

Marrow & Pike

VFX boutique, Bristol. 9 artists. Plan: Studio.

Fluid and smoke caches of 1.8 TB per shot used to take two evenings to upload on a 1 Gbit/s office line. With content-hashed chunks the second iteration of a shot uploads in under 10 minutes.

Houdini 21, Karma XPU on Arc G4. Typical shot: 140 frames, 41 minutes per frame.

Orchard Lane Architectural

Visualisation, Melbourne. 14 artists. Plan: Studio, with spiky Spark-sized weeks.

Fly-throughs in Unreal Engine 5.6 at 4K, 60 frames per second, 90 seconds each. The team moved to ap-oceania in September to cut round-trip time and now sees frames appear on the review board 6 seconds after they finish.

"The surprise was how dull the invoices became. Same line items each month, a cost cap on every job, nothing to explain to finance." - Hannah Whitlam, studio manager

What studios ask us for

  • Predictable invoices: cost caps per job, tags per show, CSV export per department.
  • Fast turnaround on first frames: scene upload and the first frame back usually take under 20 minutes for a 100 GB scene.
  • No lock-in: all outputs are standard EXR, PNG, or whatever your renderer writes. Export everything with one command.
  • Reliable support: engineers read the same queue the customers do. See contact.

Want your numbers here? We do not publish studio names or volumes without a written agreement, and we will not ask for it as a condition of any plan.

Bring a shot that has been giving you trouble.

Try it with free credit