

RenderFlow Updates - April 2026
RenderFlow


We’ve got a packed release to share this month. Let’s get into it.
Cloud Rendering
The headline addition is Cloud Rendering for 3ds Max and Scene Manager, currently in beta. . This is RenderFlow’s first step toward making cloud burst capacity a native part of the pipeline rather than a separate workflow. When your local farm is maxed out, you can now spin up cloud resources directly from RenderFlow without switching tools or breaking your submission flow.
If you’d like to try it out, you can sign up for the beta here.


Broader DCC and Renderer Support
RenderFlow now supports 3ds Max 2027, Blender 5.0 and 5.1, FStorm 2, and Octane 2026, keeping things current with the latest releases across the board.

Notifications and Integrations
A new Integrations settings page brings Slack and Teams notifications (currently in beta) alongside desktop notifications. Studios can now choose how they want to stay on top of farm activity without constantly checking the RenderFlow UI.

Developer and Automation Tools
Plenty of updates for studios that integrate RenderFlow into their pipeline. The REST API now requires an API key (configurable in Settings), and both the API and CLI have been improved.
We’ve also published new TypeScript/JavaScript and Python SDKs, and there’s a new MCP server that lets you query and control your farm directly from Claude Code.

Database Upgrade
RenderFlow now runs on MongoDB 8. The migration is handled automatically and transparently during update, so there’s nothing you need to do on your end.
Brand New Documentation
We rebuilt the documentation site from the ground up for both RenderFlow and Scene Manager. Everything now lives at docs.pulze.io with a cleaner structure, better search, and more up-to-date content.

Important Bug Fixes
We tackled a solid list of issues across the board. The last frame of batch renders now saves correctly, and jobs no longer get stuck after database connection drops or server restarts. The render stats display is more stable, and we fixed progress reporting for 3ds Max time-limited renders. We also resolved asset warning false positives during submission and several issues with pool selection, Scene Manager presets, and license error messaging.
Quality-of-Life Improvements
The new “Total Render Time” field sums up completed task durations, and the asset checker for 3ds Max is smarter when files are open. OCIO sanity checks now cover 3ds Max 2024 and 2025, system drive stats and network drive listings are visible, and admins get new system-level default job cleanup settings.


Thanks to everyone who reported bugs, shared feedback, and helped us test these releases. These updates are better because of you.
Got questions or feedback? Reach us on Discord or at support@pulze.io.


