Which local SQLite schema tool should you use before deployment?

Choose dbmate for reviewed SQL files with a written undo, narrowly ahead of goose. Atlas scores higher, with unresolved operator details and free undo access; sqlite-schema-diff also generates rebuilds.

PRACTICAL PICKSPreferredPickOur Preferred PickReviewed SQL files with a written undo$0

dbmate

Each migration file carries an up and a down section, runs in a transaction, and is recorded by version. A CI status check and a schema dump help review before deployment.

Narrow recommendation: 4.05 versus goose’s 4.03. Atlas scores 4.15, but its contracting entity’s address and free undo access remain unconfirmed. You write dbmate’s rebuild yourself.

Why dbmate is our Pick
Newcomer assessment

No Rising Star selected

sqlite-schema-diff fits the job and targets Windows and macOS, but its first public release date could not be established. Other researched newcomers did not provide a complete standalone migration workflow.

Making a column NOT NULL replaces existing NULLs with empty values; inspect the plan and keep a separate backup.

Who is this article for? Developers checking a local SQLite schema change on a disposable copy before deployment.

About 23 min read

What Preferred Pick, Rising Star and Ready to Rock mean

The quick list

Start with dbmate for SQL files reviewed alongside their undo. Choose goose for stricter ordering, or compare Atlas and sqlite-schema-diff for generated rebuilds.

dbmate and goose are free and MIT-licensed; sqlite-schema-diff is free and Apache-2.0-licensed, checked November 8, 2026. Atlas Starter is free under Ariga’s own terms; Pro starts at $9 per developer a month and adds linting, triggers and views. Free access to its undo command remains unconfirmed.

The comparison at a glance

Compare where each change comes from, how each tool handles changes SQLite cannot make in place, what you can check before applying, and how you would undo a change.

dbmate is our recommendation for reviewing a SQLite change before deployment, narrowly ahead of goose. Atlas scores higher, with unresolved operator and free undo details; sqlite-schema-diff follows for generated rebuilds. All tools remain selectable.

Tools for planning and applying SQLite schema changes before deployment
FeaturedbmategooseAtlassqlite-schema-diff
Best fitPreferred Pick: SQL migration files you review, each with a written undo sectionThe same file-based job, with out-of-order files refused by default or migrations in GoLetting the tool write SQLite table rebuilds from the schema you wantGenerated table rebuilds with destructive-change prompts and automatic backup
Cost and licence (November 8, 2026)Free; MIT licence; no accountFree; MIT licence; no accountFree Starter tier under Ariga’s own terms; free undo access unconfirmed; Pro from $9 per developer a month for linting, triggers and viewsFree; Apache-2.0 licence; no account
Where the change comes fromOrdered SQL files you write, each with up and down sectionsOrdered SQL or Go files you write; the down section is optionalA desired schema, applied directly or turned into versioned migration filesDesired SQL schema files compared with the local database
Changes SQLite’s ALTER TABLE cannot makeYou write SQLite’s documented rebuild yourself; mark the file transaction:false to switch foreign keys offYou write the rebuild yourself; mark the file NO TRANSACTION to switch foreign keys offGenerates the rebuild (new table, copy rows, drop, rename, indexes); triggers and views are managed only with ProGenerates a table rebuild with a foreign-key check; inspect documented NULL replacement and virtual-table limits
Before applyingThe SQL file itself; status --exit-code for CI; a schema.sql dump to reviewThe SQL file itself; status; validate checks files without running them--dry-run prints the planned SQL and apply asks for approval; destructive-change linting is ProDry run prints SQL; destructive changes are flagged and prompt by default
Undo pathrollback runs the down section you wrotedown, down-to and redo run the down sections you wrotemigrate down plans a reversal from the database’s current state; not in the Apache-licensed Community buildAutomatic backup before apply; no authored down command; keep a separate backup
Main limitNo generated dry run or table rebuild; open report about rollback when a file is missingNo generated dry run or table rebuild; open report about down after out-of-order filesProprietary terms for the standard download; triggers, views and linting need ProNOT NULL changes replace NULLs with empty values; virtual-table changes can lose content; first public release date unknown
Reader reviewsNo reviews yet. Write a reviewNo reviews yet. Write a reviewNo reviews yet. Write a reviewNo reviews yet. Write a review

