Evolve
github.com
- Free plan
- Windows
- Linux
What Evolve is
Evolve is a free, open-source database migration tool for Windows and Linux that applies plain SQL scripts. It keeps database changes synchronized across environments and development teams, including continuous integration and delivery workflows. Evolve is available as a .NET library, a .NET tool, and a standalone CLI. Supported databases listed in its documentation include PostgreSQL, SQL Server, SQLite, MySQL, MariaDB, Cassandra, and CockroachDB. Versioned migrations run once; repeatable migrations run again when their contents change. Evolve records migration names and checksums in a metadata table and checks them whenever it runs. Its commands are migrate, erase, repair, and info. Separate transactions are used by default, while TransactionMode can group scripts into one commit or rollback. Cluster mode coordinates nodes with a session-level lock. The standalone CLI targets x64 Windows and Linux without external dependencies. Runtime requirements vary by format, and Cassandra and CockroachDB have documented limitations.
Who it suits
Evolve suits developers and teams managing SQL migrations across supported databases, environments, and CI/CD workflows. It also fits self-hosted deployments needing library, tool, or CLI formats.
Good to know, and what to watch
- Free and open source
- Supports seven listed database systems
- Versioned and repeatable migrations
- Rollback and CI/CD automation support
- Standalone CLI has no external dependencies
- CockroachDB concurrent migrations are not officially supported
- Cassandra scripts require specific semicolon placement
- Runtime requirements vary by deployment format
- Project is maintained as unfunded free-time work
Plans
Every plan and priceEvolve
Open source
The verdict
Evolve provides SQL-based migrations, tracking, transaction controls, and cluster coordination across several databases. Review its runtime requirements and database-specific limitations before adopting it for production workflows.
What the maker publishes
- Automation
- It automates database changes and keeps them synchronized across environments and development teams, including for continuous integration and delivery. source
- Cassandra limitation
- For Cassandra scripts, commands must end with a semicolon as the last character on a line, and the `use <keyspace>;` command is unsupported by the underlying driver. source
- Cluster coordination
- Cluster mode uses a session-level lock to coordinate migrations across nodes and prevent concurrent Evolve commands on the same database. source
- CockroachDB limitation
- Concurrent migrations are not officially supported for CockroachDB because it does not implement `pg_try_advisory_lock`; the documented alternative is described as not battle tested. source
- Commands
- Its four commands are migrate, erase, repair, and info. source
- Deployment formats
- Evolve is available as a .NET library, a .NET tool, and a standalone CLI. source
- Migration tracking
- Evolve stores migration names and checksums in a metadata table and checks it each time Evolve runs. source
- Migration types
- Evolve supports versioned migrations that run once and repeatable migrations that run again when their content changes. source
- Purpose
- Evolve is a cross-platform database migration tool inspired by Flyway that uses plain SQL scripts. source
- Runtime requirements
- The .NET library requires .NET 4.7.2+ or .NET Standard 2.0/.NET 5.0, while the .NET tool requires .NET Core SDK 3.0 or later. source
- Standalone CLI platforms
- The standalone CLI is provided for x64 Windows and Linux and has no external dependencies. source
- Support
- The maintainer says the project is personal, free-time, and unfunded, and invites users and companies to support it through GitHub Sponsors; company donations are mentioned as a way to receive priority support. source
- Supported databases
- The documentation lists PostgreSQL, SQL Server, SQLite, MySQL, MariaDB, Cassandra, and CockroachDB. source
- Transactions
- By default, each migration runs in a separate database transaction; the TransactionMode option can instead commit or roll back a group of scripts together. source
Checked against the maker's pages on 9 Oct 2026.