Hi HN! We’re Alessia and Elia, the founders of VibeFlow (https://vibeflow.ai). VibeFlow lets semi-technical people (i.e. people with some technical skill but who are not professional programmers) build full-stack web apps from natural language prompts, while making the underlying business logic clear and editable as a visual workflow. Demo video: https://www.youtube.com/watch?v=-CwWd3-b1JI.

The problem we’re trying to solve: today, people who want to build apps without coding often have to stitch together multiple tools, e.g. using Lovable for the frontend, n8n for workflows, and Supabase for the database. That creates data silos and leaves builders with fragile apps that break in production, don’t scale, and aren’t safe. We saw YouTube tutorials teaching people how to duct-tape these together just to get a functional app running. As engineers building no-code tools, we realized that people wanted the power of AI-generated UIs but also the ability to see and control their backend workflows and data.

Our solution is to generate the whole app at once, and represent it as a visual workflow. Users describe what they want in English (“I need a chat widget with an AI agent”) and VibeFlow generates both the interface and the logic. That logic shows up as a workflow graph they can edit visually or by giving new instructions.

We use Convex (https://www.convex.dev/) as backend. The generation of the backend code is fully deterministic, we map workflow graphs to code templates. This makes deployments predictable and avoids the hallucinated, black-box code you often get from AI.

Workflow representation: the logic is a directed graph where each node can be customized. We currently support CRUD operations and agent components. Any changes to the graph compiles directly back into code, so you always own the underlying logic.

Frontend: generated via AI and directly linked to workflow outputs, so it always stays in sync with the business logic. Changes to the frontend can be made through a chat interface.

Semi-technical builders can create maintainable apps (not opaque “magic”), and technical folks can still inspect the code and architecture. Compared to Bubble/Webflow, the interface is simpler; compared to Zapier, the workflows have an output code; and compared to AI coding assistants, you get an automatic backend plugged in with no black-box.

You can try it here: https://app.vibeflow.ai/. The demo video is https://youtu.be/-CwWd3-b1JI We'd love to hear from the HN community, whether you're a builder who's struggled with stitching tools together, a developer who's seen the pain points in no-code platforms, or someone curious about where AI-powered app generation is heading - we're eager for your thoughts!

I want to like this and dig into it as someone who has recently used Lovable and Base44 (and been using Bubble for a while), but the YouTube ‘demo’ video is really weak.

The pace is too fast and you spend barely any time showing off your visual workflow feature, which according to your description is your differentiator.

I would strongly recommend using some of your YC money to have a professional recreate that demo and show off what makes you unique. Even if it goes longer than two minutes - if I’m interested I’ll keep watching.

I’ll still try it out because I’m a sucker for trying out new vibecoding tools, but you’re not doing yourself any favors with that video…

In general to me it makes a lot of sense to lean much more into "templates" (I'm sure lovable etc already do it, because it's also a nice way to save money). And it's much easier to at least guarantee some basic security when it comes to auth, payments, db setup etc. Of course you can shoot yourself in the foot right after that.

Quite like the positioning of "this is the backend to your lovable ui", probably how chef (the vibe coding tool from the makers of convex) should have positioned it. (and kind of do).

This looks great! Can I export my end code / app and host it elsewhere easily? Where else would easily be able to host it?

I've been playing around with vibeflow for a while, it's impressive how fast you can go from a prompt to a working full stack app. The visual workflow editor is a game changer.

I think the evolution of vibe coding tool is definitely the editor. Having a black box with no way to maintain it is an absolute liability.

That's why I think app generators must be a good editor before being able to generate anything. It seems you went this way with the cool node interface.

I'm doing the same thing with https://luna-park.app, but for fullstack apps.

I've just tried my first prompt on your "try" setting, and what was generated wasn't anything like what I was expecting, to be honest. I asked for a workout tracking app with a good list of requirements (maybe it was too complex?), and the platform thoughts for quite a while. What I got was a template for a front end to connect to an AI agent for chats.

I like this. Any chance you'll be bringing similar tactility (is that a word) to the frontend? Granular changes to components via prompts leaves a lot to be desired.

Will have to try this later, the YT video looks promising. Found tools similar to this promising to create early mockups or other pre-prototypes when developing products.

I do like convex but do you support any other data stores?

Seeing the backend nodes generate feels like magic

Congrats! Doesn't replit have an integrated database as well? Lovable has supabase, and I'm pretty sure Base44 as well, plus other agent integrations.

I tried this but kept getting errors. I asked it to build a TODO list that searches the internet to "augment" my todo list with advice

Well I am/was building something that looks a lot like this, a shame I never applied to YC, wondering now if I should apply to other funds now so I can continue working on it, the prototype is ready so I have the main part figured out. A question, perhaps, could you give some tips to pitch this specifically, just for incubators, based on your experience?

[CONVEX M(events:insertEvents_ion)] [Request ID: bbc76cc0a8e100df] Server Error Called by client

Why did you use convex as backend?

nicely done. are you sideswiping n8n as well here? i like it.

congrats on the launch, lots of competition in this space. (leap.new, replit etc). Even convex has their own app-builder.

did you think about using Effect.ts as the backend? i'm interested in pros/cons there

Awesome. Really, really awesome. One day no one will actually know how to write code, and no one will be able to fix all this shit.

Now make this build desktop apps. We don't need more web or mobile apps

Don't get me wrong, I wish your start-up all the best, but this particular application seems so stereotypical by current standards. It's at least four buzzwords combined into one "idea". As someone who has never tried to apply, I wonder how difficult it was to get through Y Combinator's selection process.

That's the most 2025 startup name and idea i've come across so far.

[flagged]