dbmate and goose run SQL you write; Atlas and sqlite-schema-diff generate SQL from your desired schema. dbmate is our narrow recommendation over goose. Atlas scores higher, but its contracting entity’s address and free undo access remain unconfirmed. sqlite-schema-diff has no migration-history ledger. None of these documents proves your data survives a change; test on a copy and keep a backup. Earlier check record, October 3, 2026.

All features and sources 10 criteria

Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.

Writing and reviewing a change

Show 4 criteria
Writing and reviewing a change
FeaturedbmategooseAtlassqlite-schema-diff
Where the change comes fromOrdered SQL files you write, each with up and down sectionsOrdered SQL or Go files you write; the down section is optionalA desired schema, applied directly or turned into versioned migration filesDesired SQL schema files compared with the local database
Changes SQLite’s ALTER TABLE cannot makeYou write SQLite’s documented rebuild yourself; mark the file transaction:false to switch foreign keys offYou write the rebuild yourself; mark the file NO TRANSACTION to switch foreign keys offGenerates the rebuild (new table, copy rows, drop, rename, indexes); triggers and views are managed only with ProGenerates a table rebuild with a foreign-key check; inspect documented NULL replacement and virtual-table limits
Before applyingThe SQL file itself; status --exit-code for CI; a schema.sql dump to reviewThe SQL file itself; status; validate checks files without running them--dry-run prints the planned SQL and apply asks for approval; destructive-change linting is ProDry run prints SQL; destructive changes are flagged and prompt by default
Guard against dropsNone beyond your review of the fileNone beyond your review of the fileApproval prompt; automatic checks for destructive changes are ProDestructive changes prompt by default; inspect the plan before approval
Sources for writing and reviewing a change

From each project’s documentation, and for Atlas its published source code, checked October 19, 2026; sqlite-schema-diff documentation and release configuration checked November 8, 2026. SQLite’s rebuild procedure.

Failure, undo and record

Show 3 criteria
Failure, undo and record
FeaturedbmategooseAtlassqlite-schema-diff
If a statement failsEach file runs in a transaction by defaultEach file runs in a transaction by defaultEach migration file runs in its own transaction by defaultDocuments transactional apply and a foreign-key check before commit
Undo pathrollback runs the down section you wrotedown, down-to and redo run the down sections you wrotemigrate down plans a reversal from the database’s current state; not in the Apache-licensed Community buildAutomatic backup before apply; no authored down command; keep a separate backup
Record of applied changesVersion numbers in schema_migrations, not file contents; out-of-order files run unless --strictVersion numbers in goose_db_version, not file contents; out-of-order files refused unless -allow-missingA revisions table plus an atlas.sum file that detects edited migration filesDesired-schema files, no migration-history ledger
Sources for failure, undo and record

Documented behavior, not a measured result. An undo section or an old schema cannot recreate rows that a change deleted; keep a separate backup.

Cost, licence and upkeep

Show 3 criteria
Cost, licence and upkeep
FeaturedbmategooseAtlassqlite-schema-diff
Cost and licence (November 8, 2026)Free; MIT licence; no accountFree; MIT licence; no accountFree Starter tier under Ariga’s own terms; free undo access unconfirmed; Pro from $9 per developer a month for linting, triggers and viewsFree; Apache-2.0 licence; no account
Release evidence (dates shown)2.37.0, October 18, 20263.29.0, October 11, 20261.3.0, August 2, 2026 (open-source repository)0.3.5, November 4, 2026; rename fix shipped in 0.3.2 on October 21
Main limitNo generated dry run or table rebuild; open report about rollback when a file is missingNo generated dry run or table rebuild; open report about down after out-of-order filesProprietary terms for the standard download; triggers, views and linting need ProNOT NULL changes replace NULLs with empty values; virtual-table changes can lose content; first public release date unknown
Sources for cost, licence and upkeep

Prices and licences checked November 8, 2026. Release evidence is dated in the row.

What matters when choosing

dbmate is our Preferred Pick for a developer who wants to write, review and, if necessary, undo SQLite schema changes as plain SQL files before deploying them. Every dbmate migration file has an up section and a down section, so the undo is written and reviewed alongside the change. dbmate runs each file in a transaction by default and records the applied version in a schema_migrations table. dbmate status --exit-code lets a CI job fail while migrations are pending, and after each change dbmate rewrites a schema.sql dump that reviewers can read in the pull request. The dump needs SQLite’s own sqlite3 command-line program; without it, dbmate skips the dump without failing. Version 2.37.0 came out on October 18, 2026. dbmate is free, needs no account and is MIT-licensed. dbmate documentation, 2.37.0 release

