About
Built between deadlines.For people who actually render.
I'm Federico Ventura. I work in advertising and product visualization. Eclipse Render Manager started as the tool I needed when other managers wasted hours on scene reloads, babysitting, and farm friction.
It grew into a real product: Local on one machine, Distributed across a short farm, Render Node on every box that burns frames. Now it is in beta for other artists and small studios who want their time back.
Why Eclipse exists
Stop babysitting renders. Keep making the shot.
Scene prep once where the DCC + renderer path allows it. A clear queue. Logs and Preview beside the job. A farm that does not need a full-time TD to stay honest. That is the bar.
Local
One workstation. Zero network setup. Submit from your DCC and let the queue run.
Read moreDistributed
One job across the farm. Coordinator plans. Nodes claim slices. Same Eclipse app.
Read moreRender Node
The worker on every box that renders. Active when it should work. Paused at the desk.
Read moreHow it is built
Production first. Corporate bloat never.
Every feature has to survive a real client night: submit from Houdini, Maya, Blender, Cinema 4D, 3ds Max, or Solaris; watch the farm; relaunch what failed; open the render folder; move on. If it does not earn that, it does not ship.
The product is in beta. Join free, break things, tell us what hurts. Paid plans open when the beta ends, with notice.
Company
Federico Ventura SRLS
Eclipse Render Manager, including the apps, website, branding, and documentation, is owned by Federico Ventura SRLS. See Terms for the full intellectual property statement.
Via Gaetano Donizetti 2, 22063 Cantù (CO), Italy
VAT IT04000010134