Overview

SchemaHero suits teams that want database changes expressed as desired state rather than a hand-maintained sequence of migration files. Its plan-before-apply workflow makes proposed SQL reviewable, though the absence of rollback support is a serious constraint for teams that need a built-in reversal path.

It is an open-source tool under Apache-2.0, delivered as a standalone CLI or an optional Kubernetes Operator. The CLI does not require Kubernetes, so teams can use the same declarative approach in local or CI environments without adopting the operator.

Key features

Plan and apply

Schema definitions in YAML describe columns, primary keys, indexes, foreign keys, defaults and constraints. The plan command compares that target with the current database and outputs SQL without changing the database; apply executes the SQL. This separation gives reviewers a chance to inspect changes before execution. Because SchemaHero calculates changes from current state to declared state, it does not require numbered migration files—a useful fit for teams that prefer a declarative workflow, but a different model from manually curated migration histories.

Safety and change visibility

SchemaHero supports schema diffing and drift detection. Migration policies can flag destructive changes such as dropping a column or table and fail CI checks, helping teams catch risky proposals before they proceed. That is a guardrail, not rollback: SchemaHero does not support rolling changes back, so teams that require a product-provided reversal mechanism should look elsewhere.

Automation and deployment

The project documents GitHub Actions and GitLab CI workflows for planning and applying changes, as well as GitOps integration with Argo CD and Flux. Its Docker image includes the CLI and can run in CI systems that support Docker. The Kubernetes Operator can create Migration resources and wait for approval, with approve and reject workflows; teams not using Kubernetes can stay with the CLI.

Database connections

Supported engines are PostgreSQL, MySQL, CockroachDB, TimescaleDB, Cassandra, SQLite and RQLite. PostgreSQL connections include SSL modes such as require and verify-full. Connection guidance covers AWS RDS, AWS SSM, Google Cloud SQL and HashiCorp Vault, and Kubernetes credentials can be stored in Secrets. These options make the tool relevant across several database and deployment setups, while the supported-engine list remains the boundary of its fit.

Pricing

SchemaHero is free, with no paid plan or seat, quota, or trial terms specified. Its Apache-2.0 license and self-hosted deployment make it an option for teams seeking an open-source migration tool without a software charge; teams should still account for the operational work of running their own CLI or operator.

Platforms

SchemaHero supports Linux, macOS and Windows installations, and is also distributed as a Docker image. It can be self-hosted or used through its web presence. The Kubernetes Operator is optional rather than a prerequisite for the CLI.

Who it's for

SchemaHero is best suited to engineering teams comfortable declaring database structure in YAML and reviewing generated SQL before applying it. CI and GitOps users can put its planning workflow into documented automation, while Kubernetes teams can add approval steps through the operator. It is less suitable for organizations that require built-in rollback support or rely on a database engine outside its supported set.

Pros and cons

Pro: Plan produces SQL without modifying the database, giving teams a clear review point before apply.
Pro: It avoids numbered migration files by deriving changes from the current and declared schemas.
Pro: Destructive-change policies can fail CI checks, and the tool documents CI and GitOps integrations.
Pro: A standalone CLI keeps Kubernetes optional, while the operator adds approval workflows for Kubernetes users.
Con: There is no rollback support, leaving teams without a product-provided way to reverse an applied change.
Con: Its declarative YAML-to-SQL model may not suit teams that want to manage numbered migration files directly.

Alternatives

For a broader comparison, see Database Migration Tools.

Skeema is worth considering if its free Community plan, which includes tables, stored procedures and functions, and 18 linter checks, or its paid Plus plan better matches your needs. Atlas is another freemium, open-core option with an Apache-2.0 core and advanced features available in proprietary form. Liquibase offers a freemium alternative whose Starter plan is tied to up to five applications and one database type, with a professional services package required for onboarding and implementation.

Bytebase Enterprise may suit teams comparing a paid product with a free Community tier capped at 20 users and 10 database instances. Alembic is a free, MIT-licensed open-source alternative. GitHub Accessibility Scanner and FluentMigrator are also free alternatives. Redgate SQL Provision is a paid option with capacity tiers based on production data volume to provision or mask, ranging from 1TB to 100TB.

Verdict

Choose SchemaHero if your team wants a free, open-source declarative workflow that generates inspectable SQL and can fit into CI, GitOps or Kubernetes approval processes. Its lack of rollback support is the clearest reason to choose another tool, especially where reversing an applied migration is a requirement.

	SchemaHero	Umzug
Free plan	No	No
Free trial	No	No
Paid from	—	—
Open source	No	No
Platforms	Linux, macOS, self-hosted, Web, Windows	—
Free plan	Yes	Yes
Rollback support	No	Yes
Schema diff	Yes	—
CI/CD automation	Yes	—
Drift detection	Yes	—
Self-hosted option	Yes	Yes
Migration format	mixed	mixed

SchemaHero vs Umzug

SchemaHero

Umzug