Wyro

Design, query, and ship Postgres-backed apps without leaving the browser.

What you get

  • A real, dedicated Postgres database per project — provisioned on demand.
  • Visual Schema Designer for modeling tables and relationships.
  • SQL Editor with multi-tab queries, saved snippets, and one-click run.
  • Table Editor for browsing, inserting, and editing rows.
  • Firebase-backed auth, per-user data isolation, and plan-based limits.

What compiling produces

Compiling turns the canvas into an ordinary Express application on disk — the dependency tree is Express, Drizzle and Zod, with nothing bespoke in it to learn before you can read the code:

  • src/index.ts — the Express app: middleware, and every route mounted.
  • src/api/*.ts — one handler module per route block on the canvas.
  • src/db/schema.ts — Drizzle table definitions, and src/db/schemas.ts for the matching Zod validators.
  • src/middleware/auth.ts, src/auth/* — JWT verification, OAuth sign-in, and role checks.
  • src/jobs/*, src/flows/*, src/logic/* — queue consumers, cron handlers, and the branch/map/filter steps you wired up.
  • Dockerfile, docker-compose.yml, railway.json, README.md — everything needed to run it somewhere.

The runtime dependencies are express, drizzle-orm, postgres, zod, cors, helmet, morgan, jsonwebtoken and nodemailer — all of them packages you can audit or swap.

Start here

Pick the path that matches what you want to do first:

  • Quickstart — draw a backend, compile it, and download the repository on the free tier.
  • Databases — provisioning, credentials, and connecting from your own code.
  • SQL Editor — multi-tab queries, saved snippets, keyboard shortcuts.
  • Table Editor — browse and edit rows without writing SQL.
  • Architecture checks in CI — fail a pull request that introduces a new violation.
  • Plans & billing — what each plan includes.