Give your platform team a schema change control plane. Catch breaking changes before they merge, enforce migration standards across microservices, and keep every service's database contract reviewable.
Microservices multiply databases. Without a lightweight control plane, schema changes become a source of outages and blocked deploys.
A dropped column or a NOT NULL without a default can take down a service. Manual review misses semantic changes in long ALTER TABLE scripts.
One service uses Liquibase, another uses raw SQL, another uses ORM migrations. Platform engineers need a dialect-agnostic view that works everywhere.
Production schemas drift from source-controlled DDL. By the time someone notices, rollback is complicated and customer impact is real.
Senior engineers become bottlenecks because every schema change needs human eyes. Automating the first pass frees the team to ship faster.
A no-install, no-signup layer of schema visibility that fits into the workflows your teams already use.
Flag dropped tables, removed columns, type narrowing, NOT NULL additions, and missing indexes before they reach production.
Post markdown diff reports to PRs, fail Check Runs on breaking changes, and archive HTML reports as pipeline artifacts.
Commit a schemalens.lock file and verify it in CI. Catch unauthorized or accidental schema drift automatically.
Compare PostgreSQL, MySQL, MariaDB, SQLite, SQL Server, and Oracle schemas with the same tooling and output format.
Score schema complexity and map table/view dependencies to plan safe migration order across tightly coupled services.
Send schema drift alerts to Slack or Teams. Share a persistent alert page that teams can bookmark and revisit.
From ad-hoc review to continuous governance in four steps.
Paste two SQL dumps into the browser app or call the free /api/free-diff endpoint. SchemaLens parses the DDL and returns a semantic diff with risk scores.
Add the SchemaLens GitHub Action, GitLab CI template, or standalone Node.js script to your pipelines. It runs on every schema file change and posts a report.
Generate a lockfile from your canonical schema and verify it against production dumps on a schedule. Drift triggers a Slack alert and a dashboard entry.
Share the same diff rules, report format, and migration checklist across every team. No forced migration from their existing tools.
Drop SchemaLens into the CI/CD platforms and chat tools your teams already use.
Free micro-tools that plug into your schema governance workflow.
Map foreign-key and view dependencies, detect cycles, and compute a safe migration order across services.
Analyze dependencies →Score schema health, surface risk factors, and prioritize which services need refactoring attention.
Score schema →Create a signed lockfile from any SQL dump and verify it in CI to catch unauthorized schema drift.
Generate lockfile →A 32-point checklist for production schema changes, ready to print, share, or paste into a runbook.
Open checklist →Turn a SQL migration into a step-by-step runbook with rollback steps, verification queries, and comms.
Build runbook →Free webhook endpoint that posts schema drift notifications to Slack, Teams, or Discord.
Set up alerts →A complete propose-review-test-deploy-verify workflow for managing database schema changes across teams.
Read guide →Catch schema changes that break data pipelines, dbt models, and ETL workflows. Compare source and warehouse schemas.
Data engineering guide →How platform engineering teams use SchemaLens.
No, and it does not try to. SchemaLens is a review and governance layer. It diffs schemas, detects risks, and generates reports. You keep using Flyway, Liquibase, Prisma Migrate, or raw SQL migrations for actual deployments.
Add SchemaLens to each service's CI pipeline with the same config. Fail builds on breaking changes, require migration rollbacks, and archive reports. The shared report format keeps every team aligned without forcing a single migration tool.
No. SchemaLens works with SQL dumps, migration files, and schema exports. You can run it entirely client-side or in CI against files in your repo. It never needs a live database connection.
Yes. The standalone Node.js script has zero external dependencies and runs fully offline. You can also self-host the browser app or call the API from your own infrastructure.
The Team plan adds shared workspace features, persisted drift dashboards, and consolidated billing. While Gumroad Team products are pending, you can request an invoice or demo from the Team page.
Add SchemaLens to your platform engineering workflow in minutes. No signup, no install, no database connection required.