Pre-launch: building now

Every render, on every computer, in one place.

Werkhaus is a render-monitoring and production platform for Blender. It turns every render into data you can learn from: where the time goes, which computer is best for the job, and which settings would get the same look faster. For schools, it turns a room of lab computers into one shared queue and gives teachers a real view of how their class is learning.

Join the beta See what's built Werkhaus for schools
The Grain, the model behind Tune, learns only from render measurements that adults choose to share. Never images, files or names.
Monitor

Watch every render, on every computer, live

Each computer gets a live card: what it is rendering, how far along it is, and how hard the hardware is working. Open one to see layer-by-layer progress and the timing of every frame.

  • Layer and frame progress, with an honest time left
  • GPU, VRAM, CPU and RAM, coloured by how close they are to the limit
  • Per-frame data that marks the slowest frames
Sam-DesktopRTX 4070 · 12 GB
Personal
Started 6 min ago
forest_path.blendAnimation
1920×1080 · 256 samples · Cycles
Frame 31 of 12026%
About 18 min left
GPU94%
VRAM61%
CPU28%
RAM44%
RENDERING
LAB-07RTX 4060 · 8 GB
Period 2
For Kenji Morita · 3D Animation
street_corner.blendStill
1280×720 · 128 samples · Cycles
Layer 2 of 349%
About 3 min left
GPU88%
VRAM72%
CPU31%
RAM38%
RENDERING
Still render · street_corner3 min left
ForegroundDone
StreetRendering
BackgroundWaiting
Layer 2 of 348.7%
Frame data · 48 framesGPUVRAMCPURAMTIME
Average 14.3 s a frameSlowest frame 32, 33 s
What this means
  • GPU at 94% is good news: the graphics card is doing the heavy lifting.
  • VRAM at 61% means the scene fits in graphics memory with room to spare. Past about 90%, renders can fail.
  • Frame 32 took more than twice the average. Frames with lots of glass or reflections in view usually do.
Tap any term:GPUVRAMSamplesDenoise

Modules from our approved designs, shown with made-up names and sample data. The live app may differ in detail.

Inside Blender
The Werkhaus add-on
Reports render progress, frame times, render settings and hardware while you work. It never reads your scene contents.
On your computers
The desktop app
Windows, macOS and Linux. Links each computer to your account, runs queued renders and moves files between machines.
Anywhere
werkhaus.app
Watch renders live from any browser, look back through your history, and manage your computers, team or class.

What Werkhaus does

Built for people who render in Blender every day, from one laptop to a studio's worth of machines.

Monitor

Live progress for every render on every computer, frame by frame, with per-frame timing so a slow frame stands out the moment it happens.

Dispatch

Queue renders and send them to any of your computers or your team’s. Werkhaus moves the files, starts Blender and brings the frames back.

Tune

Suggested settings that render faster at the same look, powered by the Grain. It learns only from adults who choose to share their render measurements.

Renders and Insights

A searchable history of every render with the settings, hardware and timing behind it, plus trends across your projects.

Files

Find project files across your computers, package a scene with everything it needs, and send it to the machine that will render it.

Teams and classes

Shared machines, one queue and clear roles for studios, and class teams for schools with groups, assignments and lab computers.

Transfer64%
forest_path.blend1.2 GB · Sam-Laptop to Studio-PC · about 40 s leftTextures and the HDRI are packed with it, so nothing comes back pink.
forest_path.blendNormal
Waiting for its fileStudio-PC
Frames 1–120 · 256 samples · 1920×1080 · starts when the transfer lands
desk_lamp_study.blendHigh
Scheduled tonight at 23:00Sam-Desktop
Still · 512 samples · 2560×1440 · runs while you sleep
robot_turntable_v3.blendNormalPeriod 2
3rd in line, about 9 minClass queue · LAB-12
Frames 1–120 · checked against Unit 3's settings before it starts
Dispatch

Send renders to whichever computer is free

