Migrations you don't write by hand
typescript postgres kysely
Enobase was a friend's early-stage startup. Between missions, I jumped in to build a piece of internal tooling the team kept tripping over.
Their database schema was declared in code, but the actual database drifted from it, and reconciling the two with hand-written migrations was tedious and easy to get wrong.
What shipped
Tooling that detects the changes made to the declarative schema and generates the corresponding TypeScript migrations for it — typed end to end with Kysely, so a schema edit turns into a reviewable migration instead of a manual chore.
Result
Schema changes stopped being a source of drift and foot-guns: the diff is the migration, and it's generated, typed and reviewable by default.
At a glance
clientEnobase — Brussels year2024 duration~5 months rolesolo — freelance
The idea
The declarative schema is the single source of truth. Every migration is diffed
out of it and generated as typed Kysely code — never written by hand.
Stack
typescript postgres kysely
want something similar?
Start a project
Tell me what's slow, manual, or fragile