dbmate vs Ridgepole
dbmate
github.comRidgepole
github.comSide by side
| Figure | dbmate | Ridgepole |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Database Migration Tools | 8.6 (#3) | 7.1 (#27) |
| Database support | The README lists MySQL, MariaDB, PostgreSQL, SQLite, and ClickHouse as supported databases. | The README documents MySQL and PostgreSQL examples and states that SQLite is not supported. |
| Distribution | The README documents installation through NPM, Homebrew, Scoop, a Linux binary, and Docker images published to GitHub Container Registry. | Ridgepole is distributed as a Ruby gem and the repository identifies its license as MIT. |
| Purpose | Dbmate is a database migration tool that keeps database schemas in sync across developers and production servers. | Ridgepole manages database schemas by defining them with Rails DSL and updating the database to match. |
Plans
In their own words
dbmate
dbmate is a free, open-source command-line tool for keeping database schemas in sync across developers and production servers. It works independently of application language and can be used with Go, Node.js, Python, Ruby, PHP, Rust, C++, and other languages or frameworks. Migrations are plain SQL in timestamp-versioned files. Commands create, apply, and roll back migrations, check status, dump or load a schema, and wait for a database server. The project lists MySQL, MariaDB, PostgreSQL, SQLite, and ClickHouse, and documents BigQuery connections and Spanner support for databases using the PostgreSQL dialect. Migrations run atomically in a transaction by default when the database supports transactions, though individual migration blocks can opt out. dbmate can maintain a schema.sql dump for source-control review and Git diffs; creating dumps relies on database client tools such as pg_dump, mysqldump, or sqlite3. It reads DATABASE_URL by default and can load environment variables from a .env file. Installation options include NPM, Homebrew, Scoop, a Linux binary, and Docker images. Go applications can use it as a library, and Go embed can package migrations into an application binary.