Queue a render and pick a computer, or let Werkhaus choose. It moves the files, starts Blender and brings the frames back when they are done.

  • Each job shows where it will run, its priority and its settings
  • Transfers show every file moving between your computers
  • Scheduled jobs start on their own, overnight if you like
Files

Your files, across every computer you use

See each computer's files from wherever you are, pin the projects you are working on, and know which computer has what before you send anything.

  • Every computer with its files, folders and what is moving
  • Sharing switches, set on each computer by you
  • Pinned files show where they live and what is on the way
Sam-Desktop1,284 files · 46 projects
OnlineSharing
Sam-Laptop312 files · 1 moving
Sending 1 fileSharing
Studio-PC2,046 files · 71 projects
RenderingSharing
Old-LaptopNot shared
Offline · 3 daysSharing
Pinned
forest_path.blendSam-Laptop · edited 20 min ago
Moving to Studio-PC
desk_lamp_study.blendSam-Desktop · 4 versions
On 2 computers
studio_small_03.hdrSam-Desktop · 24 MB
Used by 3 scenes

Modules from our approved designs, shown with made-up names and sample data. The live app may differ in detail.

Render intelligence

Every render becomes something you can learn from

Most artists never see why a render was slow. Werkhaus measures each one as it happens and turns the numbers into plain answers, so every render teaches you something about your scene, your settings and your hardware. The insight is the product. Your data stays yours: we never sell it.

What one render recordsSample data
File
forest_path.blend
Computer
Studio-PC
GPU
RTX 4070, 12 GB
Engine
Cycles, GPU, OptiX
Resolution
1920 x 1080, 100%
Samples
1024, denoise on
Frames
1 to 240
Time per frame
41.8 s average
Slowest frame
#112, 71.0 s
Time by view layer
Volumetrics 58%
Peak VRAM
9.4 of 12 GB
Scene size
412 objects, 2.1 M faces

Measured by the add-on while Blender renders. It never reads your scene's contents, images or files.

What it tells you · example insights
Monitor

Volumetrics take 58% of each frame

Raising the volume step rate from 1.0 to 2.0 would save about 14 s a frame.

Monitor

Frame 112 took 71 s, 70% above average

The camera passes through fog there. Check that shot before the final render.

Dispatch

Studio-PC does this scene 2.4 times faster

Send long renders there and keep your laptop free for work.

Dispatch

Sam-Desktop sat idle for 6 hours this week

Queued jobs can use it overnight instead of waiting.

Files

3 textures are missing on Sam-Desktop

Werkhaus packs them with the scene before sending, so the render does not come back pink.

Insights

Your average frame time fell 22% this month

Most of the gain came from denoising and lower sample counts.

A loop that makes you faster

  1. 1 · Render Render as you always do, on any of your computers.
  2. 2 · Measure Werkhaus records time, settings and hardware for every frame.
  3. 3 · Understand Insights point to what made it slow and what would help.
  4. 4 · Improve Try a Tune suggestion, see the result next render, and keep what works.
The Grain

Learn from every render, not just your own

The Grain is built from render measurements that adult artists choose to share. It turns thousands of renders into benchmarks anyone can use: how your hardware compares, what a scene like yours should take, and which changes really pay off. Nobody's images, files or names are ever part of it.

Grain insights

See what the Grain has learned

The Grain shows its work: how confident it is, how many runs taught it, and whether its suggestions really made your renders faster.

  • Confidence that rises with every measured Tune run
  • Improvement over time, run by run
  • Before and after: below the line is faster
