Quickstart

Go from a blank canvas to a typed TypeScript repository on your machine — without a card, and without provisioning anything.

Steps 1–5 are the whole free path, start to finish. Every one of them works on the default hobby plan. Managed databases and the SQL Editor are a paid add-on and are covered separately at the end — you do not need them to get real code out.

Tip:You can skip signing in entirely for a first look: the box on the home page runs the same compiler this doc describes and returns readable files in a few seconds.

1. Sign in

Open wyro.in and sign in with Google. A user record is created on first login; your plan defaults to hobby, which includes 1 project, 10 compiles a month, and 5 AI generations.

2. Create a project

From the dashboard, hit + New project. A project is the unit that holds your backend design, your compiles, and — on paid plans — a dedicated database.

3. Draw the backend

Open Canvas from the project sidebar. Drag blocks onto it — API routes, tables, auth, file storage, queues, scheduled jobs — and connect them. The edges are not decoration: a route wired to a table compiles into a handler that actually queries that table.

If you would rather start from a sentence, use the Generate box at the top of the canvas and describe what you want. It lays out blocks you can then rewire by hand. Check what it produced before you compile — it infers a starting point, not a finished design.

4. Compile and read the code

Hit Compile on the canvas or from the project card on your dashboard. Wyro walks the graph and emits a typed Express codebase — src/api/* handlers, a Drizzle schema in src/db/schema.ts, and Zod validators alongside it. Compiling the same graph twice produces the same files, so a re-compile is reviewable as a normal diff.

Free accounts get 10 compiles a month; paid plans are unlimited.

5. Export it

Click Download to get the repository as a ZIP. It contains the full source plus Dockerfile, docker-compose.yml, railway.json, package.json and a README. Unzip it and start it with the standard Node toolchain:

npm install
cp .env.example .env      # add your DATABASE_URL
npm run dev

The DATABASE_URL can point anywhere Postgres runs — local, Neon, Supabase, RDS, or a Wyro-managed database if you add one below.

Tip:Export is unrestricted on every plan, including the free tier. Read exactly what the compiler produces and review it the way you would review a pull request from a teammate.

6. Optional: add a managed database

Note:This section needs a paid plan. Hobby accounts can design schemas and draft SQL, but cannot allocate a live database. Steps 1–5 above are unaffected.

Open SQL Editor from the project sidebar. In the left panel, click the + next to Databases, pick a name (alphanumeric, dashes/underscores ok), and confirm. Status reads Provisioning for ~30 seconds and flips to Healthy automatically.

Then type into the editor and press ⌘↵ (or click Run):

create table notes (
  id serial primary key,
  body text not null,
  created_at timestamptz default now()
);

Open Table Editor from the sidebar and your new table appears under Tables. Click it to view, edit, or insert rows without writing SQL.

Where to go next

  • Connect from your own code — credentials and connection strings are covered in the databases guide.
  • Deploy it — anywhere Node runs: Railway via the generated config, or any container host via the Dockerfile.
  • Check your limits — projects, compiles, AI generations and databases are all capped per plan.