Our recommendation is narrow: dbmate scores 4.05 out of 5, just ahead of goose at 4.03. Atlas scores 4.15, but its legal documents name different Ariga entities and we have not confirmed an address for the contracting entity; free access to its undo command is also unconfirmed. We retain dbmate as our recommendation. Atlas legal terms, privacy policy, checked November 8, 2026. dbmate’s review aids—the schema dump and CI status check—give it the edge over goose. Choose goose instead if you want out-of-order migrations refused by default, or need some migrations written in Go. Giving the record of applied changes more weight puts goose ahead. goose documentation

Know SQLite’s limit before you choose. Its ALTER TABLE can rename a table, rename a column, add a column and drop a column, and since SQLite 3.53.0 (April 9, 2026) it can set or drop NOT NULL. Other changes, such as changing a column’s type or adding a UNIQUE constraint, a primary key or a foreign key, need what SQLite’s documentation calls the 12-step procedure: switch foreign keys off, start a transaction, create a new table, copy the rows, drop the old table, rename the new one, recreate its indexes, triggers and views, run PRAGMA foreign_key_check, commit, and switch foreign keys back on. Foreign keys must be switched off before the transaction starts, because SQLite ignores that setting inside one. With dbmate or goose you write these steps yourself, in a file marked transaction:false (dbmate) or NO TRANSACTION (goose), with your own BEGIN and COMMIT around the rebuild. Getting this wrong loses data: in September 2025, Zed’s developers reported that table rebuilds run with foreign keys on had repeatedly deleted related rows, including unsaved editor text, through ON DELETE CASCADE. SQLite ALTER TABLE, PRAGMA foreign_keys, Zed’s fix

Choose Atlas if you would rather describe the schema you want and let the tool write that table rebuild, and you accept Ariga’s terms. For changes SQLite cannot make in place, Atlas’s open-source code follows SQLite’s documented procedure: it creates a new table, copies the rows, drops the old table, renames the new one and adds back its indexes. Its free Starter tier covers tables, indexes and constraints, with a dry run and an approval prompt. The standard download is free to use under Ariga’s own terms (the Atlas MSA), not an open-source licence. Triggers, views and automatic checks for destructive changes need Atlas Pro, which costs from $9 per developer a month after a 30-day trial. The Apache-licensed Community build also leaves out migrate down and linting. Check two things before relying on a rebuild. First, a rebuilt table’s triggers: the open-source code we read does not recreate them, and we could not establish whether the free tier keeps them. Second, foreign keys: Atlas switches them off at the start of a rebuild, but its own code notes that this does nothing inside a transaction, and migrate apply wraps each migration file in one by default. Atlas editions, pricing, schema apply, migrate apply, SQLite rebuild code

Disclosure: Practical Picks articles are researched and written with AI, currently Anthropic’s Claude. Atlas publishes a plugin and instructions for Anthropic’s Claude Code. We have no relationship with Ariga or Anthropic over this article, and this Claude link carried no weight in our judgment. Atlas Claude Code instructions

We no longer describe sqlite3def as the established choice for a desired-schema workflow on SQLite. Its dry run and its guard against accidental drops are good. But it does not rebuild tables, and in sqldef’s source code on October 19, 2026, the SQLite path generates nothing when an existing column’s type, NOT NULL setting or default changes. A code comment says that changing a CHECK constraint “requires recreating the table, which is not supported”. The documentation does not mention either gap. If you use it, compare its dry run with the change you meant to make. sqlite3def documentation, generator source

No Rising Star selected. sqlite-schema-diff fits this job and its current release configuration targets Windows and macOS, but we could not establish its first public release date. Its table rebuilds, destructive-change prompts and automatic backup earn it a place in the comparison below. Release history, version 0.3.5 release configuration, checked November 8, 2026.

Back up before any consequential change, whichever tool you use. A down section, an old schema file or a reverse plan cannot recreate rows that a change deleted. The four tools below run on your own machine. This comparison does not rank speed.

dbmate

Preferred Pick · reviewed SQL files with a written undo

$0One MIT-licensed binary, no account

