@TimoBuilds_ · X

building up to leading SaaS for solo-founders to close the feedback-loop to their customers what are you building rn?

@dipanshurdev

@himanshu_b20 · X

@BuiltByAmar · X

@Fluxify_pro · X

everyone who sign up today, get free pro plan, without credit card

@vasanthadabala · X

Not really a startup. It's just something I built for myself a simple note taking app with a planner, progress tracker, and mind map I'm going to share it publicly @NodesMap check it

allybahaei · HN

Bring all your sources into a visual space, ask questions with full context, branch LLM conversations, and go deep on YouTube videos / research papers to build your knowledge canvas.

@brryg_ · X

sure man, working on a social and visual news hub called heuron - lmk what you think!

@PeakVisibilitys · X

🚀 AI-powered SEO audits and AI search optimization. Would love some feedback!

@UmarIqbal000 · X

tahazsh · HN

Hi! I’m Taha. In many agentic products that support workflows (including one I worked on), I noticed they either don’t support node-based editors, or use React Flow and go through the difficult work of integrating it into their product to run it and work with their existing logic. So I thought about creating a tool that could help with this by closing the gap between the editor and the runtime. That’s why I created Wayflow. The basic architecture is simple: you just need to create a graph (which is a JSON object) that the runtime knows how to run. The runtime doesn’t care where that graph is coming from, it just needs the right schema. And with the help of the editor, you can create the graph, and then export it or directly save it on your backend in your database. And then when you want to execute it, you just hand it to the runtime. The runtime can either stream the execution (which is useful for the editor), or give you the final result. How you execute the graph is up to you: t

@JNRVInnovations · X