Detect & reconcile DB migrations missing from local repo (Prisma-aware)

Executive Summary

Engineering teams that use ORMs such as Prisma and TypeORM routinely face a subtle failure mode: migrations that exist in production or CI but are missing or diverged from the local repository, causing broken CI pipelines, failed deployments, or silent schema drift during onboarding. This problem crops up across a sizeable market—roughly 2.0M engineering teams building on schema-as-code patterns—and is particularly acute for teams with multiple environments, frequent schema changes, or distributed committers. You could build a Prisma-aware developer tool that scans a repo and connected database(s), detects migrations present in running databases but absent or different in the local migration history, and offers a guided reconciliation flow: generate safe migration stubs, produce preview SQL, open corrective PRs, and optionally run simulation checks in CI. The product would ship as a CLI, GitHub/GitLab app and an IDE extension, with integrations for CI pipelines and permissions-aware enterprise connectors to inspect production schemas without leaking secrets. The timing is favorable: a $6.0B addressable market (2.0M teams at roughly $3K ACV each) is driven by accelerating ORM adoption, infrastructure-as-code practices, and the expectation that checks run automatically in PR pipelines. Differentiation comes from deep Prisma knowledge rather than generic schema diffing—familiar semantics for Prisma migrations, deterministic stubs, and heuristics tuned to avoid false positives—and from shipping low-friction developer UX (IDE hints, automated PRs) that reduces trust hurdles. Honest challenges include supporting multiple ORM versions and dialects, obtaining safe read-only access to production schemas, and convincing teams to trust automated migration generation; these are solvable but will require engineering effort and conservative defaults.