Choose dbmate when each SQLite change should be a SQL file your team reviews, with an undo section written beside it. Our lead over goose is narrow.

Reasons to choose it

  • Up and down sections in every migration file
  • Pending-migration check for CI and a schema dump to review
  • Each file runs in a transaction by default

What to watch

  • You write SQLite’s table rebuild yourself
  • No generated dry run; out-of-order files run unless --strict
  • Open report: rollback when an applied file is missing

dbmate reads ordered SQL files from a migrations folder. Each file has -- migrate:up and -- migrate:down sections; dbmate requires both directives, even if you leave the down section empty. dbmate migrate applies pending files in version order, dbmate rollback runs the most recent file’s down section, and dbmate status lists what is pending. The release binaries include SQLite, so DATABASE_URL="sqlite:db/app.sqlite3" is enough to start. Each file runs in a transaction by default. For SQLite settings that cannot change inside a transaction, such as foreign keys during a table rebuild, mark the file transaction:false and write your own BEGIN and COMMIT. Documentation

For review before deployment, the SQL file is exactly what will run. status --exit-code makes a CI job fail while migrations are pending, and the schema.sql file dbmate rewrites after each change shows reviewers the resulting schema. dbmate does not generate SQL from a desired schema, does not print a dry run and does not flag destructive statements; your review of the file is the safeguard. Two record-keeping limits matter. dbmate stores only the version number of each applied file, not its contents, so roll back before editing an applied file. And by default it applies a pending file with an older version number than files already applied, which can happen when branches merge; add --strict to make that an error. Documentation

Read the full dbmate analysis and sources

Version 2.37.0 (October 18, 2026) fixed three things worth knowing. dbmate no longer prints “Applied” for a migration that then fails, a problem reported in August 2025. Files with several up and down sections now work on SQLite and roll back in reverse order. And the release updates Go and two Go libraries after a maintainer’s govulncheck scan of 2.36.0 returned nine findings; the project did not say whether any of them affected dbmate itself, so upgrade from 2.36.0. One report remains open: when the file for the most recently applied migration is missing, rollback does not stop with an error. The reporter used PostgreSQL and version 2.26.0, but the lesson applies here too: deploy every applied migration file with your application, and check schema_migrations before rolling back. GitHub listed no security advisory for dbmate on October 19, 2026, and the project has no security policy file. 2.37.0 release, Applied-message report, closed October 18, 2026, dependency update, missing-file rollback report

In an earlier hands-on check on October 3, 2026, before we adopted our research-only method, dbmate 2.36.0 applied a small synthetic schema change and kept two invented rows. A deliberately failing migration left neither its earlier table nor a version record behind, although dbmate printed “Applied” before the error, the message 2.37.0 fixes. A down section we wrote then returned the original schema. The table that change dropped was empty, so the check says nothing about recovering deleted data. These observations match dbmate’s documentation; they did not decide the Pick. Earlier check record, October 3, 2026

Used dbmate? Share your experience to help other readers choose.

goose

Also consider · the same job, stricter ordering

$0One MIT-licensed binary, no account

Choose goose when you want out-of-order migrations refused by default, or need some migrations written in Go. It is effectively level with dbmate.

Reasons to choose it

  • Refuses out-of-order migrations unless you allow them
  • down, down-to and redo commands
  • validate checks migration files without running them

What to watch

  • You write SQLite’s table rebuild yourself
  • Down sections are optional, so undo depends on discipline
  • No schema dump and no generated dry run

goose, maintained under the pressly GitHub organization, does the same job as dbmate in nearly the same way. Migrations are SQL files with a -- +goose Up section and an optional -- +goose Down section, or functions written in Go. The release binaries include a SQLite driver (goose sqlite3 ./app.db up). Each file runs in a transaction unless it starts with -- +goose NO TRANSACTION, which you need for a table rebuild that switches foreign keys off. goose records applied versions in a goose_db_version table and offers down, down-to, redo and status, plus validate, which checks migration files without running them. Version 3.29.0 came out on October 11, 2026, and goose is MIT-licensed. Documentation, releases

The main difference is ordering. By default goose raises an error if you try to apply a missing, out-of-order migration, and you must pass -allow-missing to run it. The maintainers recommend timestamps during development and sequential numbers in production, which goose fix converts. That is a safer default than dbmate’s for a team whose branches merge migrations in a different order. An open report says that -allow-missing followed by down does not behave as expected, so roll back carefully after applying out-of-order files. Out-of-order migrations, allow-missing and down report

