Sqitch
sqitch.org
- Free plan
- Windows
- macOS
- Linux
- Self-hosted
What Sqitch is
Sqitch is a free, open-source application for managing database changes. It works independently of a particular framework, ORM, database engine, or development environment. Changes are written as scripts native to the selected database engine, and can declare dependencies on other changes, including changes in separate Sqitch projects, to determine execution order. A plan file and Merkle tree pattern help check deployment integrity without requiring numbered change names.
Sqitch can deploy and revert changes, report deployment status and history, and run optional verification scripts. Committed deployment scripts can still be revised during development before a project is tagged and released. The manual lists support for PostgreSQL, YugabyteDB, CockroachDB, SQLite, MySQL, MariaDB, Oracle, Firebird, Vertica, Exasol, Snowflake, and ClickHouse. To connect to a database and execute scripts, Sqitch requires that engine’s native command-line client and connector libraries. Installation options include source, Docker, Linux packages, macOS Homebrew, and Windows instructions. Its license permits use and distribution subject to a stated condition, and provides the software without warranty. Help is available through GitHub Discussions, the Sqitch Users mail list, and Stack Overflow.
Who it suits
Sqitch suits developers and database teams who want a framework-independent way to plan, deploy, verify, and revert database changes. It is especially relevant when database-native scripts and explicit change dependencies fit the team’s workflow.
Good to know, and what to watch
- Works independently of frameworks and ORMs.
- Changes can declare dependencies across projects.
- Deployments can be verified and reverted.
- Supports a wide range of listed database engines.
- Available for Linux, macOS, Windows, and self-hosted use.
- Requires a database-native command-line client and connector libraries.
- Software is provided without warranty.
- Filing project issues requires a GitHub account.
Plans
Every plan and priceSqitch
Open source
Getting started
- Open the Sqitch website
- Choose a source, Docker, Linux package, macOS Homebrew, or Windows installation option
- Install the database engine’s native command-line client
- Install connector libraries for the database engine
- Create native database change scripts and define their dependencies
- Use Sqitch commands to deploy, verify, or revert changes
The Club's review
Overview
Sqitch is a free, open-source database change management application built around scripts native to each database engine. It is best for teams that want framework-independent migrations, explicit dependencies, and command-line control across varied environments. The trade-off is operational: every target database requires its native client and connector libraries.
Because Sqitch is standalone rather than tied to an ORM, framework, database engine, or development environment, it can fit heterogeneous projects and established database practices. Its SQL migration format gives database specialists direct control, but teams must maintain engine-specific scripts rather than expecting one abstraction to smooth over database differences.
Key features
Changes are implemented as scripts native to the selected engine. This is a strong choice when PostgreSQL, MySQL, Oracle, or another supported system's own capabilities matter, and when developers are comfortable writing SQL. It is less suitable for organizations seeking a database-agnostic migration language.
A plan file records changes and their dependencies, including dependencies on changes from other Sqitch projects. Sqitch uses a Merkle tree pattern to protect deployment integrity, and change names do not need numeric prefixes. In practice, teams can express execution order through relationships instead of relying on filename numbering, which is useful for projects with parallel work or shared change sets.
Deployment scripts may be modified after being committed to version control until the project is tagged and released. That supports iterative development before a release boundary, while teams should treat tagging as the point at which the migration history becomes fixed for dependable delivery.
Sqitch can deploy and revert changes, report deployment status and history, and run optional verification scripts during deployment. Revert commands provide a defined rollback path, while verification gives teams a way to check that a deployed change behaves as expected. These controls favor disciplined release processes over ad-hoc database edits.
Credential handling is deliberately conservative: Sqitch has no command-line password option, avoiding passwords being captured in shell history or exposed to other users. The consequence is that operators must use another supported way to provide credentials.
Installation options include source, Docker, Red Hat and Ubuntu/Debian packages, macOS Homebrew, and Windows Strawberry Perl instructions. Support is documented for PostgreSQL, YugabyteDB, CockroachDB, SQLite, MySQL, MariaDB, Oracle, Firebird, Vertica, Exasol, Snowflake, and ClickHouse. The database-native client and connector requirement remains a prerequisite for executing scripts and connecting to each engine.
Pricing
Sqitch costs nothing under the Sqitch plan. It is open source, with a license that permits use, copying, modification, merging, publishing, distribution, sublicensing, and sale. The license also states that the software is provided without warranty, so adopters remain responsible for operational support and risk assessment. There are no paid tiers or usage caps described, making it suitable for teams that want to deploy the same tool without per-user or per-environment fees.
Platforms
Sqitch runs on Linux, macOS, Windows, and self-hosted installations. Its source, Docker, distribution-package, Homebrew, and Windows installation paths cover both locally managed tooling and server-side deployment workflows. Platform availability does not remove the need to install the relevant database client and connector libraries.
Who it's for
Sqitch is a strong fit for database-led teams, infrastructure engineers, and developers who prefer SQL native to their engine and need explicit dependency tracking, verification, status history, and rollback. It also suits organizations managing several database technologies without wanting an ORM or framework to dictate migration structure.
Look elsewhere if your priority is a single database-agnostic migration format, a managed web interface, or an experience that bundles database drivers and clients. Sqitch's flexibility assumes technical ownership of scripts, credentials, connectors, and installation.
Pros and cons
Pros
- Framework independence: Works without tying migrations to an ORM, framework, database engine, or development environment.
- Explicit dependency model: Cross-project dependencies and a plan file define order without numbered change names.
- Integrity and control: Merkle-tree deployment integrity, optional verification, status history, and revert commands support auditable releases.
- Broad engine coverage: Documented support spans major commercial, open-source, cloud, and analytical databases.
- Zero purchase price: The free open-source plan has no stated seat or usage charge.
Cons
- Operational prerequisites: Every target needs a database-native command-line client and connector libraries.
- Engine-specific work: Native scripts preserve database control but do not provide a portable migration language.
- Release discipline required: Script edits are explicitly supported before tagging and release, making that boundary important for stable history.
- No warranty: The license places responsibility for reliability and support on the adopting organization.
Alternatives
Consider Atlas when a freemium product with a free trial, API access, and an open-core model is a better fit. Choose Bytebase Enterprise for a web-oriented, self-hosted or API platform with a free Community tier for up to 20 users and 10 database instances, or paid per-user Pro access.
Skeema suits teams focused on MySQL-compatible schema tooling with a free Community plan and a paid Plus tier. Goose is another free, open-source migration option across API, desktop, and self-hosted environments.
pgroll is appropriate when PostgreSQL 14 or later and a single cross-platform binary match your deployment. Refinery offers a free MIT-licensed SQL toolkit with database drivers selected as features. golang-migrate is a free open-source alternative with no paid plans or stated usage limits.
For broader discovery, browse Database Migration Tools or Database Testing Tools.
Verdict
Choose Sqitch if your team wants a free, framework-independent way to manage native SQL changes with dependencies, integrity checks, verification, and rollback across many database engines.
The verdict
Sqitch offers a script-based approach to database change management with dependency tracking, verification, and rollback. Teams should account for the required database client and connector libraries and review the license condition before adopting it.
Questions people ask
Is Sqitch free?
Yes. Sqitch is open-source software, and the listed Sqitch plan is free.
Which platforms does Sqitch support?
It supports Linux, macOS, Windows, and self-hosted deployments.
Which databases are supported?
The manual lists PostgreSQL, YugabyteDB, CockroachDB, SQLite, MySQL, MariaDB, Oracle, Firebird, Vertica, Exasol, Snowflake, and ClickHouse.
Does Sqitch support rollback?
Yes. It provides commands to revert database changes and verify deployed changes.
What does Sqitch require at runtime?
It requires the selected database engine’s native command-line client and connector libraries.
Is Sqitch open source?
Yes. The manual grants rights to use, modify, publish, distribute, sublicense, and sell the software under its stated condition.
What the maker publishes
- Community support
- Users can seek help through GitHub Discussions, the Sqitch Users mail list, and Stack Overflow; filing issues requires a GitHub account. source
- Community support
- The community offers GitHub Discussions, a users mailing list, Stack Overflow questions tagged sqitch, and a GitHub issue tracker for bugs and feature requests. source
- Credential security
- Sqitch intentionally has no command-line password option because command-line passwords can be recorded in shell history or exposed to other users. source
- Database prerequisites
- Sqitch requires a database-native command-line client and connector libraries to execute change scripts and connect to the database. source
- Database support
- The manual lists support for PostgreSQL, YugabyteDB, CockroachDB, SQLite, MySQL, MariaDB, Oracle, Firebird, Vertica, Exasol, Snowflake, and ClickHouse. source
- Database support
- Sqitch supports PostgreSQL, YugabyteDB, CockroachDB, SQLite, MySQL, MariaDB, Oracle, Firebird, Vertica, Exasol, Snowflake, and ClickHouse. source
- Dependencies
- Changes can declare dependencies on other changes, including changes from other Sqitch projects, to determine execution order. source
- Dependencies
- Changes can declare dependencies on other changes, including changes in other Sqitch projects, to determine execution order. source
- Deployment and verification
- Sqitch can deploy and revert database changes, report deployment status and history, and run optional verification scripts during deployment. source
- Deployment integrity
- Sqitch uses a plan file and a Merkle tree pattern to ensure deployment integrity; change names do not need to be numbered. source
- Deployment integrity
- Sqitch uses a plan file and a Merkle tree pattern to manage changes and dependencies and ensure deployment integrity. source
- Framework independence
- Sqitch is a standalone system that is not tied to a framework, ORM, database engine, or development environment. source
- Framework independent
- Sqitch is a standalone system not tied to a framework, ORM, or platform. source
- Installation
- The project provides source and Docker installation options, Linux distribution packages, a macOS Homebrew installation, and Windows installation instructions. source
- Install options
- The download page lists source, Docker, Red Hat, Ubuntu/Debian, macOS Homebrew, and Windows Strawberry Perl installation options. source
- Iterative development
- Before a project is tagged and released, deployment scripts can be modified after being committed to version control. source
- Iterative development
- Deployment scripts can be modified during development until the project is tagged and released. source
- License
- The manual grants permission to use, modify, publish, distribute, sublicense, and sell the software subject to its stated condition, and provides it without warranty. source
- License and warranty
- The manual grants software use and distribution rights free of charge and states that the software is provided without warranty. source
- Maintainer
- The manual names David E. Wheeler as the author. source
- Native scripts
- Database changes are implemented as scripts native to the selected database engine. source
- Native scripts
- Database changes are implemented as scripts native to the selected database engine. source
- Purpose
- Sqitch is a database change management application. source
- Purpose
- Sqitch is a database change management application for framework-free development and dependable deployment. source
Checked against the maker's pages on 9 Oct 2026.