Skip to main content
Databases

MariaDB

The database most businesses inherit rather than choose.

Almost nobody chooses MariaDB. They find out they’re on it.

It’s the default database on most Linux distributions and most shared hosting. So this rarely arrives as a developer proposing MariaDB in a meeting. It arrives when you discover, part way through a conversation about something else, that the database your business runs on isn’t the one you thought it was. The question that follows is a fair one: is that a problem?

Usually not, but the reasoning matters, because the sentence that makes it fine also hides the two things worth checking.

“It’s basically MySQL”

You’ll be told it’s a drop-in replacement for MySQL. Same thing, different name.

That’s mostly right. It’s also an answer someone can give without having thought about it, which is why it earns a second question rather than a nod.

A fork, not a rebrand

MariaDB is a fork of MySQL. It was started in 2009 by MySQL’s original developers, while Oracle’s acquisition of Sun, and with it MySQL, was going through. The purpose was to keep a version under the GPL and outside the control of one commercial owner. That origin is why the reassurance you’re being given mostly holds up.

Where the MySQL compatibility stops

“Drop-in” has been eroding for fifteen years. Compatibility is still very good, but it isn’t total. Some newer MySQL features have no MariaDB equivalent, and some behave differently. It also isn’t symmetrical: MySQL to MariaDB is usually straightforward, while going back is straightforward only if nobody adopted MariaDB-specific features in between. “They’re interchangeable” stops being true the moment someone uses one of those.

The licence catch: the server is free, MaxScale isn’t

The “open source” label covers the database itself, and only some of what carries the name. The server is GPLv2. MariaDB plc, the commercial company alongside the project, sells surrounding tools, and some of those run under a Business Source Licence instead. MaxScale, its database proxy, is the one you’re most likely to meet. If you’re being sold MariaDB, establish whether that means the free database or a commercial product built around it, because the two carry different long-term costs.

Governance is the quiet strength nobody mentions

The MariaDB Foundation stewards the open source project and holds the trademark. MariaDB plc sells commercial products around it. That separation is structural rather than a promise, so no single company is in a position to relicense the database out from under you. Redis changed its licence in 2024, and a lot of businesses found out that “it’s open source” had been a statement about the past. MariaDB’s split ownership is the arrangement Redis did not have.

Questions to ask if you’ve inherited MariaDB

  • “Are we using anything MariaDB-specific, or just MySQL features that happen to run on it?” This decides whether you’re free to move. A vague answer means nobody has checked.
  • “Which version are we on, and when does it stop getting security patches?” Treat end of life as a budget deadline. Somebody should know the date.
  • “Are we buying anything from MariaDB plc, or only running the open source server?”
  • “If this had to become PostgreSQL in two years, what would that cost?” You aren’t planning to do it. You’re finding out whether anyone has thought about it.

When staying on MariaDB is the right call

Most of the time, and for a good reason. It’s the path of least resistance to a well-understood relational database that any developer can pick up.

If you’re running WordPress or WooCommerce, MariaDB and MySQL are functionally identical for your purposes. The platform doesn’t know which one it’s talking to. If your host already provides it, moving to MySQL is effort spent for no gain. The hiring position is about as good as it gets, too: MariaDB is close enough to MySQL that the whole MySQL talent pool can work on it, so being on it doesn’t narrow who you can employ.

A developer who tells you MariaDB is fine is, in the ordinary case, right. Ask anyway, to find out whether they know why.

When MariaDB is the wrong default for a new build

When the data model is the hard part of the system. MariaDB, like MySQL, is weaker than PostgreSQL for complex relationships, rich data types and heavy analytical work. If your application’s real difficulty lives in the data rather than the interface, that gap stops being academic. It’s worth deciding at the start of a build, because revisiting it later is expensive.

When “MariaDB” turns out to mean a commercial product. Covered above. The free server and the paid tooling around it are different commitments.

And when nobody decided it. MariaDB being the default is a perfectly good reason to be on it for a system that already exists. It’s a weaker reason to pick it for a new build. If something new is going onto MariaDB, it’s fair to ask whether that was considered or inherited.

Alexander De Sousa, Founder of Digital Royalty
Developer’s verdict

If you're on it, stay on it.

If you're already on MariaDB, stay on it. Migrating to MySQL costs real money and buys you nothing you could name in a meeting. The argument worth having isn't MariaDB versus MySQL, it's whether a database of this shape fits your data at all, and that's a PostgreSQL conversation. If you're starting something new and the data model is the hard part of the build, don't take MariaDB just because the host hands it to you.

Alexander De Sousa · Founder, Digital Royalty · LinkedIn

Compare it yourself

Compare it against the alternatives

The questions worth asking, answered honestly for MariaDB — line it up against any of the alternatives to check the call.

MariaDB — at a glance
What it actually is
Relational database
Licence
GPLv2 for the database server. Some surrounding tools from MariaDB plc (MaxScale, for instance) are under a Business Source Licence rather than the GPL, so "MariaDB is GPL" is true of the database and not of everything carrying the name.
Has the licence changed?
Not for the server itself. MariaDB was created in 2009 as a fork of MySQL specifically to keep a GPL version outside Oracle's control, and the server's licence has held since. The Business Source Licence on some adjacent tools is the thing to check if you are being sold more than the database.
Who controls it
Split deliberately: the MariaDB Foundation stewards the open source project and holds the trademark, while MariaDB plc sells commercial products around it. That separation is the structural protection against the licence being changed for commercial reasons — the arrangement Redis did not have.
Can you hire for it
Abundant — most developers know it
Paid support available
Yes, from MariaDB plc, and it is offered as a managed service by most cloud providers and virtually every shared host.
Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.