Free, state-based schema management for SQL Server, PostgreSQL, MySQL, and MariaDB — vs imperative, version-numbered migration scripts.
SchemaSmith uses a state-based approach: you declare the end state and the tool generates the changes. Flyway is built around an imperative approach: you write sequential migration scripts that apply in order, and Flyway Enterprise adds state-based deployments from a schema model. SchemaSmith is free under a source-available license — unlimited seats, schemas, and servers, at any team size or infrastructure scale. Flyway offers a free Community edition, which Redgate positions for individual developers and education, and an Enterprise edition, licensed per user and quoted by sales.
How the tools differ in approach, features, and developer experience.
| Aspect | SchemaSmith | Flyway |
|---|---|---|
| Approach | State-based: declare end state, tool generates the changes | Imperative: numbered SQL migration scripts applied in order. Enterprise adds state-based deployments from a schema model (SQL Server, Oracle, PostgreSQL, MySQL) |
| Drift Detection | Built-in (compares live database to declared state on every run) | Enterprise: check -drift compares the target to a snapshot and can stop a deployment. Community: not included |
| Environment Sync | Any environment converges to the declared state in one run | Replay every migration in order from baseline, or (Enterprise) deploy from the schema model |
| Rollback | Re-deploy prior release state; data preservation via migration scripts* | Enterprise: undo scripts, generated alongside each versioned migration. Community: no undo |
| Merge Conflicts | JSON table definitions merge cleanly in source control | Migration-script ordering conflicts on parallel branches |
| CI/CD Model | Idempotent — same result whether run once or ten times | Order-dependent — must track applied migrations |
| New Environment Setup | Apply current declared state directly | Replay every migration from V1 forward, or (Enterprise) deploy from the schema model |
| Reference Data | Declarative DataDelivery blocks; two-pass FK-aware loader |
Enterprise: static data versioning (SQL Server, Oracle, PostgreSQL, MySQL, Databricks). Community: hand-written INSERT / MERGE scripts in migrations |
| Failed Deployment Recovery | Checkpoint & resume (--ResumeQuench); skips completed work on retry |
Restart from the failed migration; manual cleanup if partial |
| Conditional Deployment | ShouldApplyExpression — one file applies per database, env, or version |
Per-environment migration files or scripted branching |
| Platform Coverage | SQL Server, PostgreSQL, MySQL, MariaDB (platform-specific schema definitions) | 60+ database engines |
| Licensing | Free under SSCL v2.0 (source-available); unlimited seats & schemas | Community (free, limited features) or Enterprise (per user, contact sales) |
*SchemaQuench rolls back schema by re-applying the prior release’s declared state. 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 axis competitors typically gate behind paid tiers.
How the two tools differ on cost, license terms, and what changes as you scale.
| Aspect | SchemaSmith | Flyway |
|---|---|---|
| License | SSCL v2.0 (source-available) | Apache 2.0 (Community) / proprietary commercial (Enterprise) |
| Cost | $0/year — free for any purpose, any organization, any scale | Community: free. Enterprise: contact sales. |
| Seat Model | Unlimited users, no per-seat charge | Enterprise is licensed per user: everyone who contributes database changes to a pipeline needs a license |
| Schema / Instance Caps | None — deploy to as many databases, replicas, or regions as you need | None on Enterprise — any number of databases can be in the pipeline at no extra license cost |
| Cost as You Scale | Stays at $0/year regardless of team size, replica count, or region count | Increases with the number of people contributing changes |
Flyway publishes its current edition matrix at red-gate.com/products/flyway/editions. We deliberately do not quote competitor prices on this page because vendor pricing changes and contact-sales tiers are not public.
SchemaSmith’s cost stays at $0/year whether one developer contributes changes or fifty do. There is no per-user license, no schema cap, no edition to upgrade to. The same free CLI deploys to dev, staging, and production at any team size, on any number of databases.
Switching from Flyway to SchemaSmith does not require rewriting your migration history. Extract current state once, review the captured package, and start managing future changes declaratively.
Your existing Flyway migration 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.
Migrate from Flyway's numbered scripts to SchemaSmith's declarative JSON, then deploy idempotently on every run.
Start the Flyway 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