Sqitch

Overview

Sqitch is a database change-management tool for teams that prefer to write migrations as database-native scripts and manage their order explicitly. It is a strong fit for SQL-comfortable teams working across database engines; it is less suitable when a project needs migrations abstracted from engine-specific scripts or cannot install native database dependencies.

Key features

Sqitch keeps changes in the selected database engine’s own script format rather than tying projects to an ORM, framework, or development environment. That gives database-focused teams control over the scripts they deploy, but does not make those scripts portable between engines.

A plan file captures changes and their dependencies, including dependencies on changes in other Sqitch projects. Sqitch uses a Merkle tree pattern to protect deployment integrity, and change names need not be numbered. This lets teams express execution order through declared relationships rather than filename numbering.

Committed deployment scripts may be edited during development before the project is tagged and released. That flexibility supports iteration, but teams should treat tagging and release as a meaningful boundary for stabilizing the change history.

Sqitch can deploy and revert changes, report deployment status and history, and run optional verification scripts during deployment. Verification gives teams a way to check deployed changes as part of the process; rollback support is useful when a change needs to be undone.

The manual lists support for PostgreSQL, YugabyteDB, CockroachDB, SQLite, MySQL, MariaDB, Oracle, Firebird, Vertica, Exasol, Snowflake, and ClickHouse. Execution requires each target database’s native command-line client and connector libraries, so teams should account for those prerequisites in their environment setup. Sqitch deliberately offers no command-line password option, avoiding a route by which credentials could end up in shell history or be exposed to other users.

Pricing

Sqitch is free and open source. Its Sqitch plan costs nothing and grants permission to use, copy, modify, merge, publish, distribute, sublicense, and sell the software subject to the license condition. There are no paid tiers to trade off against the free plan. The software is provided without warranty.

Platforms

Sqitch supports Linux, macOS, Windows, and self-hosted use. Installation options include source and Docker, Linux distribution packages for Red Hat and Ubuntu/Debian, Homebrew on macOS, and Windows installation instructions. The operating-system options are broad, but database-specific client and connector dependencies remain part of setup.

Who it's for

Sqitch suits teams that want framework-independent database change management, are comfortable writing engine-native scripts, and value declared dependencies, verification, and rollback. It is a particularly practical choice when database changes need explicit ordering without numbered change names. Look elsewhere if the project needs a migration layer that hides engine differences or if installing native database clients and connectors is not viable.

Pros and cons

• Database-native scripts: teams can use the selected engine’s own script format without adopting an ORM or framework.
• Explicit dependency planning: a plan file can express ordering across changes and Sqitch projects, without numbered names.
• Deployment safeguards: integrity tracking, optional verification, status and history reporting, and revert commands support controlled change management.
• Broad database coverage: the supported list spans relational engines and services including Snowflake and ClickHouse.
• Operational prerequisites: every target requires its native command-line client and connector libraries.
• Engine-specific scripts: the native format avoids framework mediation but leaves database differences in the scripts themselves.
• No warranty: adopters take on the risk associated with using software distributed without warranty.

Alternatives

For MySQL-focused teams, Skeema offers a free Community plan with tables, stored procedures and functions, and 18 linter checks on Linux and macOS; its Plus plan is $124 a month. sqlx-cli is another free option for database management, migrations, and offline query metadata across Linux, macOS, and Windows.

Atlas may suit teams looking for an open-core option: its core engine is Apache 2.0 licensed, with advanced features available in a proprietary offering. dbmate is a free open-source migration tool for Linux, macOS, self-hosted use, and Windows.

FluentMigrator is worth considering for teams that want an Apache-2.0 licensed framework distributed through NuGet, with provider packages selected separately. golang-migrate and Goose are also free open-source migration tools. For PostgreSQL 14.0 or later, pgroll offers an open-source option distributed as a single cross-platform binary.

Browse Database Migration Tools or Database Testing Tools for more options.

Verdict

Choose Sqitch if your team wants a free, standalone system for database-native migrations with explicit dependencies, verification, and rollback. Its strongest reason to choose it is the combination of engine coverage and structured change planning without a framework dependency. Choose another tool if your workflow requires abstraction from engine-specific scripts or you cannot provide the native clients and connector libraries each database needs.