78%
Confidence
Modelv0.14
Examples18,420
Tune runs146
Last trained6 min ago
Confidence is how sure the Grain is about a suggestion. It rises with every Tune run that gets measured.
Improvement over timeHow much faster each Tune run made the render
Average 11% faster3 runs were a little slower
Before and afterRender time before Tune against after. Below the line is faster.
0 s1000 s before
Your computers against the community
Studio-PCRTX 4080 · 16 GBFaster than identical cards
91th percentile of Blender GPUs
Sam-DesktopRTX 4070 · 12 GB12% slower than identical cards
64th percentile of Blender GPUs
Sam-LaptopApple M2 ProAs expected for this chip
22th percentile of Blender GPUs
Sam-DesktopThis computer · add-on and desktop app connected
A−78 of 100
What this means
  • It renders 12% slower than other RTX 4070s on Werkhaus.
  • The usual causes are an old graphics driver or a power plan set to save energy. Both take a minute to fix.
Tap any term:TierPercentileBenchmark
Machines

Know what your hardware can really do

Every computer is benchmarked and placed on the Blender Open Data curve, then compared with identical hardware on Werkhaus, so you can tell when a machine is underperforming.

  • A tier and a score for every computer
  • Its percentile among all Blender GPUs
  • A flag when it runs slower than identical hardware

Modules from our approved designs, shown with made-up names and sample data. The live app may differ in detail.

  • Machine tiers Every computer gets a benchmark score and a tier, so you know what it can handle and where an upgrade would actually help.
  • Fleet vs the community Each GPU placed on the Blender Open Data curve, and how it performs against identical hardware on Werkhaus.
  • Tune, measured Every suggestion is measured: render time before and after, so you see what really saved time on your own scenes.
  • Your contribution If you choose to share, see the runs you contributed and how much they improved the suggestions everyone gets.
For everyone who renders

Studio-grade render data, without a studio

Big studios have pipeline engineers who track every frame. Blender is free, and we think the tools to understand your renders should be within reach too: for a student on a school laptop, an artist with one GPU, or a lab of thirty computers.

  • Free to start Live monitoring and render history are free on one computer.
  • Any hardware From a school laptop to a render farm, on Windows, macOS or Linux.
  • Plain language Insights say what happened and what to try, with no statistics needed.
  • Built for classrooms Schools get the same data for every student, with the privacy students need.
  • Yours to keep Download everything Werkhaus has recorded about your renders at any time.
  • Shared only by choice Adults decide whether their measurements help the Grain. Students in a class never contribute.

The data you get to see

Time per frame Slowest frames Time by view layer Samples and denoising Light path settings Resolution and frame range Peak VRAM GPU, CPU and memory use Scene size Hardware benchmark and tier Computer comparisons Community percentiles Tune savings Render history by project
Learn

Every render explains itself

Blender has hundreds of settings and very little feedback. After every render, Werkhaus explains in plain words where the time went, what each number means, and one thing to try next, so beginners learn the tools by using them.

  • A render report in plain words after every render
  • Tap any term, like samples or VRAM, for what it means and why it matters
  • A skills view that follows what you have practiced, with no points and no rankings
Render reportFinished
forest_path.blend · 14 min 20 s

Most of the time went into six frames where the camera looks through the glass greenhouse. The noise was already clean at 128 samples, so the extra 128 samples mostly cost time.

Where the time went
Path tracing 78%Denoise 9%Loading 8%Saving frames 5%
Try next128 samples with denoiseAbout 45% faster with the same look. The Grain is 82% sure, based on 3,100 similar scenes.
SamplesGlossary
How many light paths Blender traces for each pixel. More samples means less noise and a longer render. Denoise cleans up what is left.
What you have practiced
Samples and noiseConfident
You used denoise on 9 renders and cut samples on 6.
LightingPracticing
3 scenes lit with an HDRI, 1 with area lights.
Texture memoryNew
Tip ready: 4K textures on an 8 GB card can run out of memory.
Animation outputPracticing
2 image sequences rendered, 1 turned into a video.
No points and no rankings. It follows what you have actually done in your renders.

Modules from our approved designs, shown with made-up names and sample data. The live app may differ in detail.

Launching with schools first

A render lab that runs itself

