The video series
See MetaObjects in motion.
Start with the introduction for the whole idea, then the short feature videos — each one shows a single capability end to end, from one model.
Introduction — one model, the whole app
The problem MetaObjects solves, what it actually is, and how the codegen and runtime halves work together — about eight minutes.
Getting started — build a typed app from one model
Watch Claude Code build a working task tracker on MetaObjects: one model becomes the database, validation, a CRUD API, forms, hooks, and a grid — and it can't silently drift.
Assess your repo — find the drift you already shipped
Before you adopt anything: paste one message into your coding agent and it runs a read-only fit assessment against your repo — including a drift ledger mined from your own git history. Nothing installed, nothing edited. Try it on your repo →
Adopt an existing app — one table at a time
You don't have to start over to start. Point MetaObjects at one table of a real app, get typed code for it, and leave the rest untouched. Not sure it's worth it yet? Run the fit assessment first — it's read-only and finds the drift already in your history.
Drift detection — make drift a compile error
meta verify checks that your code, your prompts, and your database schema still agree with the model — any mismatch fails the build.
Runtime metadata — drive the UI live
The same model can drive your app live, at runtime. One generic function builds a grid for any object you've described — no code generation.