Wyro – 在画布上绘制后端，导出无锁定的 TypeScript
2 分•作者: Paaul01•5 天前
大家好，HN。Wyro 是一个可视化后端构建器，可以编译成您完全拥有的纯 TypeScript 代码库。
**动机：** AI 应用构建器在生成应用方面做得很好，但在让您离开方面却一直很糟糕。前端代码您可以随时导出。后端才是人质——它们的运行时、它们的数据库、它们的部署目标。
**工作原理：** 您在一个画布上连接块（HTTP 路由、表、身份验证、队列、cron、多步管道）形成一个图。该图是一个中间表示 (IR)，编译器将其降级为一个常规的 Node 项目——类型化的 Express 处理程序、Drizzle schema 和迁移、从表定义派生的 Zod 验证器，以及 `postgres` 作为驱动程序。运行时没有任何解释；图不会被发送，它会被编译掉。
**我用来测试的标准：** 导出的 package.json 列出了 express、drizzle-orm、postgres、zod、dotenv、jsonwebtoken。没有我的包。删除您的 Wyro 账户，应用程序将继续运行。
**数据库的工作方式相同——连接您自己的 Supabase，并且配置将在您的组织中，由您付费，通过管理 API 进行。我掌握画布，而不是您的基础设施。**
**真实情况：** 这是一个早期且由我一人构建的项目。生成的代码是我最自信的部分，也是我最希望被拆解的部分。粗糙之处在于围绕产品，而不是编译器。
**免费套餐，无需信用卡。您可以在五分钟内完成的有用的事情是导出项目并阅读可 diff 的代码，然后再决定是否信任它。**
https://wyro.vercel.app
**特别希望得到任何已从托管构建器迁移出来的人的反馈——哪些地方出了问题，以及您希望导出包含哪些内容。**
查看原文
Hi HN. Wyro is a visual backend builder that compiles to a plain TypeScript
repo you own outright.<p>The motivation: AI app builders got good at generating apps and stayed bad at
letting you leave. Frontend code you can always lift out. The backend is the
hostage — their runtime, their DB, their deploy target.<p>How it works: you wire blocks on a canvas (HTTP routes, tables, auth, queues,
cron, multi-step pipelines) into a graph. That graph is an IR, and the compiler
lowers it to a conventional Node project — typed Express handlers, Drizzle
schema and migrations, Zod validators derived from the table definitions,
`postgres` for the driver. Nothing is interpreted at runtime; the graph isn't
shipped, it's compiled away.<p>The test I hold it to: the exported package.json lists express, drizzle-orm,
postgres, zod, dotenv, jsonwebtoken. No package of mine. Delete your Wyro
account and the app keeps running.<p>Databases work the same way — connect your own Supabase and provisioning
happens in your org, on your bill, over the Management API. I hold the canvas,
not your infrastructure.<p>Honest state of things: it's early and solo-built. The generated code is the
thing I'm most confident about and the thing I most want torn apart. Rough
edges are in the surrounding product, not the compiler.<p>Free tier, no card. The useful thing you can do in five minutes is export a
project and read the diff-able code before deciding whether you trust it.<p>https://wyro.vercel.app<p>Would especially like feedback from anyone who has migrated off a hosted
builder — what broke, and what you wished the export had included.