Studio - Build AI workflows visually, publish as apps anyone can run
by•
A visual, node-based canvas for building AI workflows — no code required. Wire together image, video, audio, and text nodes into one pipeline: keep a character consistent across scenes, batch-generate on-brand assets, build a landing page and export it to PDF, or mockup your art on real products.
Replies
Vector Ink
Hey Product Hunt 👋
I'm Jonathan O'Farrow, solo founder of Vector Ink. A while back I launched Vector Ink here as a vector design canvas, since then the thing our users kept building inside it surprised me: they weren't just editing images, they were chaining AI steps together - vectorize this, remove the background, upscale it, generate variants - by hand, one tool at a time.
So I built Studio: a visual, node-based canvas for wiring those steps into a real workflow. Drag in an image node, connect it to vectorize, upscale, remove-bg, whatever you need, run the whole chain in one click. And when you've built something useful, you can publish it as an app other people can run directly, they pay in credits, you never get charged for their usage.
Would genuinely love feedback from this community, especially if you've used tools like Weavy/Magnific/ComfyUI and have opinions on visual workflow builders. Happy to answer anything in the comments today!
Dragged a few image nodes and a video node together and it actually just worked, kind of surprised me honestly.
Vector Ink
@hayrettinkx3ve Awesome to hear! there are a ton of things you can do with this platform. Let me know if you have any questions.
love how clean the node canvas feels, like everything's actually readable instead of that spaghetti mess you get with most workflow tools
Would love a way to save custom node setups as reusable templates I can share with my team, would save a ton of time on similar client projects instead of rebuilding the same pipelines from scratch.
Vector Ink
@ccumagil14794 You can totally do that. You can save them as public or unlisted templates and share the link so other members can fork the template. You can also share them as public or unlisted apps so the end user doesn't have to see the canvas. Checkout the tutorial on this topic ->
Love the node-based approach, super intuitive. One thing that would really help though is a version history feature for the canvas itself so I can roll back if I break a pipeline or want to branch off an earlier setup.
Vector Ink
@eray3okc Appreciate the suggestion. This is a great idea. It will save so many users so much pain. I will add it to the top of the list.