Eclipse

Eclipse Render Manager

Stop Babysitting Your Renders.

One place to monitor and manage all your renders, from a single Workstation to an entire Studio.

Join betaView Tutorials

Overview

One Dashboard
Control your Render Pipeline

Keep track of every render in one place. See what's rendering, what's finished, and what's next, all from one simple dashboard.

Eclipse Render Manager
Eclipse Render Manager Network Map with Coordinator and Render Nodes

Compatibility

Works with the appsyou already use.

Send a render from your 3D software. Eclipse handles the rest, on this computer or across your network.

Available now · Beta

Read more about Compatibility

Performance

The scene loads once*Not every frame.

Skip repeated scene prep on supported DCC workflows. More time rendering, less time loading.

* Houdini + Redshift comparison below. Scene reuse and speed gains depend on the render path and task size.

Same job · 100 frames · prep 1:12 + render 0:32

Other

2h 53m

Eclipse

54m 32s

You save 1h 58m on this shot alone.

Other managers

0s

Calculating & loading scene (1:12)

Eclipse

0s

Calculating & loading scene (1:12)

Houdini + Redshift example: per-frame loading versus scene reuse. Results vary by workflow.

Node Weights

Finish together.

Balance the split around each machine’s power. Less uneven work. More time rendering.

Node Weights

100 frames · mixed machines*

Finish together

Eclipse

No idle gap

Render-01Max

2× RTX 4090

Rendering

56 frames

Desk-MacBalanced

M3 Max

Rendering

33 frames

Laptop-02Light

Laptop GPU

Rendering

11 frames

Idle 0

* Simulation to show how Node Weights work. Not live farm data.

Two ways to work

Localwhen you're solo.Distributedwhen you grow.

One app, two modes. Same dashboard. Switch anytime with one toggle.

Jobs on your machine, one after another.

Local render queue

Your machine. Your queue. Ready to go.

One artist, one computer. A reliable queue with no network or coordinator.

  • Install on the machine you already render on.
  • Submit from your DCC like always.
  • Eclipse queues jobs while you keep working.
Read more about Local mode

Local mode

This machine · queue

1 slot

hero_shot

Running

Maya · 120 frames

product_turntable

Queued

Blender · 48 frames

lookdev_v03

Queued

Houdini · 12 frames

One computer. Jobs in order.

Submit

One Submit.Local or farm.

Local renders on this machine, one job at once. Distributed sends work to the Coordinator, then to compatible Render Nodes.

Network PC → Coordinator → Render Nodes. More compatible nodes, more tasks in parallel.

Computer on the network

Any machine that submits

Eclipse Coordinator

Same PC or another on the network. Runs the farm.

Render Nodes

Parallel work across the farm.

tasks in parallelon compatible Render Nodes

Submission modes

Four modes.One submit button.

Pick how your files reach the farm. Available modes depend on your DCC and renderer.

Messy paths. Scattered assets.

Scattered assets, one shared package. Eclipse collects supported scene dependencies and updates paths. Review any missing-file warnings before submitting.

C:/Desktop/shot.hipD:/tex/wood.exr~/Caches/geo.bgeoUSB/hdr.exr
Clean package//share/projects/…
Paths rewritten for every node

1. Gather

Scene + textures + caches from messy drives.

2. Package

One tidy project lands on the share.

3. Resolve

Every Render Node opens clean paths.

Day to day: Collect & Package. Shared Path for share-ready assets. Standalone with a licensed renderer CLI. USDZ Package for supported Solaris workflows.

Read more about Submission modes

Preview

See the frames.Flip the AOVs.

Scrub saved frames, switch AOVs and channels, catch issues early.* Includes multipart and multilayer EXR in supported workflows.

PreviewBeta
1920 × 1280
Beauty preview
Beauty.0001.jpg
Frame 1 / 1–100
100%
Output
Channel
11–100
1255075100

Setup

Zero IT theatre.Local capabilities just work.

Hosts, plugins, and renderer CLIs in one place. Check paths here; renderer licenses are separate.

  • Eclipse finds the DCCs and renderers on this machine.
  • Check this workstation here. Configure farm capabilities on each Render Node.
  • No IT checklist. Built for artists who just want to render.