Read the full goose analysis and sources

goose gives reviewers less than dbmate. It writes no schema dump, prints no dry run, and the down section is optional, so a team has to insist on it. Statements that contain semicolons, such as a SQLite trigger’s body, must be wrapped in -- +goose StatementBegin and -- +goose StatementEnd. Like dbmate, goose stores version numbers, not file contents. GitHub listed no security advisory for goose on October 19, 2026. SQL migration format

Used goose? Share your experience to help other readers choose.

Atlas

Also consider · the tool writes the table rebuild

$0 StarterPro from $9 per developer a month; undo access unconfirmed

Atlas writes SQLite’s table rebuild. Its standard download has proprietary terms, and free undo access remains unconfirmed.

Reasons to choose it

  • Generates SQLite’s documented rebuild for changes ALTER TABLE cannot make
  • Dry run and an approval prompt before applying
  • atlas.sum detects edited migration files

What to watch

  • Standard download is under Ariga’s own terms, not an open-source licence
  • Triggers, views and destructive-change linting need Pro
  • Check that foreign keys are really off during a rebuild

Atlas, made by Ariga, works from the schema you want, written as SQL or in its own HCL format. atlas schema apply compares that schema with the database and applies the difference after you approve the printed plan; --dry-run prints the SQL without running it. Or atlas migrate diff writes the difference as a versioned migration file for review, atlas migrate apply runs pending files, and an atlas.sum file holds a checksum of each migration file, so Atlas reports files that were edited or added in parallel. Planning needs a scratch database, which for SQLite can be in memory (--dev-url "sqlite://dev?mode=memory"). Declarative workflow, versioned workflow, atlas.sum, undo

Its advantage for SQLite is that it writes the table rebuild. For changes SQLite cannot make in place, its open-source code creates a new_ table, copies the rows, drops the old table, renames the new one and adds back the indexes, citing SQLite’s documented procedure. atlas migrate down plans a reversal from the database’s current state rather than running an undo you wrote. Know the gaps before relying on it. The free tier does not manage triggers or views, and the rebuild code we read does not recreate a table’s triggers. The foreign-key setting it adds at the start of a rebuild does nothing inside the transaction that migrate apply opens by default, as Atlas’s own code notes. And it adds no PRAGMA foreign_key_check, so run one yourself. SQLite rebuild code, SQLite’s procedure

Read the full Atlas analysis and sources

Atlas scores 4.15. Its standard download is free under Ariga’s proprietary MSA, while the Apache-2.0 Community build omits migrate down, linting, triggers and views. The MSA and privacy policy name different Ariga entities; the available evidence does not reconcile them. Starter is free, and Pro starts at $9 per developer a month, with separate charges for hosted CI and monitoring. Neither hosted service is needed for this local job. Check the command entitlement before relying on an undo after a trial ends. Editions, pricing, MSA, privacy policy, checked November 8, 2026. The open-source repository’s latest release remains 1.3.0, August 2, 2026; its security page lists no published advisory. Releases, security, checked November 8, 2026.

Used Atlas? Share your experience to help other readers choose.

sqlite-schema-diff

Evaluated · generated rebuilds with a backup

$0Apache-2.0 licence; no account

Choose sqlite-schema-diff for generated SQLite rebuilds, destructive-change prompts and backups, after checking its documented data-conversion limits.

Reasons to choose it

  • Generates table rebuilds and checks foreign keys before commit
  • Dry run and destructive-change prompts
  • Backup before applying; release targets Windows and macOS

What to watch

  • NOT NULL changes replace NULLs with empty values
  • Virtual-table changes can lose content
  • No migration-history ledger; first public release date unknown

MizuchiLabs’ sqlite-schema-diff compares a desired SQL schema with a local SQLite database, previews the SQL and applies the difference. Its documentation describes automatic table rebuilds, a foreign-key check before commit, destructive-change prompts and a backup before applying. Version 0.3.5 was released November 4, 2026; its tagged build configuration targets Linux, Windows and macOS. It is free and Apache-2.0-licensed. Choose it if you want a local desired-schema workflow with generated rebuilds and can review the plan carefully. It scores 3.90 out of 5. Documentation, releases, release configuration, checked November 8, 2026.

