schema / drift

Read-only schema incident review

See what drifted.
Repair nothing yet.

Turn PostgreSQL or MySQL catalog differences into a review your team can reason about—destructive risk, ORM blind spots, and likely ownership included.

Install the CLI Try the local demo
  • No row data
  • No repair SQL
  • No schema upload
Paper-cut database diagrams separated by a coral seam, representing drift between expected and production schemas.
Expected schemaObserved drift

PostgreSQL

portable snapshot

classified review

MySQL

A calmer incident path

Three artifacts. One decision.

The CLI stays outside your migration framework. It gathers metadata, labels the gap, and stops before a repair becomes executable.

  1. 01

    Capture both edges

    Use a catalog-only role. Keep names, or hash them consistently before an incident artifact leaves your machine.

  2. 02

    Separate the layers

    Columns, indexes, foreign keys, tables, and views are compared in a stable, versioned format.

  3. 03

    Review before repair

    Every difference gets a risk, visibility flag, likely owner, and plain-language reason—never destructive SQL.

Single local binary

From catalogs to Markdown

Build with stable Rust today. Factory-owned release archives can be attached without changing the command surface.

shell
cargo install --git https://github.com/B-Divyesh/sf-schema-drift-snapshot --bin sds
$ sds snapshot --url "$DATABASE_URL" --output prod.json
$ sds compare --before expected.json --after prod.json --output review.md
Wrote 6 classified differences to review.md

Browser-local sample

Open the layers yourself

These are small SDS snapshots. Edit either one, then compare. Input stays in this tab and is never sent anywhere.

Never uploaded

Ready to separate the layers

Run the comparison to classify this sample.

Classification vocabulary

Built for the awkward boundary

High risk

Destructive

Removed tables or columns, stricter nullability, and changed types get an explicit stop-and-review signal.

Review

ORM-invisible

Views and database-native details are called out where an ORM model may not tell the whole story.

Additive

Likely owner

Naming and object kind suggest the migration tool, database, or out-of-band DDL path to investigate first.

One-time team tool

Keep the review free.
Unlock CI policy for $49.

Every developer gets capture, redaction, classification, ownership guidance, Markdown, and JSON. Pro adds configurable CI risk gates for one team.

$49 one time

Buy Pro through Sociobot

Sociobot / Dodo is the merchant of record. Refunds revoke the associated license.

Paste the license token from your receipt. Stored only in this browser.

Before the migration window

Make drift reviewable.
Keep repair deliberate.

Install Schema Drift Snapshot