In order
Change 12 never runs before change 11.
Running inside SAIG
SAIG Schema · part of SAIG
Database changes,in order, once,every time.
Applies each app's numbered database changes safely, in order and once only, and stops at the first error. It records what ran, so nobody guesses what state a database is in.
One SAIG account for every app. No separate sign-up.
Already doing the work inside SAIG. Opening to customers next.
Change history per appBaselines for existing databasesNext: One-click rollback plansNext: Changes for Studio customer apps
What it does
Three jobs, done properly.
Once only
A change that already ran is never run twice.
Stops at the first error
A failed change halts the run and says why, before anything else breaks.
Replaces Deploy pipelines and the Supabase CLI
How it fits
Not a tool on its own. A part of SAIG.
SAIG is a group of 66 apps that share one account, one way to pay, one AI and one record of every decision. SAIG Schema plugs into the rest, so each app does its job once and every other app benefits.
In use
Already at work inside SAIG.
SAIG runs its own businesses on its own apps first. These are real uses, not mock-ups.
Every estate app
Database changes for estate apps are recorded here, so the history of every table can be read back.
Moving house
As apps move onto SAIG Data, Schema sets the baseline so the move starts from a known state.
For developers
Every SAIG app and engine is reached through /api/ext with its own per-app key. Health is public at /api/ext/health.
The SAIG ecosystem
66 apps. One account. One intelligence.
Travel, finance, legal, property, education and the engines underneath them, run by Skylite Group and built in the open. Start with the app you need; the rest is there when you are ready.
66apps on the grid
1SAIG account