THE RENDER WORKFLOW

One managed workflow,
from upload to output.

BDCEG breaks supported Blender jobs into frame tasks, dispatches them to enabled worker computers and keeps the progress visible in one portal.

Plan a pilot →
01
STUDIO PORTAL

Prepare and submit

A client account uploads a Blender .blend scene, sets a job name, frame range, output resolution and sample count. Pack external textures and assets in the Blender file before submission.

InputPacked .blend sceneControlsFrame range · resolution · samples
02
CONTROL SERVER

Queue and assign frames

The portal creates one task per frame. Enabled workers poll over outbound HTTPS, receive a lease and claim work within their configured concurrency limit.

Queue statusQueued · running · completed · failedRecoveryExpired leases are retried within policy.
03
AUTHORIZED WORKER PC

Render with Blender

The Windows agent downloads the assigned scene, launches Blender in background mode for one frame and returns the rendered image through the protected worker API.

AgentWindows 10/11 · Python packaged agentSecurityPer-node token · TLS verification
04
CLIENT PORTAL

Review and download

Job details show frame-level status, attempts and worker assignment. Completed output frames can be downloaded together as a ZIP file.

OutputPNG frames in a ZIP archiveAccessOnly the owner and authorized staff
Good to know

The first release focuses on Blender frame rendering. It does not package arbitrary external dependencies automatically. Projects should include packed assets, and worker PCs should use compatible Blender versions.

Have a scene that’s ready to test?

We can start with a representative 2–3 frame project and a small authorized worker pool.

Talk to BDCEG →