Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

dbmate

github.com

  • Free plan
  • Windows
  • macOS
  • Linux
  • Self-hosted
7.9 Club score Visit github.com

What dbmate is

dbmate is a free, open-source database migration tool for keeping schemas consistent across developers and production servers. It is a standalone command-line program, so it can be used with Go, Node.js, Python, Ruby, PHP, Rust, C++, and other languages or frameworks. Migrations are plain SQL stored in timestamp-versioned files. The project lists MySQL, MariaDB, PostgreSQL, SQLite, and ClickHouse, and documents BigQuery connections plus Spanner support for databases using the PostgreSQL dialect. dbmate can create, apply, and roll back migrations, report migration status, and dump or load a schema. Migrations run in transactions by default when the database supports them, with individual files able to opt out. It can maintain a schema.sql file for source-control review and Git diffs, though dumping depends on 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.

Who it suits

It suits developers who want SQL-based migrations independent of their application language or framework. Go applications can also use dbmate as a library and embed migrations in an application binary.

Good to know, and what to watch

  • Supports five listed databases
  • Creates, applies, and rolls back migrations
  • Uses transactions by default when supported
  • Free and open source
  • Schema dumps require database client tools
  • Spanner schema dumps are not supported

dbmate

Free

Open source

The verdict

dbmate offers a language-independent way to manage SQL migrations and track schema changes. Check the database-specific limits and client-tool requirements if schema dumps are part of your workflow.

What the maker publishes

Additional database support
The README also documents BigQuery connections and Spanner support limited to databases using the PostgreSQL dialect. source
Commands
Its commands include creating, applying, and rolling back migrations, checking migration status, dumping or loading a schema, and waiting for a database server. source
Configuration
Dbmate reads DATABASE_URL by default and has built-in support for loading environment variables from a .env file. source
Databases
The README lists MySQL, MariaDB, PostgreSQL, SQLite, and ClickHouse as supported databases. source
Database support
The README lists MySQL, MariaDB, PostgreSQL, SQLite, and ClickHouse as supported databases. source
Distribution
The README documents installation through NPM, Homebrew, Scoop, a Linux binary, and Docker images published to GitHub Container Registry. source
Embedding
Dbmate can be used as a library in Go applications, and migrations can be embedded into an application binary using Go embed. source
Framework support
It is a standalone command-line tool usable with Go, Node.js, Python, Ruby, PHP, Rust, C++, or other languages and frameworks. source
Language independent
The standalone command line tool can be used with Go, Node.js, Python, Ruby, PHP, Rust, C++, or other languages and frameworks. source
License
The repository includes an MIT license. source
Limit
The README says Spanner schema dumps are not supported because pg_dump uses functions Spanner does not provide. source
Migration transactions
Migrations run atomically inside a transaction by default when the database supports transactions, and migration blocks can opt out. source
Purpose
Dbmate is a database migration tool that keeps database schemas in sync across developers and production servers. source
SaaS
The README says dbmate does not try to upsell users on a SaaS service. source
Schema snapshots
Dbmate can keep a schema.sql dump updated for review in source control; dumping relies on database client tools such as pg_dump, mysqldump, or sqlite3. source
Schema tracking
Dbmate can save a schema.sql file so schema changes can be diffed in Git. source
Security and company details
The opened README and repository page do not state security certifications, support terms, company headquarters, or a founding date. source
Security page
The repository's GitHub Security page is available, but the opened page does not state a security or compliance certification. source
SQL migrations
Migrations are written as plain SQL in timestamp-versioned files, which the README says helps avoid version number conflicts among developers. source
Support
The repository README links to a discussion of alternatives and a contribution guide, but the opened page does not specify a support service or response time. source
Transactions
Migrations run atomically inside a transaction, with per-migration transaction behavior configurable in migration files. source

Checked against the maker's pages on 5 Oct 2026.