启动 HN：VibeFlow（YC S25）——具有可视化和可编辑工作流程的网页应用生成器
嗨，HN！我们是Alessia和Elia，VibeFlow的创始人（<a href="https://vibeflow.ai">https://vibeflow.ai</a>）。VibeFlow让半技术人员（即具备一定技术技能但不是专业程序员的人）能够通过自然语言提示构建全栈网页应用，同时将底层业务逻辑以可视化工作流的形式清晰呈现并可编辑。演示视频：<a href="https://www.youtube.com/watch?v=-CwWd3-b1JI" rel="nofollow">https://www.youtube.com/watch?v=-CwWd3-b1JI</a>。
我们试图解决的问题是：如今，想要无编码构建应用的人往往需要将多个工具拼凑在一起，例如使用Lovable作为前端，n8n处理工作流，Supabase作为数据库。这会造成数据孤岛，使得构建者面临脆弱的应用，这些应用在生产环境中容易崩溃，无法扩展且不安全。我们看到YouTube教程教人们如何将这些工具“粘合”在一起，以便让应用能够正常运行。作为构建无代码工具的工程师，我们意识到人们希望拥有AI生成用户界面的强大功能，同时也希望能够查看和控制他们的后端工作流和数据。
我们的解决方案是一次性生成整个应用，并将其表示为可视化工作流。用户用英语描述他们想要的内容（“我需要一个带AI代理的聊天小部件”），VibeFlow会生成界面和逻辑。这些逻辑以工作流图的形式呈现，用户可以通过可视化编辑或给出新指令来修改。
我们使用Convex（<a href="https://www.convex.dev/" rel="nofollow">https://www.convex.dev/</a>）作为后端。后端代码的生成是完全确定性的，我们将工作流图映射到代码模板。这使得部署可预测，避免了从AI获得的幻觉般的黑箱代码。
工作流表示：逻辑是一个有向图，每个节点都可以自定义。我们目前支持CRUD操作和代理组件。对图的任何更改都会直接编译回代码，因此您始终拥有底层逻辑。
前端：通过AI生成，并直接链接到工作流输出，因此始终与业务逻辑保持同步。前端的更改可以通过聊天界面进行。
半技术人员可以创建可维护的应用（而不是不透明的“魔法”），技术人员仍然可以检查代码和架构。与Bubble/Webflow相比，界面更简单；与Zapier相比，工作流有输出代码；与AI编码助手相比，您获得的是自动连接的后端，没有黑箱。
您可以在这里试用：<a href="https://app.vibeflow.ai/">https://app.vibeflow.ai/</a>。演示视频在这里：<a href="https://youtu.be/-CwWd3-b1JI" rel="nofollow">https://youtu.be/-CwWd3-b1JI</a>。
我们非常希望听到HN社区的反馈，无论您是曾经在拼凑工具中挣扎的构建者，还是看到无代码平台痛点的开发者，或是对AI驱动的应用生成未来感到好奇的人——我们期待您的想法！
查看原文
Hi HN! We’re Alessia and Elia, the founders of VibeFlow (<a href="https://vibeflow.ai">https://vibeflow.ai</a>). 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: <a href="https://www.youtube.com/watch?v=-CwWd3-b1JI" rel="nofollow">https://www.youtube.com/watch?v=-CwWd3-b1JI</a>.<p>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.<p>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.<p>We use Convex (<a href="https://www.convex.dev/" rel="nofollow">https://www.convex.dev/</a>) 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.<p>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.<p>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.<p>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.<p>You can try it here: <a href="https://app.vibeflow.ai/">https://app.vibeflow.ai/</a>. The demo video is <a href="https://youtu.be/-CwWd3-b1JI" rel="nofollow">https://youtu.be/-CwWd3-b1JI</a>
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!