The limits matter: changing a column to NOT NULL replaces existing NULLs with empty values, and the documentation warns of content loss when changing virtual tables. Destructive changes prompt by default; inspect the SQL and keep your own backup. There is no migration-history ledger or authored down command; recovery depends on the backup. The rename-detection fix shipped in 0.3.2 on October 21. We could not establish its first public release date from the release history, so it receives no newcomer award. Neither a small user base nor few reviews alone lowers its score. Documentation, earlier releases, checked November 8, 2026.

Used sqlite-schema-diff? Share your experience to help other readers choose.

Which product are we missing?

Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.

Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.

Suggest a product

Opens an email draft with this article attached as a link. Nothing is sent until you send it.

No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.

What people are saying

Practical Picks has no reader reviews for these tools yet. Issue trackers show the problems users run into, not how often they happen. dbmate users reported the misleading “Applied” message (fixed October 18, 2026) and the rollback behavior when a migration file is missing (still open). A goose user reported unexpected down behavior after out-of-order migrations (still open). The only outside reports we found for sqlite-schema-diff are four issues from one user in April 2026, all closed. dbmate report, goose report, sqlite-schema-diff issues

The clearest real-world warning about SQLite table rebuilds comes from outside this comparison. Zed’s developers wrote in September 2025 that rebuilds run with foreign keys on had deleted related rows several times, including the only copy of unsaved editor text; their fix switches foreign keys off during migrations and runs a foreign-key check before each commit. Django’s documentation says its own SQLite rebuild process “generally works well, but it can be slow and occasionally buggy”. Zed’s fix, Django on SQLite

As rough signals of use, on October 19, 2026 dbmate had about 7,500 GitHub stars, goose 11,600, Atlas 8,800, sqldef 3,200 and sqlite-schema-diff 2. Homebrew counted about 11,400 installs of dbmate, 6,400 of goose and 8,800 of Atlas in the previous year. Homebrew’s Atlas package is listed as Apache-2.0, which suggests it is the Community build. These counts are not counts of teams.

How we researched

This is public-source research. For this review we did not install or run any tool, create accounts or contact a maker. No maker supplied access or payment, and our links carry no affiliate tracking. We first compared dbmate, sqlite3def and sqlite-schema-diff on October 3, 2026, including a small hands-on check described below. On October 19, 2026 we rechecked documentation, GitHub release and commit records, issue trackers, security advisories in GitHub and OSV, licences, pricing pages, published source code and Homebrew records, added candidates we had missed, and made the decision again from public evidence.

We wrote this for a developer with a SQLite-backed application who must plan, review, apply and, if needed, undo a schema change on a disposable copy before deploying it. Every option has to work free without an account, run locally through its standard installation and support SQLite. We compare SQLite change handling (25%); review before applying (20%); failure safety and recovery (20%); the record of applied changes (15%); and cost (20%). The ongoing job is compared over three years. dbmate scores 4.05, goose 4.03, Atlas 4.15 and sqlite-schema-diff 3.90. Atlas has the legal-entity and undo-access limits described above. dbmate’s recommendation over goose is narrow.

On November 8, 2026 we checked GitHub’s database-migrations, sqlite-migrations and schema-migrations directories alongside the newcomers found in October. sqlite-schema-diff fits this job and its release configuration targets Windows and macOS, but its first public release date could not be established. choplin/sqlite-schema remains unreleased and only implements an initial create-table workflow. UniSoma/sqlite-migrate is a Clojure library without a published CLI binary; dbconform is a SQLAlchemy library whose current package page could not be read; AIM generates migration files rather than running them; and dobrinov/schema visualizes schema differences rather than applying them. Database migration directory, SQLite migration directory, schema migration directory, checked November 8, 2026.

sqlite3def scores 3.55 and is best limited to simple additions: its dry run and drop guard are useful, but the October 19 source inspection found no generated SQLite change for several existing-column and CHECK changes, and it has no native rollback. sqlite-utils scores 3.73; its table transforms and Python migrations are useful helpers, with recovery through your own backup. Yoyo scores 3.75 and provides SQL files, dependency ordering, transactions and separate rollback files through a Python CLI, but its last release and public source activity are from 2024, so we do not recommend it. sql-migrate scores 3.75 and provides SQL up/down sections, a dry run and transactional application, without dbmate’s schema dump. Yoyo documentation, release history, source activity, sql-migrate, checked November 8, 2026.

