@tools_loop · X

@tentaco_cc · X

Hey! I built 🐙 It’s a privacy-first web space packed with over 450+ free micro-tools for tech, design, marketing, and PDFs. The best part? Everything runs 100% locally in your browser. No registration, no ads. Let's connect! 🛠️

@klorityx · X

One workspace for project management, documentation, test management & CRM. Enterprise features without enterprise pricing.

@Arafat3599651 · X

Just launched 🧮 125+ free calculators — mortgage, BMI, debt payoff, compound interest, calories & more. No signup. No ads. Everything runs in your browser instantly. #buildinpublic #webdev #react

ai world generator — 用文本和照片生成自然风光视频的 AI 工具网站

@iPranayJoshi · X

Would be honoured to come join! Built talk about vibe coding at

builderwrench · HN

Show HN: Free tool that shows what AI assistants see when they crawl your site

@Fluxify_pro · X

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

@mr_wickedhacks · X

Write the doc once → get a notebook, slide deck, canvas, or resume from the same source. No rewriting for every format.

@Number1AIFanboy · X

I got to go to bed. More coding tomorrow. I just had a realization that I'm building cool shit, using @grok in an app that I built with Codex and refined with Grok. And now Grok just works on himself. LFG🚀 Drop me a note here: Get the app here (use LAUNCH50):

@buildrunkitUS · X

BuildRunKit: A complete system for founders, with (CRM/Invoices/Projects) BuildRunKit 7-part Startup foundations book series. Book 1 is live! The Startup Self Check Frenzied Founder Podcast.

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