Every DCC. One pipeline. One price.
A node-based workflow editor that runs in your browser. Executes Maya, Blender, Houdini, Nuke, and Unreal on your machine.
Pipelines are stitched together with brittle scripts, tribal knowledge, and that one TD who's been there since the beginning. We've spent twenty years getting comfortable with this.
The script depends on Python 3.9, a specific PySide2 build, MAYA_SCRIPT_PATH pointing at the right NAS, and a custom module sitting in one person's home folder. The next workstation has none of those. ImportError. Missing plugins. A "good luck" in Slack.
The browser-based dashboards are great for tracking. They have no idea what Maya is doing on the artist's machine downstairs.
The naming convention lives on Confluence. The Confluence lives in 2019. The artist learns the convention by getting it wrong.
Every TD on the team has written the same Maya-to-Houdini exporter. None of them survived the last project. The next one is already on the backlog.
One hybrid architecture. The graph lives in the cloud. The work happens on your hardware. The backend never sees your assets, your scenes, or your custom code.
Drag nodes, wire them, hit run. Any OS, no install, anywhere you've got a tab open.
The cloud orchestrates the graph but stays stateless. It never sees your assets or your code.
A small native runtime on your workstation. It finds your DCCs and runs them where they already live.
As your workflow runs, every connected DCC viewport populates natively: concurrent, on your hardware, with the actual scene. Not a preview. Not a render. The real thing, in every app at once.
Plumber's roots are in film and animation. The architecture isn't. Any application with a scripting API can become a Plumber runtime, and we're already moving into adjacent crafts. Vectorworks is next. Yours could be after.
Production-ready integrations. Native APIs, persistent sessions, full node coverage.
Plumber pushes outward: architecture, design, motion, audio. The agent doesn't care whether it's talking to a film tool or a building tool. Same protocol. Same speed.
Need a DCC we don't support yet?
Commission us to build it.
Or grab the same SDK we use ourselves and ship it solo.
No internal/external split. The integrations we ship are written with the SDK you'd download. Same APIs. Same docs. Same agent. Once shipped, Plumber Care can keep it current.
Open the SDK →Operations that took seconds now take milliseconds. Measured against the per-operation cold-launch baseline of a traditional pipeline script.
From ~16 seconds to ~100 milliseconds per operation. Validated end-to-end on a real multi-character batch export.
Persistent session means the procedural graph stays warm. Iterate on a setup without waiting for the engine.
Blender starts fast already. Plumber still makes it disappear from the loop. The scene stays loaded between steps.
// Measured against per-operation cold-launch baseline. Your mileage will vary with scene complexity.
One hybrid system. The graph is in your browser. The work happens on your hardware. There is no product that does both the way we do.
The workflow runs and your real Maya, Blender, or Houdini viewport populates in front of you. Not a preview. The actual scene.
Windows, Linux, macOS. Apple Silicon native. Build pipelines from a tablet if you want. The execution machine doesn't have to be the same machine you authored on.
Call execute_blender(), execute_maya(), or execute_houdini() from your own Python. Hot-reload on save. Your code stays on your machine.
The backend orchestrates but never sees your assets, your scenes, or your custom code. Zero IP risk by architecture, not by policy.
Smooth bezier connections, color-coded ports by data type, minimap, global search, grouping, and collapsible subgraphs.
Write Python nodes that execute locally with hot-reload on save. Bridge functions for every supported DCC.
15 ShotGrid nodes ready to go. Render → publish → update status → notify, all in one graph. More trackers on the roadmap.
Conditional and loop nodes for branching logic. Build real automation, not just linear scripts.
Windows, Linux, macOS. Apple Silicon native. The editor is a browser tab. The agent is a background service.
Founding-member pricing runs for the next six months. Whatever tier you join at, that rate is locked in for as long as you stay.
Your custom nodes need to survive every Plumber release. Care handles compatibility updates, priority fixes, and a recurring pipeline review, so your internal TD stays on the shots instead of patching infrastructure.
// Available to Team and Studio customers · Beyond 20 nodes? Custom coverage on request
Thirty days free. One agent. Every DCC. No card. If it doesn't earn its place in your studio in a week, walk away.