Graphics

Model, animate,then render it

Blender, on a Void Linux desktop of your own.The whole suite in a tab, and the render on cores you rented for the day.

Blender 5.0.04 cores · 8 GBOpens in a browser tab

hub://blender

$ dxflow workflow create --identity blender hub://blender --start --link

01Pick a machinecores, memory and a rate per hour

02Create the workflowpulled from the hub, once

03Run it, then stopstopped when the work is done

The application

One suite,the whole pipeline

Modelling, sculpting, simulation, compositing and rendering in one program.

Model and sculpt

Meshes, modifiers, geometry nodes and a sculpt mode with dynamic topology.

Cycles and EEVEE

Render interactively, or let Cycles use every core the machine has.

Headless for the long one

blender -b renders the same .blend from a shell, frames landing on the volume.

How you run it

Every defaultis one override away

The session reads its settings from the environment, so you set them on the start line.

VNC_PASSWORDWhat the tab asks for. It ships as dxflow, and everyone reading this knows that.

PANEL and TASKBARBoth hidden, so the viewport has the whole screen. Show either one to get the desktop back.

AUDIOOff here. Turn it on and the sequencer plays back with its sound.

start it your way

$ dxflow workflow start blender --override env.app.VNC_PASSWORD=something-long

$ dxflow workflow start blender --override env.app.TASKBAR=show --link

The session

The viewportfills the screen

Streamed to your browser, with Blender already maximized.

6082Browserin the tab, at /vnc.html

5901VNCin a native client

/volumeStorageyour files, kept between runs

Open it from anywhereStart with --link and the session comes back on an HTTPS address.

Set a password firstVNC_PASSWORD defaults to dxflow, and everyone can read this page.

Good to know

Cycles runson the cores

There is no card to offload to here. The viewport is software OpenGL and the renderer is the CPU.

Buy cores, not a GPU

A heavier scene wants more cpu on the step. That is the lever that moves a render time, not the graphics card.

Render without watching

blender -b from a terminal in the desktop runs the frames headless, which is the sensible way to spend a long render.

Scenes belong on the volume

Keep the blend file, the textures and the output frames under /volume so a stopped machine loses none of it.

The image

Pulled once,then it stays

Blender arrives as one image. This is what comes down the first time, and what the disk should have free for it.

569Mamd64compressed, the way the registry counts it

515Marm64compressed, the way the registry counts it

20GOn diskunpacked, with room to work beside it

ghcr.io/dxflow-ai/blender:latestPublished from the hub, pulled on the first start and kept for the ones after it.

Either architectureamd64 and arm64 are both published, and the machine pulls the one it runs.

What it asks for

What it wants,and what it needs

The definition asks for 4 cores and 8 GB. The image comes up on less than that, and a start given --fit trims the ask to whatever the machine actually has.

4 cores · 8 GBAsks forwhat the definition writes down

2 cores · 4 GBRuns onthe least the image comes up on

Not neededGPUit works on the cores alone

The ask is not the floorThe definition writes down what suits the work. The image itself starts on less, which is what the second figure is.

--fit caps it to the hostA start given --fit trims each step to what the machine actually has, for that start alone. The definition is never rewritten.

Machines that fit it

Blender asks for 4 cores and 8 GB. Cheapest first.

E2 Standard-4

$0.168/ hour4 cores · 16 GBStart this machine

T4g XLarge

$0.168/ hour4 cores · 16 GBStart this machine

C7g XLarge

$0.181/ hour4 cores · 8 GBStart this machine

Run Blender on your own machinePick a machine that meets it, and it opens about a minute after you ask.

Start Blender Browse workflows