April 7, 2026
How we built an in-house render farm for ₹18 lakhs — and why it beats cloud rendering for our workflow.
Cover Image Placeholder
When you're a boutique studio working on tight deadlines, render time is the bottleneck that keeps you up at night. A single 4K frame of an arch-viz exterior can take 30-60 minutes on a workstation. A 30-second animation at 24fps means 720 frames — that's 15 to 30 days of continuous rendering on a single machine.
The obvious answer is a render farm. The commercial options — Chaos Cloud, RenderStreet, PixelPlow — are excellent but expensive for Indian pricing. A single project can easily cost ₹50,000-1,00,000 in cloud rendering. Do that for 5-6 projects a month and you're looking at serious operating costs.
So we built our own. Our current setup is 8 workstations (each with an RTX 4090), networked via a 10GbE switch, running Deadline as the queue manager. Total investment: approximately ₹18 lakhs. At our current volume, that pays for itself in about 7 months compared to cloud rendering.
Key lessons from the build: (1) Don't skimp on cooling — rendering 8 GPUs simultaneously in a Mumbai summer generates serious heat. (2) Use enterprise SSDs for cache and project files — NVMe drives in RAID 0 gave us a 40% speedup in texture loading. (3) A dedicated render node (no monitor, no keyboard, just GPU and RAM) is 30% cheaper than repurposing workstations.
The biggest unexpected win was the ability to run overnight batch renders of variations. When a client says 'can we see it with marble instead of oak?', we queue 4 variations before we leave and have them rendered by morning. That speed of iteration has directly won us projects.