Distributed Content Rendering System

You're paying EUR1,920/month for cloud GPUs. Your office machines sit idle every night.

The thing nobody tells you

You already own a render farm. You just don't know it. Every office workstation, every laptop sitting idle overnight, every machine parked on a screensaver -- that's unused GPU and CPU time you're already paying for. I've deployed these as design-rigorous infrastructure across production studios -- machines that have been rendering brand-correct content autonomously for years.

Stop waiting for renders. Start using what you already have.

High-volume content production creates a rendering bottleneck. Blender animations, FFmpeg video compositing, ImageMagick batch processing, headless After Effects — all of it takes compute time that your single dedicated render machine runs out of fast.

The common solution is cloud rendering. The common problem is the bill.

8 render nodes on AWS/GCP at €3/hour each, running 4 hours a night, 20 days a month: ~€1,920/month.

8 office workstations running overnight on Renderbot: €0/month after one-time setup.

Renderbot distributes your render load across any available machines on your network — workstations, laptops, spare hardware — turning idle compute into a private render farm that's already paid for.

Cloud rendering cost:
- 8 nodes × €3/h × 4h/night × 20 days
- = €1,920/month
- Plus egress fees
- Plus storage fees
- Plus the time spent managing cloud infrastructure

Renderbot on idle machines:
- Hardware you already own and pay for
- = €0/month in additional compute cost
- One-time setup: a few hours
- Payback period on setup cost: first month
- No cloud account. No surprise invoices.

The architecture in plain English

Think of it as Uber for render jobs. Jobs wait in a queue. Idle machines pick them up, render them, and return the output. The moment a machine becomes available — end-of-day, overnight, weekend — it picks up the next job automatically. You submit work and results appear. That's it.

How it works

Central node: REST API, task queue, result storage, web dashboard — runs on any always-on machine
Render nodes: lightweight Python agent, polls the queue, processes tasks, returns output — install on anything
Task types: Blender renders, FFmpeg video jobs, ImageMagick batch ops, custom scripts — if it runs headless, it queues
Node discovery: nodes register on startup, heartbeat confirms availability, dropped nodes are detected automatically
Fault tolerance: failed tasks re-queue immediately, crashed nodes don't lose work
Job priorities: urgent jobs jump the queue — campaign deadline vs overnight batch are handled differently
Result delivery: completed outputs immediately available via dashboard, API, or pushed to your delivery pipeline

What can render on the nodes

Blender (headless EEVEE and Cycles) — still frames and animation sequences
After Effects (aerender headless) — motion graphics and video template renders
FFmpeg — video compositing, format conversion, overlay processing at scale
ImageMagick / Pillow — high-volume image generation, transformation, and batch manipulation
Any custom script that produces file output — the system is renderer-agnostic. If it runs via command line, Renderbot can queue it.

Central node provides:
- Task submission API (POST a job, get a result URL)
- Queue management and prioritization
- Dependency rules (job B waits for job A)
- Result storage, archiving, and delivery
- Dashboard with live queue status and logs

Each render node provides:
- Automatic task pickup (no manual intervention)
- Local render execution in isolated environment
- Real-time progress reporting
- Output upload on completion
- Self-healing on crash or restart — no babysitting required

Measured performance

A production Blender frame that takes 4 minutes on one machine takes 30 seconds distributed across 8 idle workstations. Setup across 8 machines: approximately 2 hours. Payback on cloud GPU costs: first month of operation.

Who needs this

Motion studios and animation teams with regular Blender or AE render loads
Production agencies running high-volume video content — reels, ads, social video
Teams using Stamper or SMM Factory at scale — Renderbot is the rendering backbone for both
Gambling and iGaming studios producing hundreds of video creatives per week -- Renderbot turns overnight idle time into production capacity.
Anyone who has sat watching a progress bar when they should be doing something else

Integration with Stamper and SMM Factory

Renderbot is built to be the rendering backbone for Stamper and SMM Factory pipelines.

Stamper submits batch composition jobs to the Renderbot queue — hundreds of variants rendered in parallel
SMM Factory triggers render jobs when new content is due — the whole chain runs without manual intervention
Results flow back automatically into the delivery pipeline
The complete chain — content source → template → render → brand layer → delivery — runs unattended

Show me your render setup. I'll show you the savings.

EUR120/h. Works with your existing hardware. No cloud required. Design-rigorous infrastructure. You own the code.

madeby.mex.com