How Distributed starts

  1. 1

    Install Eclipse Render Manager

    On one PC. That machine submits and runs the Coordinator.

  2. 2

    Install Render Node

    On every machine that should render, including the PC where ERM is running.

Eclipse Render Manager
Local capabilities overlay showing machine check ready status
Machine check ready. Then you’re free to render.

Insights

Know the cost.Day by day.

Which DCC burned the night, which engine won the week, and how quiet last month was.

Eclipse Render Manager · Insights

Insights

DayMonthYear

September 2026

Daily spend

Estimated cost by render node · per day

Farm-4090-AFarm-4090-BDual-3090mac-studioRN-WS-01RN-WS-02ThreadripperLaptop-RTX

Spent in September 2026

0

Jobs

€0.00

Spend +128%

Frames96,000
Time74d 6h
Energy1,520 kWh
Avg / day€17.37
Nodes8
Success91%

582 OK · 41 Fail · 17 Part

DCC

  • Houdini42%
  • Maya24%
  • Cinema 4D18%

Engine

  • Redshift34%
  • Octane28%
  • Arnold18%
StoryActivity

  • Jobs

    640 jobs · 96,000 frames

  • Most used DCC

    Houdini · 42% of time

  • Favorite engine

    Redshift · 34% of time

  • Busiest day

    Sep 12 · 38 jobs

  • Longest streak

    22 days back-to-back

vs quieter August 2026

Spend +128%Time +94%Jobs +110%
Distributed Insights: estimated cost by node, DCC and engine mix, and the render story for the month.

Projects

Think in shows.Not job ids.

Projects browses the shared folder by show. Open a project to see linked renders, disk use, and what is still running.

Eclipse Render Manager · Projects
Jobs QueueNetwork MapProjects
ReloadScan sizes

All projects

0

Projects

0 GB

On share

0

Linked jobs

Browse the share by show folder. Open a project to see linked renders without hunting job ids.

Storage by app

  • Maya29 GB
  • Solaris27 GB
  • Houdini16 GB
  • Blender9 GB

Shared folder

/Users/studio/EclipseData

Projects on the share

Click a folder to inspect linked jobs

Sort · Size

Selected project

Ep 03

Solaris · Shared Path

Size

27.4 GB

Linked jobs

6

Activity in this project

  • beauty_pass

    Solaris · Karma · Lighting

    Running

  • volume_holdout

    Solaris · Redshift · FX

    Queued

  • lookdev_hero

    Solaris · Karma · Lookdev

    Completed

Producers think in shows. Projects maps share folders to live farm jobs and disk use.

Click a project folder to inspect size, mode, and linked farm jobs.

GPU Frame Distribution

Every GPU earns its keep.One slot per card.

Enable split on the job and node for supported Redshift or Octane tasks. More cards, more parallel work.

RedshiftOctane

GPU split on

8 GPUs → 8 slots at once

One Render Node

GPUJobStatusProgress
  • 0chrome_sphere_turn.rsRunningDone
  • 1wet_asphalt_car.hipRunningDone
  • 2hero_octane_v03.hipRunningDone
  • 3city_block_rs.hipRunningDone
  • 4env_rsRunningDone
  • 5hero_rsRunningDone
  • 6crowdRunningDone
  • 7still_01RunningDone

Each enabled GPU gets a slot. Eight cards, eight tasks. Same node.

Eclipse Render Node
Eclipse Render Node with GPU Frame Distribution enabled, one slot per GPU

Notifications

Done or broken.Ping your Discord.

Wire a Discord channel in Settings. Pick which statuses fire. Scene, frames, and DCC land in your studio channel so you can keep working.

EclipseWebhook#render-alerts
CompletedEp 03 · beauty

Scene

beauty_pass.hip

Frames

1-240

DCC

Houdini · Redshift

Job

job_8f2a

EclipseWebhook#render-alerts
FailedCrowd Hero

Scene

crowd_main.ma

Frames

88-90

DCC

Maya · Arnold

Job

job_3c91

EclipseWebhook#render-alerts
PartialEnv · night

Scene

env_night.c4d

Frames

