I built a modern, self-hosted control plane to manage migrations

I built Open Migration because I was tired of "blind" database migrations causing deployment failures.

The standard way to handle migrations—running them automatically when the application starts—works perfectly until one day, it doesn't. You might have a migration fail halfway through, or a lock-contention issue that takes down your entire production environment before you even realize what happened.

I realized I needed a centralized "Control Plane"—a place where I could see all my databases (SQLite, Postgres, MySQL) and their migration history in one dashboard. I also wanted to fetch migration files directly from GitHub/GitLab without the overhead of project-specific CI/CD jobs.

So I built it myself.

What it does:

Centralized management for all your databases from one UI. Native SCM integration to securely fetch migration files via tokens. Framework-agnostic (works for any stack). Everything is self-hosted