Made for Artists by Artists: The Power of Independence

It’s been almost a year since AWS placed Thinkbox Deadline 10 into ‘maintenance mode.’ With a year passing, I wanted to take a look at what those repercussions have meant to its users and the platform as a whole. Maintenance mode translates to… ‘Security & Critical Fixes mode’. Application support (Maya, Houdini, etc) is frozen, meaning any new version of those tools risks breaking Deadline integration.
Existing farms keep running, but active development has stopped and users are being pointed toward a cloud service instead for a higher cost (e.g. 10 of your machines cost $1,314/year in Deadline Cloud software fees alone, not the hardware, nor the VM, nor Maya licensing).

I want to start by saying something that might surprise you, coming from a competitor, Deadline was a good piece of software. For two decades it was the backbone of many render farms, from two person studios to the biggest facilities in the industry. Anyone who builds render management tools, and I’ve been doing it for 25 years, competed against Deadline with respect. It earned its place.

Which is exactly why the past few months have been hard to watch. Spend any time in the forums and community threads and you won’t find much anger. You’ll find something closer to grief, mixed with three very reasonable questions. Will the tool I built my pipeline on still exist in 3 years? What will rendering actually cost me by the hour in a few years? And how did a decision this fundamental to my studio end up being made in a boardroom I’ve never seen?

I can’t answer those questions on AWS’s behalf. But I can tell you how I think about them, because they’re the questions I’ve spent my whole career answering.

The roadmap problem

A render manager isn’t like other software. It sits underneath everything, every DCC, every renderer, every delivery deadline. When it works, nobody thinks about it. When its development stops, the problems don’t arrive on day one. They arrive slowly: the new Houdini version that isn’t supported, the OS update that breaks a submitter or everything (Mac Arm CPUs…), the plugin that nobody is maintaining anymore. Security fixes mode doesn’t mean your farm stops working. It means your farm stops keeping up with your work and therefore degrades.

That’s why the question that matters isn’t “does it still run today?”
It’s “who is committed to it in five years, and what are their incentives?”

The independence question

Here is the uncomfortable truth about creative industry software in 2026, most of the tools studios depend on are owned by companies whose real business is something else. When a render manager belongs to a cloud provider, the roadmap will eventually serve the cloud. I don’t mean  to sound cynical, but it’s just how incentives work. The product that was free becomes the on-ramp; the on-ramp leads somewhere with a meter running.

I made a different choice 25 years ago, and I’ve made it again every year since. Binary Alchemy has never been acquired although there have been interested parties. Royal Render has no parent company whose strategy it serves. No stockholders that demand a 3% increase no matter what. When our users ask for a feature, there is no committee weighing whether it drives cloud consumption. There’s a development team, one I still lead, asking only whether it makes rendering better for the people doing the work.

That independence isn’t a marketing line. It’s the reason we’re still here, a quarter of a century on, while so many of the tools in our industry are not.
(RIP Shake, Softimage, mentalRay, Mudbox, FreeHand 🙁 )

The control question

The studios I talk to aren’t against the cloud. Most of them use it, and Royal Render works happily in hybrid pipelines. What they’re against is being moved, having the choice made for them, on someone else’s timetable, at a price they can’t predict.

I think that instinct is exactly right. Your render farm isn’t just a simple workload to be migrated. It’s the infrastructure you’ve shaped around your shows, your scripts, your way of working. The hardware in your machine room, the pipeline your TDs have refined over years, that’s an asset, not a legacy problem. Any vendor who tells you otherwise is describing their business model, not your interests.

So, my advice to studios weighing their options right now is simple, and it applies whichever tool you end up choosing: don’t panic-migrate, but don’t wait for something to break mid-show either. Use this calm window to evaluate properly. Ask every vendor the three questions above, who owns you, what will this cost me in year three, and what happens to my existing pipeline. The answers will tell you most of what you need to know.

An open door

Twenty five years ago I started to craft Royal Render because, as a TD, I wanted a render manager that answers directly to artists rather than to a separate render wrangler, removing the mundane tasks like frame checking, empowering artists to unleash their full creative potential. That’s still the whole idea. Your farm, your hardware, your rules. Made for artists, by artists, render on your terms.

Holger Schönberger is the founder of Binary Alchemy and lead developer of Royal Render, the independent render manager, celebrating 25 years in 2026.