Zuflow is a web app that helps you build 3D assemblies with visual logic. Map your parts on a node graph and let the engine do the math. 🕸️ Visual Constraints: Wire parts on a canvas. See your logic. ⚡ Auto-Solver: Define relationships and watch parts snap together. 🚀 Browser-Native: Fast 3D rendering with zero downloads. 📐 Instant Drawings: Export dimensioned PDFs and DXFs
Hi Product Hunt! 👋 I’m Matas, the solo dev behind Zuflow.
This started when a mechanical engineer friend was venting to me about how frustrating CAD assembly tools are. He explained that most of the time, you just want to line up simple things like holes or flat surfaces, but instead, you get stuck fighting with opaque mates and hidden constraints.
As a software developer, it seemed crazy that such a common process was so clunky. I realized a visual, node-based system would make way more sense.
So, I built Zuflow. It’s a web-based constraint solver where you:
Drop in loose STEP files.
Wire up the relationships on a visual canvas.
Watch the engine automatically snap the parts into place.
Export dimensioned engineering drawings and PDFs in a single click.
I’d love for you to try it out with some parts and roast the workflow. Does a visual node approach actually make things faster for your daily work?
Let me know what you think in the comments! I’ll be here all day answering questions and fixing bugs. 🛠️
Okay this one hits close to home — spent years in SolidWorks and Fusion during my robotics/mechatronics days, and the moment assemblies get complex, mate relationships turn into an unreadable mess in the FeatureTree. A node graph is such an obvious fix in hindsight that it's wild nobody's shipped it well before.
Question: how does Zuflow handle over-constrained assemblies? That's where most parametric solvers either silently fail or throw cryptic errors. Does the node graph give you visual feedback on which constraint is the offender?
Browser-native + DXF export is the combo that makes this actually usable in the real world. Rooting for you 🫡
@sai_tharun_kakirala Thanks for the feedback! To answer your question, Zuflow avoids this entirely by design. Because the system relies on snapping predefined 'Ports' together via a node graph, a single connection fully defines how the two parts attach and rotate. It’s basically like snapping Lego bricks together—you just connect Port A to Port B. Because of this architecture, the math doesn't conflict, and it's virtually impossible to over-constrain the assembly.
Zuflow
Hello Aria
Okay this one hits close to home — spent years in SolidWorks and Fusion during my robotics/mechatronics days, and the moment assemblies get complex, mate relationships turn into an unreadable mess in the FeatureTree. A node graph is such an obvious fix in hindsight that it's wild nobody's shipped it well before.
Question: how does Zuflow handle over-constrained assemblies? That's where most parametric solvers either silently fail or throw cryptic errors. Does the node graph give you visual feedback on which constraint is the offender?
Browser-native + DXF export is the combo that makes this actually usable in the real world. Rooting for you 🫡
Zuflow
@sai_tharun_kakirala Thanks for the feedback! To answer your question, Zuflow avoids this entirely by design. Because the system relies on snapping predefined 'Ports' together via a node graph, a single connection fully defines how the two parts attach and rotate. It’s basically like snapping Lego bricks together—you just connect Port A to Port B. Because of this architecture, the math doesn't conflict, and it's virtually impossible to over-constrain the assembly.