Blender Render Farm

Build a real Blender scene, render even and odd frames in parallel using Cycles on the CPU, compose an MP4, and verify all six frames. The default command uses Docker, so the host does not need a Blender installation. No JSON file is represented as a .blend file.

Run locally

Requires Go and Python 3.12+. Blender Render Farm also requires Docker. Run from a fresh checkout:

git clone https://github.com/UFFeScience/akoflow-examples.git
cd akoflow-examples/rendering/blender-render-farm
./prepare.sh && ./run.sh

Preparation downloads the Go YAML module. Results are in outputs/manifest.json, outputs/dag-validation.json, and outputs/stage-<activity>.json. Independent branches run concurrently as soon as their own dependencies and a local execution slot are available.

Inspect the same DAG in Desktop

Start the local AkôFlow daemon with Docker available and configure AKOFLOW_API_TOKEN in your shell. From this example directory:

go run ../../tools/daemon-local -root ../.. -example rendering/blender-render-farm

The command builds the declared image, validates Docker connectivity, registers local-only infrastructure, and executes the workflow through the daemon. Current verified screenshots are in screenshots/current/; their manifest identifies the exact run and image. The full daemon projection is in evidence/daemon-run.json.

Public Hub version and measured execution

Open this workflow and its results · Documentation

Import into AkôFlow Desktop

Create workflow → Import from Hub → paste this immutable URI:

akoflow://hub/publications/f0608ece-22cb-45d9-ba33-aaf5d1c42231/versions/1

The URI imports the workflow definition. Build or pull the public image and register the companion environment.yaml, scope.yaml, and topology.yaml from this source bundle before planning a local execution. No hosted account, GPU or cloud capacity is required for this CPU profile.

Image: ghcr.io/uffescience/akoflow-examples/blender-render-farm@sha256:065a3b2b7f449b31ee4b6403c3580720cf4c1e87ede9c04c7ca3510ab570aaae.

Actual homeserver results

Run hubv1-blender-render-farm-local-37884b15c5-run-20261115t055538.830501945 completed 5/5 activities in 18.980467796325684 seconds. These are measured Docker-backed computations, not simulated timing. The captured manual plan uses placeholder predicted timings; those predictions are not benchmark measurements. Use the observed execution metrics for performance analysis. Cost is the configured local compute cost and excludes electricity and hardware.

Download the native experiment capture. The Hub Results tab includes the same plan, attempts, metrics and logs.

Inputs and outputs

Input fixtures and their generation code are in this bundle's data/ and scripts/ directories; inspect them together with the workflow definition and bundle configuration for profile assumptions. Fixtures are generated by the included code unless a bundle identifies an upstream dataset. No repository-wide LICENSE file is currently present: inspect the bundle and upstream terms before redistributing source or data; publication here does not grant additional rights. Outputs expected from this workflow:

• render-plan.json
• scene.blend
• animation.mp4
• render-report.json

Download the actual validated output files.

Illustrated walkthrough

The following reference screenshots come from the documentation walkthrough. The current measured run is recorded separately above.

compose

render-even

render-odd

setup

verify

workflow