MariaDB

MariaDB, GPL-only MySQL fork under a foundation, with Galera clustering and native vectors. MariaDB was forked from MySQL 5.1 by its original authors after Oracle acquired Sun, and is stewarded by the MariaDB Foundation with MariaDB plc selling support. It stays broadly wire- and dialect-compatible while diverging where it wants to: bundled Galera synchronous clustering, pluggable storage engines such as ColumnStore and Spider, and native vector search shipped in the community server ahead of MySQL. Built by MariaDB Foundation. Founded 2009. Open source under GPL-2.0.

We track it in 1 comparison, Database engines, so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 4 other tools, and what follows is where it visibly separates from them.

Where it wins.

• Online schema change, Yes, which only 2 of 5 tools here manage.
• Vector search, Native type + ANN index, the best figure of the 5 here.

Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.

Where it gives ground.

• Ops burden, 3, 3rd of 5. SQLite records 1.
• Extension ecosystem, 3, 4th of 5. PostgreSQL records 5.
• Migration tooling, 3, 3rd of 5. PostgreSQL records 5.
• JSON support, Text functions only, 3rd of 5. PostgreSQL records Binary JSONB + indexes.

None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.

Provenance. 26 of 26 tracked fields carry a value for MariaDB, and 20 of those cite a document you can open. Last verified 2026-07-01. Every figure keeps its own provenance, measured by us, claimed by the vendor, inferred, or community-reported, and we would rather print a dash than a guess.

Its nearest neighbour in our data is DuckDB. MariaDB is ahead on Replication (Built-in async + synchronous against None) and PITR (Yes against No). DuckDB takes Ops burden (1 against 3) and GitHub stars (33,000 against 6,000). That pattern repeats across the rest of the roster, see MariaDB alternatives for the other rivals, each compared the same way.

Company

MariaDB Foundation

Founded

2009

Licence

GPL-2.0 (open source)

Fields we track

26 of 26

Last verified

2026-07-01

MySQL without Oracle, and increasingly not just that: Galera clustering in the box and native vector search shipped in the community server before MySQL's did. The cost is a smaller ecosystem and a slow compatibility drift that now genuinely matters when picking drivers and tools.

Online schema change

●Yes1st of 5

Vendor-claimedverified 2026-07-01source

Vector search

Native type + ANN index1st of 5

Vendor-claimedverified 2026-07-01source

Ops burden

33rd of 5

Inferredverified 2026-07-01

Replication

Built-in async + synchronous1st of 5

Vendor-claimedverified 2026-07-01source

PITR

●Yes1st of 5

Vendor-claimedverified 2026-07-01source

Extension ecosystem

34th of 5

Inferredverified 2026-07-01

Migration tooling

33rd of 5

Inferredverified 2026-07-01

Full-text search

Built-in1st of 5

Vendor-claimedverified 2026-07-01source

MariaDB is the right call in these situations, each one drawn from a field we actually record:

• MySQL-shaped workloads where GPL-only licensing or Oracle stewardship is a blocker.
• Synchronous multi-primary clustering without buying anything.
• Vector search inside a MySQL dialect you can self-host.
• Online schema change is your binding constraint. MariaDB records Yes, which only 2 of the 5 tools in the Database engines roster do. We define that field as whether a large table's schema can be changed while writes continue, without a long exclusive lock, using either the engine's own online DDL or well-established shadow-table tooling.
• Vector search is your binding constraint. MariaDB records Native type + ANN index, the best figure in the Database engines roster.

Reach for something else when any of the following is a requirement rather than a nice-to-have:

• Ops burden. MariaDB records 3, 3rd of 5 in the Database engines roster. SQLite records 1 on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Extension ecosystem. MariaDB records 3, 4th of 5 in the Database engines roster. PostgreSQL records 5 on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Migration tooling. MariaDB records 3, 3rd of 5 in the Database engines roster. PostgreSQL records 5 on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• JSON support. MariaDB records Text functions only, 3rd of 5 in the Database engines roster. PostgreSQL records Binary JSONB + indexes on the same field. If that is a hard requirement rather than a preference, start elsewhere.

We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.

What we don't know. Nothing, on the fields we track: all 26 of them carry a value for MariaDB. That is unusual and it will decay, vendors add dimensions faster than we add columns, so the verification dates beside each figure matter more than the completeness does.