Skeema

Skeema is a SQL-based schema management tool for MySQL and MariaDB. It suits teams that want database structure reviewed and deployed from a repository. Its deployment safeguards and shard awareness are compelling, but the free edition’s platform and object limits can make a paid plan necessary.

Overview

Skeema turns repository schema files into database DDL, with commands to diff, lint, push, and pull changes. That gives development teams a repeatable way to manage schema alongside application code, rather than treating database changes as a separate manual process.

Configurable lint rules flag unsafe changes, and Skeema verifies generated ALTER TABLE statements in a workspace before proceeding. For online changes, it can use database-native alterations or tools such as pt-online-schema-change and gh-ost, with execution configured by environment and table size. These controls help teams shape a deployment workflow around their environment, but they are not a substitute for rollback: Skeema does not support rollback.

Key features

Review and deployment controls

Diff and lint commands support pre-deployment review, while workspace verification checks generated ALTER statements before they are applied. GitHub teams can add Skeema Cloud Linter for automatic diff and lint output on Skeema-related commits and a pull-request workflow through cloud-based CI. That makes the add-on relevant when teams want checks to run during code review; it covers an entire GitHub organization rather than being priced by repository.

Sharding and scope

Skeema can map a schema directory to multiple servers or schemas and detect drift across shards. That is useful for teams maintaining similar structures across a fleet, though shard limits vary by plan. Its scope is focused on schema objects: it does not manage users, grants, roles, or global variables, and MariaDB sequences are not supported.

Pricing

Skeema uses a freemium model, with paid plans from $124/mo. Community costs nothing and includes tables, stored procedures and functions, 18 linter checks, Linux and macOS support, and an Apache 2.0 license. It is a credible starting point for open-source users on those systems, but omits Windows and several object types included in paid tiers.

Plus costs $124 a month, billed $124/month or $1238/year. It adds routines, views, triggers, events, and seed data, runs on Linux, macOS, and Windows, and supports up to 10 shards per directory. Public support is included. This is the practical upgrade for smaller teams that need broader object coverage, Windows, or bounded sharding.

Max costs $499 a month, billed $499/month or $4988/year. It includes the same listed schema-object coverage and platform support as Plus, but removes the shard cap and adds private email technical support. Larger organizations with extensive sharding or a need for private support have a clear reason to pay the premium; teams without those needs may find Plus sufficient.

Skeema Cloud Linter is an optional SaaS add-on at $649 a year, billed $649 USD per year. It covers an entire GitHub organization and automatically produces diff and lint output for Skeema commits. It is most relevant where pull-request CI is part of the review process, rather than for teams that only need the CLI workflow.

Platforms

Community runs on Linux and macOS; Plus and Max add Windows. All editions can use SSL/TLS connections. Premium adds client certificates, CA verification options, and SSH tunnels, giving teams additional connection-security options when those are required. The listed database support includes MySQL 5.5–9.7, MariaDB 10.1–12.3, and Percona Server; AWS Aurora MySQL 5.7–8.4 is supported on Premium.

Who it's for

Skeema is strongest for MySQL and MariaDB teams that want declarative SQL schema changes kept in version control, checked before deployment, and applied across multiple servers or shards. Community suits users who can work within its Linux/macOS and schema-object limits. Startups and smaller teams are the stated audience for Premium Plus, while Max is positioned for larger organizations. It is a poor fit when database access management or rollback is central to the workflow.

Pros and cons

Pros: Diff, lint, workspace verification, and configurable online-change options provide several points of control before schema changes reach a database.

Pros: Drift detection and directory-to-server mapping address the operational burden of keeping sharded schemas aligned.

Pros: Community is free and Apache 2.0 licensed, with public technical support available to CLI users through GitHub issues.

Cons: The free edition is limited to Linux and macOS, tables and routines, and 18 linter checks; broader object coverage and Windows start with Plus.

Cons: Max is required for unlimited sharding and private email support, making those capabilities a substantial step up from Plus.

Cons: No rollback support, user or privilege management, roles, global variables, or MariaDB sequences limits its reach beyond schema deployment.

Alternatives

For a broader comparison, see Database Migration Tools and Database Schema Comparison Tools.

Atlas is worth comparing if you want an open-core tool with a free plan, a free trial, and support across API, Linux, macOS, self-hosted, and Windows environments.

Bytebase Enterprise may suit teams looking for a paid product with a free Community plan, a free trial, and API, self-hosted, and web platforms.

Sqitch is a free database change management application for teams that prefer a cross-platform option with a license permitting modification and redistribution.

Goose is a free, open-source database migration tool for teams looking for a cross-platform alternative.

Redgate SQL Provision is a paid alternative with a free trial and capacity tiers based on production data volume to provision or mask.

sqlx-cli is a free cross-platform option when database management, migrations, and offline query metadata are the priority.

dbmate is a free, open-source migration tool without a stated paid SaaS upsell.

FluentMigrator is a free Apache-2.0 framework distributed through NuGet, with provider packages selected separately.

Verdict

Choose Skeema if your team manages MySQL or MariaDB schemas in Git and needs linting, verified DDL, online-change options, or shard drift detection. The Community plan offers a capable free entry point, but Windows support, broader object coverage, and substantial sharding require paid plans. Look elsewhere if rollback or database user and privilege management is essential.