Define your schema with s.* — a drop-in for Zod. Schemic generates your database's native DDL,
validates at runtime, and runs your migrations.
TypeScript-first Zod-compatible MIT
But you already describe your data in TypeScript.
// schema in, native ddl out
s.* schema to generated native DDL .
Define your tables and fields in TypeScript — the native DDL is generated for you.
// what you get
A drop-in s.* schema, generated
DDL, a migration CLI, end-to-end types, the full
define* vocabulary, and a live round-trip
— all from one typed file.
A 1:1 drop-in for z.* — refinements,
defaults, coercion, and infer / input / output.
email: s.string(),
name: s.string().optional(),
createdAt: s.datetime(),
Migrate an existing schema by find-replacing z.
→ s. Nothing new to learn.
Introspect a live database into typed schema files.
sc status sc check sc doctor
sc rollback sc seed sc pull
Infer row shapes straight from the schema.
type User = App<typeof User>
Unsupported types are flagged in your editor — not at migration time.
Store any class with a typed codec — app value in, wire type out.
Diff against the running database.
// the cli
Write a migration from your schema, apply it, and check for drift against the live database — three commands, no DDL by hand.
// if you know Zod, you already know this
Go past tables and fields. Events, functions, and access rules all live in the same typed source — and generate real DDL.
// common questions
+
Yes — s.* is a 1:1 drop-in for z.*. Migrate an existing schema by find-replacing z. → s. If you know Zod, there's nothing new to learn.
+
Hand-written DDL drifts from your types. Schemic keeps your schema, the generated DDL, and your TypeScript types as one source of truth — generated, never out of sync.
+
Three commands cover the whole loop: one writes a migration from the schema diff, one applies it, one checks for drift.
sc gen sc migrate sc diff --live
+
SurrealDB and Postgres are available today; more databases are on the way through drivers. Each driver maps the full define* vocabulary — tables, fields, indexes, events, functions, and access — to that database's DDL. MIT licensed.
+
Yes. One command introspects the live database and generates the matching s.* schema files, so you start from the database you already have and migrate forward.
sc pull
+
No — it sits on top. You keep your database's official client for queries; Schemic owns the schema, the generated DDL, the migrations, and the row types.
+
Neither. Schemic is a schema + migrations toolkit. It owns the schema, the generated DDL, and the migrations; pair it with your database's query tools.
+
Always. Schemic owns the schema and migrations, not your queries — use your database's client directly, and compose raw expressions into defaults, events, permissions, and functions where a driver supports it.
// set up with ai
Let your AI coding agent set up Schemic for you. Paste this prompt into Claude Code, Cursor, or any agent — it installs and configures the right driver for your database, brings your schema into TypeScript (new or existing), and prepares your first migration for you to review and run, explaining each step.
one prompt · full setup
Read the full guideGenerate the DDL, run the migrations, keep your types — straight from the schema you already wrote.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。