@TimoBuilds_ · X

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

@gouravbht · X

been applying to jobs lately and realised most of the time goes into filling forms, rewriting cover letters and tweaking resumes. not the actual prep. just the repetitive part. built something to handle all of that.

@YarrowCloud · X

Vibe-coded app with a hardcoded Stripe key and no RLS. Yarrow rotates it, logs it, files the audit — founder still tweeting 'just shipped.'

@Tino_Ferreira23 · X

@saifcodes_exe · X

@MilletGilmore · X

@MalkkiLea · X

Hi, I'm building

sirily11 · HN

Application Signal – AI That Evaluates Your YC Startup Idea

brandonpayton · HN

Kandelo – a POSIX-compatible multi-process WASM kernel for the browser

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

@Aryandwi007 · X

Hey check this out

@adityabastawad · X

Every recruiter deserves a twin that hires the way they do.