1-120 · 3 missing

DCC

Cinema 4D · Octane

Job

job_b7e0

Recap

Everything in one pass.The Eclipse checklist.

All the chapters side by side. Drag, scroll, or use the arrows.

Dashboard

One place for every render.

See what is running, waiting, and done. Local machine or whole studio.

Jump to section

Compatibility

Works with your apps.

Houdini, Maya, Blender, Cinema 4D, 3ds Max, Solaris, and the engines you already use.

Jump to section

Performance

The scene loads once.

Reuse scene preparation across frames in supported DCC workflows.

Jump to section

Node Weights

Finish together.

Weighted split. Balanced workloads. Actual finish times vary by frame.

Jump to section

Two ways

Local or Distributed.

Solo queue on your machine, or farm across Render Nodes. Same app.

Jump to section

Submit

One submit. Desk or farm.

Send from your DCC. Eclipse lines it up locally or through the Coordinator.

Jump to section

Submission modes

Four modes. One button.

Shared Path, Collect & Package, Standalone Renderer, or USDZ Package.

Jump to section

Preview

See frames. Flip AOVs.

Scrub saved frames, switch passes and channels, catch issues early.

Jump to section

Setup

Zero IT theatre.

Capabilities check on this machine. ERM on one PC, Render Node on every node.

Jump to section

Insights

Know the cost.

Render time, estimated energy and cost. See what burned the night.

Jump to section

Projects

Think in shows.

Browse the share by project folder. Linked jobs and disk use, not raw job ids.

Jump to section

GPU Frame Distribution

One slot per GPU.

Enable split on job and node. Supported Redshift and Octane paths.

Jump to section

Notifications

Done or broken. Discord.

Optional Discord pings for the job statuses you enable, to a channel you choose.

Jump to section

Dashboard

One place for every render.

See what is running, waiting, and done. Local machine or whole studio.

Jump to section

Compatibility

Works with your apps.

Houdini, Maya, Blender, Cinema 4D, 3ds Max, Solaris, and the engines you already use.

Jump to section

Performance

The scene loads once.

Reuse scene preparation across frames in supported DCC workflows.

Jump to section

Node Weights

Finish together.

Weighted split. Balanced workloads. Actual finish times vary by frame.

Jump to section

Two ways

Local or Distributed.

Solo queue on your machine, or farm across Render Nodes. Same app.

Jump to section

Submit

One submit. Desk or farm.

Send from your DCC. Eclipse lines it up locally or through the Coordinator.

Jump to section

Submission modes

Four modes. One button.

Shared Path, Collect & Package, Standalone Renderer, or USDZ Package.

Jump to section

Preview

See frames. Flip AOVs.

Scrub saved frames, switch passes and channels, catch issues early.

Jump to section

Setup

Zero IT theatre.

Capabilities check on this machine. ERM on one PC, Render Node on every node.

Jump to section

Insights

Know the cost.

Render time, estimated energy and cost. See what burned the night.

Jump to section

Projects

Think in shows.

Browse the share by project folder. Linked jobs and disk use, not raw job ids.

Jump to section

GPU Frame Distribution

One slot per GPU.

Enable split on job and node. Supported Redshift and Octane paths.

Jump to section

Notifications

Done or broken. Discord.

Optional Discord pings for the job statuses you enable, to a channel you choose.

Jump to section

13 features

Community

Join the community.Help shape what comes next.

Eclipse is built in the open with artists. Hop in Discord, grab the beta, and start rendering.

Join DiscordAsk questions, share setups, shape the roadmap with other artists.Continue →Join betaCreate an account. Download Eclipse from your account after signup.Continue →

FAQ

Questions artists ask.Straight answers.

Other managers, Local vs Distributed, setup, speed, and what Eclipse supports.

A lot of legacy managers feel stuck in time: slower updates, heavier installs, and UIs built for big facilities rather than freelancers and small studios.

Eclipse is built for that gap. Install in minutes, submit from your DCC, and switch Local or Distributed with one toggle. Supported DCC workflows reuse scene preparation across a job or slice to cut repeated loading.

You get a modern queue without babysitting a farm stack you do not need on day one.

See all FAQs

Top