1 of 3

SCHEMASYNC · HACK THE NORTH

2026

10:00 AM

9/20/2026

SchemaSync

GitHub for your database

Everyone has dropped a column in prod. SchemaSync versions your schema like code, shows every change as a live ER diagram, and has an AI review board check each migration against your real codebase before it ships.

COMMIT

DIFF

REVIEW

psql — production

ERROR

column "total" does not exist

LINE 1: SELECT total

FROM orders ...

Rollback

Panic

Existing tools version your schema as text. The real danger lives in the code that depends on it.

2 of 3

SCHEMASYNC · HACK THE NORTH

2026

10:00 AM

9/20/2026

Live demo

WHAT TO WATCH FOR

1

Branch + diff

The ER diagram animates the new payments table

2

Review board

Five agents review the merge, stage by stage

3

Impact Scout

Finds orders.total still used in 4 real files

4

Revision

The Engineer rewrites a DROP into a safe migration

5

Dry-run

Passes on real Postgres with seeded data

6

Ship

Approve opens a real PR, Linear tickets, and Slack

0:25 – 2:30 (~2 minutes). Switch to the app now. Keep talking while things load.��1. BRANCH + DIFF (~20s)�"Here's our production schema: users, products, orders. I'll branch off to add payments."�Commit the transactions table. Click compare.�"The new table glows in, the foreign key draws itself, and the rename from email_addr to email is detected as a rename, not a drop."��2. OPEN THE MERGE REQUEST (~10s)�"I'll also drop orders.total, which looks harmless, and open a merge request."��3. REVIEW BOARD (~45s)�"Five agents now review this, running on openJiuwen with Backboard as the brain."�Point at the Impact Scout: "It searched our real repo through Composio and found orders.total in 4 files."�Point at the revision: "So the Migration Engineer rewrote its own plan. Instead of a DROP, it's now an expand/contract migration."�"And it dry-ran that against real Postgres with seeded data. It passed."��4. APPROVE + SHIP (~25s)�Click Approve. "Nothing ships without a human. Now it opens a real PR, files a Linear ticket per affected file, and posts to Slack."�Show the PR in the GitHub tab.��5. MEMORY (~15s, cut if short on time)�"And if I make a similar change later, the Leader remembers the lesson from this one."��FALLBACK: if anything breaks, hit "Play review" for the scripted run, or play the backup video. Don't debug on stage.

3 of 3

SCHEMASYNC · HACK THE NORTH

2026

10:00 AM

9/20/2026

How it works

Diff engine

Rust on libpg_query, Postgres's own parser, with a round-trip test proving every migration is exact.

Review board

Five agents on openJiuwen. Backboard for models and memory, Composio for GitHub, Linear, and Slack.

Migration CI

Go generates the SQL and dry-runs it on real Postgres with seeded rows, in milliseconds.

BUILT WITH

MONGODB ATLAS

BACKBOARD

OPENJIUWEN

COMPOSIO

Also: React, Node.js, Python, Go, Rust, PostgreSQL, Redis, PyTorch, Docker

Questions?

Ship schema changes without fear.