Free, state-based schema management for SQL Server, PostgreSQL, MySQL, and MariaDB — vs XML/YAML changelog-driven migrations.
SchemaSmith uses a state-based approach: you declare the end state in JSON and the tool generates the changes. Liquibase uses a changelog-driven approach: you author changesets in XML, YAML, or JSON that apply in order. SchemaSmith is free under a source-available license — unlimited seats, schemas, and servers, at any team size, application count, or database-type count. Liquibase Community is free and, from version 5.0, source-available under the Functional Source License (FSL); Liquibase Secure is paid (Starter, Team, Business, and Enterprise plans, all quoted by sales), and each plan caps database types and database targets.
How the tools differ in approach, features, and developer experience.
| Aspect | SchemaSmith | Liquibase |
|---|---|---|
| Approach | State-based: declare end state, tool generates the changes | Changelog-driven: changesets applied in order |
| Source Format | JSON template files (one per table, plus indexed and materialized views) and SQL scripts (one per procedure, function, trigger, or ordinary view) | XML / YAML / JSON / formatted SQL changelogs |
| Drift Detection | Built-in — compares live database to declared state on every run | Community's diff compares two databases; the drift report requires Liquibase Secure (Team plan and above) |
| Environment Sync | Any environment converges to the declared state in one run | Apply every changeset in order from baseline |
| Rollback | Re-deploy prior release state — views, procedures, and functions restore from that release’s package* | Automatic for many change types; hand-written for the rest, including every formatted SQL changelog |
| Merge Conflicts | JSON table definitions merge cleanly in source control | Changelog ordering / changeset-ID conflicts on parallel branches |
| CI/CD Model | Idempotent — same result whether run once or ten times | Order-dependent — tracks applied changesets in DATABASECHANGELOG |
| Reference Data | Declarative DataDelivery blocks; two-pass FK-aware loader |
loadData, insert, and sqlFile changesets |
| Failed Deployment Recovery | Checkpoint & resume (--ResumeQuench); skips completed work on retry |
Restart from the failed changeset; partial-state cleanup is manual |
| Conditional Deployment | ShouldApplyExpression — one file applies per database, env, or version |
Liquibase contexts and labels on changesets |
| Platform Coverage | SQL Server, PostgreSQL, MySQL, MariaDB (platform-specific schema definitions) | 60+ databases via JDBC drivers |
| Licensing | Free under SSCL v2.0 (source-available); unlimited seats & schemas | Community (free; FSL-1.1-ALv2 from 5.0, Apache 2.0 for earlier releases) or Liquibase Secure (paid, four plans, quoted by sales) |
*SchemaQuench rolls back schema by re-applying the prior release’s declared state — including stored procedures, views, and functions, which restore from that release’s package. Data preservation (e.g., retaining values from a dropped column) is handled with user-written migration scripts inside the same package.
Checkpoint & resume, two-pass FK-aware data delivery, ShouldApplyExpression, secondary servers for SQL Server Availability Groups, and custom script folders all ship in the free CLI — the same production-resilience and observability axes Liquibase Secure plans charge for.
Rollback capabilities differ significantly between state-based and changelog-driven approaches.
With SchemaSmith, rolling back a stored procedure restores the prior version from that release’s SQL script automatically: re-deploy the prior release’s package, and its scripts put the earlier version back. With Liquibase, you maintain previous versions inside custom rollback blocks alongside each changeset, or accept that rollback will not restore stored logic to its prior state.
How the two tools differ on cost, license terms, and what changes as you scale.
| Aspect | SchemaSmith | Liquibase |
|---|---|---|
| License | SSCL v2.0 (source-available) | FSL-1.1-ALv2 (Community, from 5.0; earlier releases Apache 2.0) / proprietary commercial (Secure) |
| Cost | $0/year — free for any purpose, any organization, any scale | Community: free. Secure: contact sales for pricing. |
| Plans / Caps | One edition; no database-target, database-type, or seat caps | Liquibase Secure has four plans (Starter, Team, Business, Enterprise), each capped on database types and database targets; every plan requires a Professional Services package |
| Cost as You Scale | Stays at $0/year regardless of applications, database types, replicas, or regions | Going past a plan's database-type or target cap means buying added capacity or moving up a plan |
Liquibase publishes its current plan matrix at liquibase.com/pricing. We deliberately do not quote competitor prices on this page because vendor pricing changes and contact-sales pricing is not public.
SchemaSmith’s cost stays at $0/year regardless of how many applications, database types, replicas, or regions you deploy to. There is no per-user license, no database-target cap, no database-type cap, no higher plan to move up to. The same free CLI deploys to dev, staging, and production at any team size, on any number of databases.
Switching from Liquibase to SchemaSmith does not require rewriting your changelog history. Extract current state once, review the captured package, and start managing future changes declaratively.
Your existing Liquibase changelog history stays in place as a record of how the database got here. SchemaSmith takes over from the current state forward.
Pricing and feature data last verified November 2026. Competitor information may change.
Switch from XML/YAML changelogs to JSON state files and deploy idempotently, with no changeset ordering to wrangle.
Start the Liquibase labEverything from here is organized by database. Choose yours below and keep going.
Free schema-as-code for SQL Server, PostgreSQL, MySQL, and MariaDB.
The source is on GitHub for anyone to read.
Get Started on GitHub