PU2LE is a free, public-beta tool that turns the PCs you already have into a distributed render farm for Blender, no cloud rendering subscription, no new hardware.
I'm not a software engineer. I studied architecture at Politecnico di Milano. But somewhere along the way I started noticing something that bothered me: people rendering, watching the same machine grind for hours, while every other computer around them, other PCs in the same studio, same office, sat there with a GPU doing absolutely nothing.
It felt like such a waste. All that idle GPU capacity, right there, unused, while one machine carried the whole rendering load alone. That observation is basically the origin story of everything that follows.
The idea
PU2LE turns the computers you already have access to, yours, a colleague's, a friend's, into a coordinated Blender render farm. A few things mattered a lot to me while building it:
- Only the people you choose ever see your work. Your project renders exclusively on machines you've picked, your own PCs, a colleague's, a friend's. Never on some shared render farm, never on a stranger's computer.
- You can run multiple jobs at once. Launch a render and start prepping the next project while it's running, you're not stuck waiting for one job to finish before starting another.
- You decide who works on what. Assign PCs project by project, a colleague's machine on this one, yours on that one, wherever they physically are.
- Nothing to configure. No terminal, no network setup, no IPs or firewalls to fight with. Install the plugin, connect the PCs, done.
Your own hardware does the actual rendering, nothing gets sent off to rent someone else's cloud GPUs. Once a render is done, the finished file just lands back on your dashboard automatically.
It's distributed rendering in the most literal sense: instead of one machine processing every frame in sequence, you split the work, different frames, or different render jobs entirely, across every PC you've got, and they all render in parallel.
Building it as someone who'd never built anything like it
The honest version of this story is a lot of trial and error. I knew what I wanted the thing to feel like, simple enough that you install it and forget it's there, long before I knew how to make that true technically.
The part I'm proudest of, looking back, is how the worker side ended up working. Each machine you add doesn't run Blender's render engine through some complicated integration, it just launches Blender itself in the background, the exact same way you'd launch it yourself, and lets Blender's own renderer (Cycles or Eevee) do what it already does well. Keeping that boundary clean, "don't get clever, just let Blender be Blender", turned out to be the decision that made everything else stable.
Everything else (the dashboard, the job queue, knowing which machine is doing what) is the part I actually had to learn from scratch, mostly by breaking it first.
What I didn't expect
Nobody warns you how much of building something solo is just sitting with the discomfort of not knowing if anyone will care. I still don't fully know. But I know the problem is real, I watched it happen, repeatedly, before I did anything about it.
Quick FAQ
What is PU2LE? A tool that coordinates Blender rendering across multiple computers you already own, so you don't have to buy new hardware or pay for cloud rendering.
Is it free? Yes, it's currently in free public beta.
Does it work with any renderer? It works with Blender's built-in renderers (Cycles and Eevee).
Where it's at now
PU2LE is in free public beta right now. If you've ever watched a Blender render crawl along while another computer sat there doing nothing, I'd genuinely love for you to try it and tell me what's broken, confusing, or just plain wrong: pu2le.com
Happy to talk through any of the technical decisions in the comments, including the ones I'd probably make differently now.
Top comments (0)