3D programs teach on Blender, and students render on shared lab computers. Instructors rarely get a clear view of that work. Werkhaus gives each class one queue across the room, a view of every student's progress, and assignments that check themselves against the project's requirements.

We are talking with university digital media and animation programs about using Werkhaus in their courses and student-led clubs.

Werkhaus for schools
One queue for the lab
Every lab computer joins the class. Students send renders to whichever machine is free.
Sign in at any seat
Students sign in on shared lab computers with their own accounts and are signed out when they walk away.
Assignments that check themselves
Set resolution, frame range, samples and file naming once. Werkhaus checks each hand-in against them.
Progress at a glance
See who has rendered, who is stuck and which machines are busy, without walking the room.
Projector view
A class-wide view for the front of the room that shows totals only, never one student’s work or name.
Groups and clubs
Separate classes, project groups and student-led clubs inside one school account.

Built for students from the start

  • Werkhaus is for people 13 and older, and every account answers an age question first.
  • Students 13 to 17 get protected settings by default: private profiles, no marketing email, no community posting unless they turn it on.
  • Class members never contribute to the Grain.
  • No advertising, no ad trackers, and we never sell personal data.
  • People can download their data and delete their account themselves.
  • Schools sign a data agreement before any student joins a class.
Beta testers wanted

Help us build Werkhaus

We are inviting testers in small groups before launch. Testers get Werkhaus free during the beta, a direct line to the people building it, and a say in what we build next.

  1. 01 Join the list. Tell us how you render, so we can invite the right mix of people.
  2. 02 Confirm your email. One click, so nobody is added without asking.
  3. 03 Get your invite. A download link and a beta account, in small groups as we open up.

Beta testers must be 18 or older for now. Students can take part through their school's pilot.

Join the beta list

I would test Werkhaus as
How many computers do you render on?
Operating systems

We keep your name, email and answers only to run the beta and invite you in. We never sell them. Leave the list any time with the link in any beta email, and we delete your details within 30 days. See our privacy policy.

Where we are

Werkhaus is built by a small independent studio. Here is what is finished, what we are building now, and what has to happen before launch. Updated October 2026.

  1. Built Monitor, Renders and Insights Live render monitoring with per-frame timing, render history and insights.
  2. Built Dispatch and file transfer Queue renders and send them, with their files, to any of your computers.
  3. Built Desktop app Windows and macOS (signed by Apple), with Linux support in the codebase.
  4. Built Teams and seats Studio teams with shared machines, roles and seat management.
  5. Built Privacy controls Age screening, protected defaults for teens, data export and account deletion.
  6. Built Support and safety In-app help with error codes, and a reporting and moderation system for the community.
  7. Building Community A forum-style feed for sharing renders and getting feedback, opening to US members first.
  8. Building Classroom tools Class teams, assignments with requirement checks, the projector view and progress tracking.
  9. Building Files and libraries Project files, assets and add-ons organised across every computer you use.
  10. Before launch School data agreement and policies Our privacy policy, terms and school data agreement, reviewed by counsel.
  11. Launch Launch with schools, then public First with university programs and their clubs, then open sign-up for everyone.

Planned plans

Prices in US dollars per month, planned for launch and subject to change. The first 100 founding members get 50 percent off for 12 months.

Free

$0
Try Werkhaus on one computer.
  • Live monitoring
  • Render history
  • 1 computer

Basic

$8
For solo artists.
  • Everything in Free
  • Insights and assets
  • 2 computers

Pro

$18
For artists with several machines.
  • Everything in Basic
  • Dispatch and Tune
  • Files across computers
  • 5 computers

Studio

$39
For studios, schools and clubs.
  • Everything in Pro
  • Team and class workspaces
  • 10 seats, more available
  • Shared lab machines

About

Werkhaus is made by Hoek Creative & Co., LLC, an independent studio in California founded by Jordan Hoekwater. We are self-funded and building in the open. We would like to hear from schools, clubs and 3D artists who want to try Werkhaus early.

General and schools hello@werkhaus.app