Wyro - Draw your backend. Export TypeScript you actually own.
by•
Your backend, drawn not typed. Wyro compiles the canvas into production
TypeScript — Express, Drizzle, Zod — then gets out of the way. No SDK, no
hostage situation. Delete your account; your app won't flinch. Free tier, no
card.
Replies
Best
Maker
📌
Hey Product Hunt 👋
I built Wyro because every AI app builder I tried was great until I wanted to
leave. The frontend you can always copy-paste out. The backend is the hostage —
their runtime, their database, their deploy target.
So Wyro compiles instead of hosting. You draw your backend on a canvas — routes,
tables, auth, queues, cron — and it emits a conventional Node project: typed
Express handlers, Drizzle schema and migrations, Zod validators.
The test I hold it to is the exported package.json:
express, drizzle-orm, postgres, zod, dotenv, jsonwebtoken
Nothing of mine in there. No SDK, no runtime shim, no phone-home. Delete your
Wyro account and your app doesn't notice.
There's an agent called Bliss that edits the canvas for you — "add auth and wire
it to the login route" is two surgical changes, not a rebuild. And if you've
already shipped something on another builder, you can point Wyro at its database
(or paste a schema dump) and your tables become editable blocks.
Honest state of it: early and solo-built. The generated code is the part I'm
most confident about and the part I most want torn apart. Payments are India-only
for a few more weeks while paperwork clears, so the free tier is the real entry
point today — and it's genuinely free, no card.
The most useful five minutes you can spend: describe a backend, watch the blocks
appear, hit export, and read what comes out before deciding whether you trust
any of this.
Would love your hardest questions about the compiler. That's the interesting
part.
Replies