#106106th of 204 in Backends, databases and hosting

goose

Database schema migration tool for Go, as CLI and library

Stars
11.7k
License
custom license
Last commit
Nov 2026
Last release
Nov 2026
Language
Go
Stars, last 29 weeks+1,214
25 Apr 2026: 10,493 stars2 May 2026: 10,532 stars9 May 2026: 10,561 stars16 May 2026: 10,602 stars23 May 2026: 10,650 stars30 May 2026: 10,706 stars6 Jun 2026: 10,772 stars13 Jun 2026: 10,814 stars20 Jun 2026: 10,852 stars27 Jun 2026: 10,889 stars4 Jul 2026: 10,915 stars11 Jul 2026: 11,064 stars18 Jul 2026: 11,139 stars25 Jul 2026: 11,181 stars1 Aug 2026: 11,222 stars8 Aug 2026: 11,266 stars15 Aug 2026: 11,294 stars22 Aug 2026: 11,320 stars29 Aug 2026: 11,361 stars5 Sept 2026: 11,395 stars12 Sept 2026: 11,436 stars19 Sept 2026: 11,466 stars26 Sept 2026: 11,493 stars3 Oct 2026: 11,520 stars10 Oct 2026: 11,558 stars17 Oct 2026: 11,594 stars24 Oct 2026: 11,619 stars31 Oct 2026: 11,647 stars7 Nov 2026: 11,678 stars14 Nov 2026: 11,707 stars

10,493 on 25 Apr 202611,707 on 14 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

Goose applies versioned schema changes written as SQL files or Go functions, tracking state in a migrations table (default goose_db_version). It runs as a CLI or is imported as a Go library, with commands such as up, down, redo, status, fix and validate. Drivers include Postgres, MySQL, SQLite, ClickHouse, MSSQL, Spanner, YDB and others.

Who it is for: Go and backend developers managing database schema migrations

Strengths

  • Supports SQL and Go migrations, plus migrations embedded in the binary via go:embed
  • Many drivers: Postgres, MySQL, SQLite, Spanner, MSSQL, ClickHouse, YDB, Redshift, TiDB
  • Build tags (e.g. no_postgres) strip unused drivers for a smaller binary
  • Out-of-order migrations, env var substitution in SQL, and a fix command for sequential numbering

Weaknesses

  • Go migrations require building your own goose binary; the stock CLI runs SQL only
  • Container image has no shell and supports .sql migrations only
  • ClickHouse is only fully supported in some deployment modes
  • MySQL needs parseTime and multiStatements enabled for status and multi-statement files

What it needs

  • no GPU
  • Docker
  • Needs A supported database (Postgres, MySQL, SQLite, etc.)

What changed

From the release notes. No flag means the note does not say so, not that the upgrade is safe.

Known problems

Reported, then fixed by a linked change

Titles are the reporters' own words, taken from the project's GitHub issues and ranked by reactions. We have not tried to reproduce any of them.

Also in Backends, databases and hosting

See all 204
Also in Backends, databases and hosting
RankProjectScore
1bunJavaScript and TypeScript runtime with bundler, test runner and package manager96.7k starscustom license94 out of 100
2coolifySelf-hosted Heroku and Vercel alternative that deploys apps and databases over SSH66.2k starsApache-2.093 out of 100
3strapiHeadless CMS that generates REST and GraphQL APIs from content models Live demo ↗ (opens in a new tab)73.5k starscustom license92 out of 100
#4traefikHTTP reverse proxy and load balancer that auto-discovers routes from orchestrators65.6k starsMIT92 out of 100
#5appwriteBackend with auth, databases, storage, functions and an MCP server for agents Live demo ↗ (opens in a new tab)58.2k stars+653 (+1.1%) in 30 daysBSD-3-Clause92 out of 100