Zanith · v0.2.0Open source · MIT

Your schema is
the runtime.

A SQL data engine that doesn't generate code. The schema parses once at startup into a runtime graph; queries compile to parameterized SQL on the way to the wire. Open source, MIT-licensed — the engine, the migrations, the Studio, all of it.

Read the architectural case Open the docs Star on GitHub

MIT · open sourceno build stepno generated files765 / 765 tests

zanith studio — fyvault_prodpostgres 17 · 127.0.0.1:5432

contractsSQL · 1migrations

id	title	status	created_by	_count.links
b4f1…9c2e	Crestline MSA renewal	active	ada	4
7d28…41aa	Fyvault DPA — EU region	active	bob	3
e901…77b3	Northwind pilot terms	draft	ada	2
30cc…d5f0	Atlas SOW #2	active	mei	6
f56a…08e1	Helios NDA (mutual)	draft	null	0

SELECT … , COUNT(links.*) AS _count FROM contracts LEFT JOIN LATERAL (…) ON TRUE — 1 query · 12.4ms

9 models · runtime graph · no codegen765/765 ✓

zanith studio · the engine's instrument panel · drawn in code, no images

PostgreSQL 14–17Prismadrop-inSQLiteTypeScript 5Node 18+MySQL — v0.4

findManyupsert$transactioninclude.select_count: { where }incrementmode: 'insensitive'hasSomeconnectOrCreateLEFT JOIN LATERALEXISTSON CONFLICTsoftDropColumnreseedArtifactcompat scan$queryRawgroupByhavingfindManyupsert$transactioninclude.select_count: { where }incrementmode: 'insensitive'hasSomeconnectOrCreateLEFT JOIN LATERALEXISTSON CONFLICTsoftDropColumnreseedArtifactcompat scan$queryRawgroupByhaving

02 — The pipelinelive · no codegen

Schema in. SQL out. Nothing generated in between.

zanith engine · schematic· v0.2.0 · runtime-first

● compile · 2.4µs / SELECT

schema in · 3 modelssql out · parameterized

step 01

Parser

.zanith→AST

22.9ms

step 02

Graph

AST→nodes

0.73ms

step 03

Compiler

graph→SQL

2.4µs

step 04

Adapter

SQL→pg

<5µs

wire · pg2.4µs

SELECT id, email, role FROM users WHERE email ILIKE $1;

no build step·schema = runtime

v0.2 · 765/765 green

parse once at boot · compile per query · parameterized to the wire

03 — The swapprisma → zanith · one file

Your Prisma code runs on Zanith. db.ts changes. Nothing else does.

src/lib/db.tsbeforeafter · zanith

import { PrismaClient } from '@prisma/client';

import { PrismaPg } from '@prisma/adapter-pg';

const prisma = new PrismaClient({

adapter: new PrismaPg({ connectionString }),

});

export { prisma }; // 1,400 call sites import this

1,400 call sites · untouched$extends chains · intactrollback · revert one filethe one-file swap, documented

04 — The gate

Destructive migrations refused.
Every drop recoverable.

Six risk levels, a hard gate, and artifacts that restore byte-identically — proven by the suite, not promised.

the recovery layer, documented

zanith migrate — fyvault_prod

05 — The engine, in tilesevery figure sourced · grep the repo

test suite · re-running

✓compat/prisma-selectors29

✓proof/06-flagship-claims16

✓engine/include-trees31

✓migrations/recovery24

✓compat/doctor3

✓adapter/pg18

0/765fully green · real postgres

1,000-model compile

0 ms

risk scoring

86 · DESTRUCTIVE

dropColumn legacy

REFUSED

0 · safe

data intact

atomic updates

stock: { increment: 1 }

41SET stock = stock + 1

filters · faithful

contains: 'ada'

LIKE '%ada%'

the whole engine

0 KB

esm · zero runtime deps · no client to generate

recovery · byte-identical

a91c·legacy

drop

artifact

restore

06 — Now shippingv0.2.0

Three surfaces landed since the engine.

● studio

Studio

The web UI, bundled with the engine. Eight tabs, two levels.

8 tabsFK drilldownbulk editEXPLAIN historyRLS inspector

$zanith studio

● migrate

Migrate

Generate, plan, verify, apply — with a risk model CI can gate on.

drift-awareshadow verifyrisk 0–9roll back N steps

$zanith migrate --verify

● recover

Recover

Every destructive op soft-dropped or archived. Restorable until cleanup.

soft-dropone-command restoreCSV / JSONL exportreseed

$zanith recover restore-table

one command to see all of it

$ zanith studio --allow-sql

✓ studio listening on http://127.0.0.1:4321

07 — Where to next

Pick the door that fits where you are.

door · 01

Read the architectural case

Why code generation is the wrong shape — and the path off it

The strongest argument for runtime-first, in eight chapters — with the canonical numbers and the architectural diagrams.

door · 02

Your schema is
the runtime.

Schema in. SQL out. Nothing generated in between.

Your Prisma code runs on Zanith. db.ts changes. Nothing else does.

Destructive migrations refused.
Every drop recoverable.

Three surfaces landed since the engine.

Studio

Migrate

Recover

Pick the door that fits where you are.

Read the architectural case

How it actually works

Real schemas, real SQL

The receipts

What's shipped, what's next

Your schema is the runtime.

Schema in. SQL out. Nothing generated in between.

Your Prisma code runs on Zanith. db.ts changes. Nothing else does.

Destructive migrations refused.Every drop recoverable.

Three surfaces landed since the engine.

Studio

Migrate

Recover

Pick the door that fits where you are.

Read the architectural case

How it actually works

Real schemas, real SQL

The receipts

What's shipped, what's next

Your schema is
the runtime.

Destructive migrations refused.
Every drop recoverable.