SchemaSmith vs Atlas

Free, declarative schema management in JSON across SQL Server, PostgreSQL, MySQL, and MariaDB — vs HCL/Terraform-style declarations with usage-based cloud pricing.

Chaos vs Precision: Product Comparisons

Quick Summary

SchemaSmith and Atlas both take a declarative approach to schema management. They differ on definition language, pricing model, and how each one is licensed. SchemaSmith uses JSON metadata files and is free under SSCL v2.0, with unlimited seats, projects, and databases at any scale. Atlas uses HCL, a Terraform-like syntax, and integrates deeply with application ORMs. The standard Atlas CLI is free to use under the Atlas MSA, and its free Starter plan covers MySQL, MariaDB, PostgreSQL, and SQLite. Atlas Pro adds fees per developer, per CI/CD project, and per database, and those fees grow with your infrastructure.

Technical Comparison

How the tools differ in approach, features, and developer experience.

Aspect SchemaSmith Atlas
Approach Declarative state-based: JSON template files define the end state Declarative: HCL or SQL defines the desired schema
Definition Language JSON template files (one per table, plus indexed and materialized views) and SQL scripts (one per procedure, function, trigger, or ordinary view) HCL (Terraform-like syntax) or SQL
Workflow Philosophy Database-first — schema is the source of truth, independent of application code Code-first via ORM integrations (GORM, Ent, SQLAlchemy, Django, Hibernate, EF Core, and others)
Drift Detection Built-in — compares live database to declared state on every run Atlas Pro (drift detection and monitoring); not in the free Starter plan
Environment Sync Any environment converges to the declared state in one run Declarative migrations applied via Atlas CLI
Rollback Re-deploy prior release state — views, procedures, and functions restore from that release’s package* atlas migrate down computes the reversal from the database's current state (not in the Apache 2.0 Community Edition)
CI/CD Model Idempotent — same result whether run once or ten times; built into the free CLI Atlas Cloud CI/CD or self-hosted CLI; Starter has basic CI/CD integrations, automated CI/CD needs Atlas Pro
Reference Data Declarative DataDelivery blocks; two-pass FK-aware loader (DataTongs) Atlas Pro: declarative data blocks for lookup and seed data (since v1.1). Starter: scripts you write
Failed Deployment Recovery Checkpoint & resume (--ResumeQuench); skips completed work on retry Re-run; partial-state cleanup is the deployer’s responsibility
Conditional Deployment ShouldApplyExpression — one file applies per database, env, or version Conditional logic in HCL or migration scripts
SQL Server Availability Groups Target:SecondaryServers — primary plus secondaries quenched in parallel Apply per server; orchestration is the deployer’s problem
Database Support SQL Server, PostgreSQL, MySQL, MariaDB (platform-specific schema definitions) Starter: PostgreSQL, MySQL, MariaDB, SQLite. Atlas Pro adds SQL Server, CockroachDB, Redshift, ClickHouse, and more
Licensing Free under SSCL v2.0 (source-available); unlimited seats, projects, and databases Standard CLI free to use under the Atlas MSA (a reduced Community Edition is Apache 2.0); Atlas Pro is paid, per developer, per CI/CD project, and per database

*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.

Production-resilience features, free

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 — no Pro tier required for CI/CD, drift detection, or production-grade orchestration.

Choose SchemaSmith when...

  • You prefer JSON files in source control over a new domain-specific language to learn
  • Your team includes DBAs who want to manage schema independently of application code and ORM frameworks
  • You want declarative reference-data delivery (DataDelivery + DataTongs) alongside schema without a paid plan
  • You need built-in CI/CD-friendly drift detection without a paid plan or cloud dependency
  • You need to resume a failed deployment without re-running everything that already succeeded
  • You need secondary-server support for SQL Server Availability Groups
  • You want one license — free, source-available, no per-developer or per-database fees — that does not change as the team or footprint grows

Choose Atlas when...

  • You prefer HCL syntax and want a Terraform-like infrastructure-as-code workflow for databases
  • You are deeply invested in ORM-driven schema generation (GORM, Ent, SQLAlchemy, Django, Hibernate, and others) and want migrations derived from the application model
  • You target a database SchemaSmith does not yet cover (CockroachDB, Redshift, ClickHouse, SQLite, etc.)
  • You want a cloud-hosted web UI for schema visualization and team collaboration
  • You prefer a managed CI/CD service with audit trails and governance built into the platform
  • You want declarative seed data, drift monitoring, and broad engine coverage in one paid plan (Atlas Pro)

Pricing & Licensing

How the two tools differ on cost, license terms, and what changes as you scale.

Aspect SchemaSmith Atlas
License SSCL v2.0 (source-available) Atlas MSA (standard CLI, free to use) or Apache 2.0 (reduced Community Edition) / proprietary commercial (Pro & Cloud)
Cost $0/year — free for any purpose, any organization, any scale As of November 2026: Atlas Starter: free. Atlas Pro: $9/mo per developer + $59/mo per CI/CD project (2 target databases included) + $39/mo per additional target database; schema monitoring $39/mo per monitored database. Atlas Enterprise: custom.
Free-Tier Coverage There is no paid plan; the free CLI is the full CLI on every supported engine Starter covers MySQL, MariaDB, PostgreSQL, and SQLite with basic database features; views, triggers, functions, procedures, and SQL Server need Atlas Pro
Seat Model Unlimited users, no per-seat charge Atlas Pro pricing scales with developer count
CI/CD & Drift Detection Included in the free CLI Atlas Starter has basic CI/CD integrations and no drift detection; Atlas Pro adds automated CI/CD at $59/mo per CI/CD project (2 target databases included) and drift detection
Cost as You Scale Stays at $0/year regardless of team size, CI/CD project count, or database count Compounds across three axes: developers, CI/CD projects, and databases (extra targets and monitored databases)

Atlas publishes its current plan matrix at atlasgo.io/pricing. Pricing components quoted above are from the public Pro pricing page as of November 2026; check the vendor site for current rates.

Cost growth pattern

SchemaSmith stays $0/year regardless of team size, CI/CD project count, or database inventory. Atlas Pro adds fees along three axes: per developer, per CI/CD project, and per additional target or monitored database, at the published Atlas Pro rates. Add a developer, add a CI/CD project, add a database: each axis increases the bill independently. Pick the model that matches how you expect to scale; run your team’s expected numbers against the published rates rather than a single sample point.

Migrating from Atlas

Switching from Atlas to SchemaSmith does not require rewriting your migration history. Extract current state once, review the captured package, and start managing future changes declaratively.

  1. Extract current state with SchemaTongs. Point it at a representative database and let it capture tables and indexed or materialized views as JSON template files, and stored procedures, functions, ordinary views, and triggers as SQL scripts.
  2. Review the captured package. The package becomes the new source of truth — commit it to source control alongside the rest of your repo, replacing the HCL or ORM-generated files in their previous role.
  3. Deploy with SchemaQuench. Future schema changes are edits to the package: a table change is an edit to its JSON, and a stored procedure change is an edit to its SQL script. SchemaQuench generates and applies the DDL on every run, idempotently.

Your existing Atlas history (HCL, migrations, or ORM-generated artifacts) 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.

Go deeper in the course

Extract your current schema into files and manage forward declaratively, instead of porting migration history.

Start the migration track

Next Steps by Platform

Everything from here is organized by database. Choose yours below and keep going.

Shape. Strengthen. Succeed.

Free schema-as-code for SQL Server, PostgreSQL, MySQL, and MariaDB.

The source is on GitHub for anyone to read.

Get Started on GitHub