Quickstart
Provision a real Postgres database and run your first query in under a minute.
1. Sign in
Open wyro.in and sign in with Google. A user record is created on first login; your plan defaults to hobby.
2. Create a project
From the dashboard, hit + New project. A project is the unit that holds your schema, queries, and a single dedicated database.
3. Provision a database
Inside the project, open SQL Editor from the sidebar. In the left panel, click the + next to Databases, pick a name (alphanumeric, dashes/underscores ok), and confirm.
Status will read Provisioning for ~30 seconds and flip to Healthy automatically.
4. Run SQL
Type into the editor and press ⌘↵ (or click Run). Try:
select now();
Or create a table:
create table notes ( id serial primary key, body text not null, created_at timestamptz default now() );
5. Browse rows
Open Table Editor from the project sidebar. Your newly-created table appears under Tables. Click it to view, edit, or insert rows without writing SQL.
6. 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.
7. 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.
8. 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 it runs on its own:
npm install cp .env.example .env # add your DATABASE_URL npm run dev
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.