I built it because I saw what workflow tools could be, and I'd dreamed for years that someone else would build them that way. Nobody did, so here we are. Ultimate impact for minimal effort, the pinnacle of my life's laziness.
Flowzart bends when you need it to, opens up when you want to look inside, and treats its plumbing as a feature you can see and fix. Eventually "find that tool" becomes "build that tool."
Typed nodes, clean composition: the engineering of getting it right is its own reward. The vision got Flowzart started; the craft is what keeps it going.
Flowzart should be the place where you can automate something, and never get stuck with a broken automation. If a node hits an edge case or has a bug, you should be able to crack it open, tinker with it, and ship a working version yourself. And then, this is the magic part: you should be able to push that fix upstream as a pull request to the registry the node came from. Once it's reviewed and merged, everyone using that node gets the fix.
That's what the Matrioshka system and the Registries system are built for, together: an App Store of automation, where the store is the community and every node anyone publishes is one PR away from getting better.
Flowzart is for anyone who builds workflows: solo builders, growing teams, and larger companies.
Flowzart is one person and a lot of nodes. Pre-revenue, in active development. Most days I'm head-down on shipping the next slice.
Eventually, Flowzart's codebase could go source-available: free for individuals and small companies to use, study, and modify, with a commercial license for larger companies. Not promised. That's the direction.
Built something with Flowzart? Tell us about it, no matter how big or small. Email [email protected].
Or use our contact form