Skeema

Skeema is a declarative SQL-based utility for managing MySQL and MariaDB schema changes expressed as CREATE statements in a repository. It generates SQL DDL from schema files and provides diff, lint, push, and pull commands. Configurable lint rules flag unsafe changes, and Skeema checks generated ALTER TABLE statements in a workspace before proceeding. For online schema changes, it supports native database alterations and external tools such as pt-online-schema-change and gh-ost, with execution configurable by environment and table size. Schema directories can map to multiple database servers or schemas, and the tool can detect drift across shards. The site lists support for MySQL 5.5–9.7, MariaDB 10.1–12.3, and Percona Server; AWS Aurora MySQL 5.7–8.4 is listed for Premium. Skeema Cloud Linter can provide automatic diff and lint output for relevant GitHub commits. All editions can use SSL/TLS, while Premium adds client certificates, CA verification options, and SSH tunnels. Community is free; paid plans start at $124 per month.

Skeema focuses on repository-driven schema changes and includes checks for unsafe alterations. The free Community edition is a starting point, while paid plans add broader platform, sharding, and support options.

It suits teams managing MySQL or MariaDB schemas through repository-based SQL changes. Community is described as free open-source software, while Premium Plus is positioned for smaller teams and Max for larger organizations.

Skeema is a SQL schema tool for teams that keep MySQL or MariaDB definitions in a repository. It suits developers who want to review database changes alongside code and control how those changes reach servers. Its deployment checks and shard support are strong; its object limits and lack of rollback support narrow the fit.

Overview

Skeema applies repository CREATE statements to MySQL and MariaDB tables and routines. Its diff, lint, push, and pull commands take a schema change from comparison through deployment, making it a practical choice for teams that want a repeatable, SQL-based workflow. Schema diff, CI/CD automation, drift detection, and a self-hosted option support that approach.

Configurable lint rules flag unsafe changes, and Skeema verifies generated ALTER TABLE statements in a workspace before proceeding. For online changes, teams can use native database alterations or tools such as pt-online-schema-change and gh-ost, with execution chosen by environment and table size. Those controls help teams manage deployment behavior, but Skeema does not provide rollback support.

Key features

Schema checks and online alterations

The diff and lint commands let teams inspect proposed changes before pushing them. Workspace verification adds a check on generated ALTER statements, while configurable online-change behavior lets teams account for environment and table size. Skeema supports MySQL 5.5–9.7, MariaDB 10.1–12.3, and Percona Server; AWS Aurora MySQL 5.7–8.4 support is limited to Premium. Teams using other database systems should look elsewhere.

Sharding and GitHub workflow

Skeema can map a schema directory to multiple servers or schemas and detect drift across shards. Plus caps sharding at 10 shards per directory, while Max allows unlimited sharding, so larger deployments may need the higher-priced plan. The optional Cloud Linter add-on provides automatic diff and lint output for Skeema commits across a GitHub organization and supports a pull-request workflow through cloud-based CI.

Security and scope

All editions support SSL/TLS connections. Premium adds client certificates, CA verification options, and SSH tunnels. Skeema manages schema objects, not database users, privilege grants, roles, or global variables, and MariaDB sequences are not supported. Teams that need those objects managed in the same workflow will need another solution for that work.

Pricing

Community is free and open source under Apache 2.0. It covers tables, stored procedures, and functions, includes 18 linter checks, and runs on Linux and macOS. It is a sensible starting point for users who need those objects on supported systems, but it excludes Windows and the broader object set in paid plans.

Plus costs $124 a month, billed at $124/month or $1238/year. It adds views, triggers, events, and seed data to tables and routines; supports Linux, macOS, and Windows; and includes sharding up to 10 shards per directory and public support. It fits smaller teams that need broader schema coverage or Windows support.

Max costs $499 a month, billed at $499/month or $4988/year. It includes the same object coverage and operating systems as Plus, unlimited sharding, and private email technical support. Larger organizations with extensive shard deployments or a need for private support have the clearest reason to pay for it.

Skeema Cloud Linter is an optional SaaS add-on at $649 a year. It covers an entire GitHub organization with automatic diff and lint for Skeema commits. Public technical support is available to all CLI users through GitHub issues; private technical support is included with Max. No free trial is offered in these plan terms.

Platforms

Community supports Linux and macOS. Plus and Max add Windows. Skeema is self-hosted CLI software, so teams choosing it should be comfortable running the tool in their own environment; the Cloud Linter is a separate SaaS add-on.

Who it's for

Skeema is best for MySQL and MariaDB teams that keep schema definitions in version control and want linting, review, and controlled deployment in one SQL-based workflow. Community suits users whose needs are limited to its supported objects and Linux or macOS. Plus targets startups and smaller teams needing broader object coverage, Windows, or modest sharding; Max is aimed at larger organizations that need unlimited sharding or private support.

It is a weaker fit for teams that need rollback, manage database-level permissions and global settings as part of schema changes, or rely on MariaDB sequences. Its database focus also makes it unsuitable as a general migration tool across unrelated database systems.

Pros and cons

• Pros: Diff, lint, and workspace verification provide several checks before generated alterations proceed.
• Pros: Native and external online-change options can be configured around the environment and table size.
• Pros: Shard mapping and drift detection help teams track schema consistency across servers.
• Cons: There is no rollback support, so teams need another way to handle reversals.
• Cons: Community excludes Windows and several schema object types included in paid plans.
• Cons: Users, grants, roles, global variables, and MariaDB sequences fall outside its supported scope.

Alternatives

Database Migration Tools and Database Schema Comparison Tools are useful starting points for comparing tools by category. Consider Doctrine Migrations if you want a free, MIT-licensed PHP library installed with Composer or as a PHAR. Sqitch is another free option, with a license permitting copying, modification, distribution, and sale.

Choose sqlx-cli if its migrations and offline query metadata match your database workflow. Atlas is a freemium, open-core option with an Apache 2.0 core engine and paid advanced features. Bytebase Enterprise may suit teams looking for a web-based or self-hosted tool with a free Community plan for up to 20 users and 10 database instances.

db-migrate is a free MIT-licensed option that officially supports Node.js 24 or newer, with database drivers installed separately. dbmate is a free open-source migration tool with no paid SaaS upsell stated. FluentMigrator is a free Apache-2.0 framework distributed through NuGet, with provider packages selected separately.

Verdict

Choose Skeema if your team works primarily with MySQL or MariaDB, keeps schema definitions in a repository, and values configurable checks and shard-aware deployment. Its strongest case is the combination of reviewable SQL changes, ALTER verification, and online-change controls. Look elsewhere if rollback, broader database coverage, or management of permissions and global settings is essential.