Sqitch and SQLx CLI each score 3.83. Sqitch uses dependency plans with separate deploy, revert and verify scripts; it needs Perl and a SQLite client, and you write the rebuild yourself. SQLx CLI runs reversible SQL files independently of a Rust application, with transactional SQLite apply/revert and migration checksums. Its SQLite locking implementation is a no-op; keep migration execution to one process. Sqitch, SQLx CLI, SQLite migration implementation, checked November 8, 2026.

We also considered Flyway Community, Liquibase Community, Alembic, Drizzle Kit, Phinx and refinery. Their local workflows are suitable alternatives, but the documentation available to us does not establish every SQLite rebuild, transaction or history detail needed for a complete score. They remain unscored. Flyway includes its SQLite driver; Liquibase’s licence permits this internal use; Alembic documents SQLite batch rebuilds; Drizzle Kit generates and applies SQL; Phinx is a standalone PHP migration tool; refinery provides SQL migrations and forward repair. golang-migrate’s prebuilt releases lacked SQLite drivers in the October 19 research. Django and Rails require adopting their application frameworks. Prisma’s current migration documentation describes experimental SQLite support; we could not establish its stable standalone SQLite workflow. SQLite’s sqldiff compares databases without a migration ledger or recovery runner. Flyway SQLite, updated November 5, 2026, Liquibase licence, Alembic batch migrations, Drizzle migrations, Phinx, refinery, Prisma migrations, checked November 8, 2026.

In an earlier hands-on check on October 3, 2026, before we adopted our research-only method, we ran dbmate 2.36.0, sqlite3def 3.11.26 and sqlite-schema-diff 0.3.1 on Linux against separate copies of one small synthetic SQLite database. Each applied the same five-part change (a new NOT NULL column with a default, a new index, a new table with a foreign key, and the removal of an old index and an empty table) and kept two invented rows. Each rejected a deliberately failing unique index without leaving it behind. For recovery, dbmate ran a down section we wrote, sqlite3def applied the original schema again, and sqlite-schema-diff’s automatic backup matched the original database when copied to a separate file. The dropped table was empty, and the check included no change to an existing column’s type, NOT NULL setting or constraints, no table rebuild and no triggers. These observations match the tools’ documentation. They did not decide the Pick, and goose, Atlas and Sqitch were not part of the check. Earlier check record, October 3, 2026

ToolPublic sourcesWhat remains uncertain
dbmateREADME and command reference; release records to 2.37.0; issue reports 670 and 671; dependency-update change 857; GitHub security page; Homebrew record.Whether the rollback report reproduces on SQLite; whether the scan findings fixed in 2.37.0 affected dbmate in use.
gooseREADME, command reference and migration format; release records to 3.29.0; issue report 402; GitHub security page; Homebrew record.How the out-of-order and down report behaves on SQLite.
AtlasEditions, pricing, schema apply, migrate apply and undo pages; SQLite rebuild source; release and commit records; Homebrew record.Whether the free tier keeps a rebuilt table’s triggers; whether foreign keys are really off during a rebuild under default settings; whether migrate down stays free.
sqlite-schema-diffDocumentation, releases through 0.3.5, human commits, issue list and Go package record, checked November 8, 2026.First public release date; behavior on your schema, including documented NULL replacement. Windows/macOS targets confirmed in the tagged release configuration.

None of this establishes how any tool behaves on your schema, your data or your deployment. Next substantive review is due December 18, 2026, or sooner if dbmate or goose changes how it records or orders migrations, or new first-release, recovery or pricing evidence becomes available. Found a changed release or behavior? Contact the editors.

Sources and evidence

Sources were checked October 19, 2026 unless another date is given. Prices, licences, newcomer releases and candidate directories were checked November 8, 2026 where cited. Documentation and source code establish intended behavior, not results on your database. Issue reports are attributed experiences, not failure rates.

Licences from each project’s repository: dbmate, goose and sqldef MIT (sqldef’s parser Apache-2.0); Atlas’s open-source code and Community build Apache-2.0, its standard download under the Atlas MSA; sqlite-schema-diff Apache-2.0. OSV listed no advisory for any of these projects’ Go modules on October 19, 2026. This is a researched comparison, not a product review. Method: evidence standard, editorial picks.