Replay in memory
Run the folder twice against :memory: and fail the hook if the second pass errors.
Under Validation
A planned local pre-commit hook that replays a folder of .sql files into an in-memory SQLite database and flags re-run errors plus obvious data-loss (DROP COLUMN, destructive type changes). Not a Flyway or Atlas replacement. Waitlist only.
Concept validation only. No payment, no commitment, no recurring newsletter.
Proposed workflow
Concept stage. Signup measures whether the SQLite-only hook is searched for.
Run the folder twice against :memory: and fail the hook if the second pass errors.
Warn on DROP COLUMN and type changes that can lose data. Heuristic, not a formal proof.
SQLite only. No cloud, no schema DSL, no multi-dialect platform.
The honest status
The concept is being validated before development time is committed. Joining tells us the problem is relevant to you and gives you first access if the evidence supports a build.
Before you decide
The current scope, privacy model, and next step without launch-day promises.
Atlas is a schema-as-code platform with 50+ checks. This concept is a zero-config SQLite folder replay only. If Atlas already fits, use Atlas.
No. This page is waitlist-only concept validation.
No. In-memory replay misses filesystem, encoding, and production-data edge cases. You still review the SQL.
Your email is recorded for this experiment only. You receive one relevant update or beta invitation if the concept moves forward.
Early access
Join the waitlist. One email if a local beta opens.
Leave your email to receive the beta invitation if this concept moves forward.