MariaDB vs MySQL: Which One Should You Use? (2026)

The Fork I Didn’t Know Existed

Back in 2023, when I was over-engineering Clickly — my URL shortener that never shipped — I went shopping for a database like a man with too much time and zero users. I already knew about PostgreSQL and MySQL. Then, somewhere around 2 AM, reading a migration thread, I hit a name I didn’t recognize: MariaDB.

My first honest reaction was, “Is that a typo for MySQL?” It practically is. Same commands, same SHOW TABLES, same muscle memory. And that confused me for a solid week, because nobody explains why there are two databases that look like identical twins wearing different name tags.

So here’s the post I wish I’d found that night. If you searched “MariaDB vs MySQL” and you’re staring at two things that look the same and can’t tell why you’d pick one, sit down. This one has a real story behind it — a corporate acquisition, a heartbroken founder, and a fork that’s slowly turning into the more interesting branch.

---

Wait — Why Does MariaDB Even Exist?

MySQL was the open-source database of the 2000s. It ran a huge chunk of the internet. Then Oracle — a company that sells a very expensive proprietary database — ended up owning it. That happened in 2009–2010, when Oracle bought Sun Microsystems, and Sun had bought MySQL a couple of years earlier. So MySQL, the free people’s database, suddenly belonged to the one company with the strongest possible reason to not care about it too much.

MySQL’s original creator, Michael “Monty” Widenius, saw where that road went. So he did the most open-source thing possible: he took the code and forked it. He called the fork MariaDB (named after his daughter, the same way MySQL was named after another daughter, My). The whole point was insurance — a version of MySQL that no single company could buy, close, or quietly starve.

That’s the entire origin story, and it’s the thing every comparison blog skips: MariaDB and MySQL are the same database that split in two around 2009. Everything below is just the two halves drifting apart over fifteen-plus years.

---

Who Actually Owns Each One in 2026

This is the part that matters more than any benchmark, and it’s where the two genuinely diverge.

MySQL is Oracle’s. They keep it shipping — the current long-term-support release is MySQL 8.4 LTS, out since April 2025 and supported all the way to 2032, with a faster “innovation” track (the 9.x series) for people who want new features sooner and don’t mind short support windows. It’s stable. It’s fine. But it’s steered by a single, very commercial company that also sells the database it competes with.

And in 2025, the nervousness a lot of people felt back in 2009 got a fresh reason to exist. In September 2025, The Register reported that Oracle laid off a big slice of the core MySQL engineering team — dozens of senior engineers — as it leaned harder into its paid cloud product. Monty called it heartbreaking. Percona’s Peter Zaitsev, another long-time voice in this world, warned it looked like the slow starving of the free MySQL that everyone feared. I’m not here to dramatize it — Oracle didn’t kill MySQL, and MySQL 8.4 will be patched for years. But if you’re betting a business on a database, “who’s actually paid to improve this thing” is a fair question. And in 2026, the answer for MySQL got quieter.

MariaDB is owned by a fork of the community it came from. The actual MariaDB Server — the free, GPLv2 software — is stewarded by the non-profit MariaDB Foundation, whose entire job is to make sure no one can pull an Oracle on it. There’s also a commercial company (MariaDB plc, formerly MariaDB Corporation) that sells enterprise support; it had a rough ride on the public markets and was taken private by a private-equity firm, K1 Investment Management, in late 2024. That corporate drama is real, but it’s a layer above the open-source server. The server itself stays community-governed, which was Monty’s whole point.

For a founder, the read is simple: Postgres is owned by nobody, MariaDB is owned by a foundation, and MySQL is owned by Oracle. Rank those by “how much do I trust this to still be lovingly maintained in ten years” however you like. Mine’s the order I just typed them in.

---

The “Drop-in Replacement” Myth

For years, the pitch for MariaDB was: it’s a drop-in replacement for MySQL. Point your app at it, change nothing, done. That was basically true around the 5.5 era, when the two had barely drifted.

In 2026, it isn’t true anymore, and MariaDB stopped promising it. Fifteen years of separate development did what fifteen years does. They’re now better described as application-compatible — the basic SQL your app writes (SELECT, INSERT, joins, the boring 90%) works on both, but the moment you touch anything fancy, they diverge:

• Authentication. MySQL 8 moved to a newer default auth plugin (caching_sha2_password); MariaDB does auth differently. This is the single most common thing that bites people mid-migration.
• JSON. MySQL stores JSON in a real binary type. MariaDB treats JSON as basically a text column with a check constraint. (Both, for the record, are clumsier than Postgres’s jsonb — more on that in a second.)
• Replication and failover. Their GTID implementations differ, so tooling built for one topology doesn’t cleanly assume the other.
• Features each grew on its own. MariaDB added things MySQL doesn’t have — system-versioned (temporal) tables, sequences, an Oracle-compatibility mode, the Aria storage engine. MySQL grew its own transactional data dictionary and optimizer changes.

So the honest 2026 rule: don’t assume you can swap one for the other without testing. For a brand-new project it doesn’t matter — you pick one and build. It only bites when you try to migrate an existing app across, expecting a no-op.

---

Where MariaDB Quietly Pulls Ahead

If you’re firmly in the MySQL world — inherited a codebase, a client’s stack, a platform that only speaks MySQL — and you’re deciding between the two, here’s my take.

MariaDB moves faster and more openly. It ships LTS releases yearly (11.8 LTS landed in 2025; the 12.x line is rolling out with 12.3 as the current LTS in mid-2026), each supported for three years, and its development happens in the open with a community that’s genuinely active. It has more storage-engine options, a few features MySQL flat-out lacks, and — the part that matters right now — a full-time reason to exist that doesn’t depend on Oracle’s mood.

MySQL’s counter-argument is real too: it’s the more widely deployed of the two, so more hosting providers, tutorials, and third-party tools assume it by default, and Oracle’s LTS support windows are long and dependable. If your platform hands you MySQL and everything works, there is zero shame in leaving it alone. Don’t rewrite a working thing to win an argument with a blog post.

But if I were starting fresh and someone forced me into the MySQL family, I’d reach for MariaDB. Community-owned, faster-moving, less single-vendor risk. It’s the branch of the fork that still has people paid to love it.

---

The Part That Decides It: Where You’ll Run It

Databases don’t live on your laptop; they live on a managed host, and for a broke founder the hosting bill is the whole conversation.

Both MariaDB and MySQL are free software. The catch is finding a home for them that doesn’t charge you from day one. Most managed MySQL/MariaDB hosts — cloud provider database services, the usual suspects — start metering the moment you turn them on. The flagship MySQL-lineage home, PlanetScale (built by the ex-YouTube engineers behind Vitess), is genuinely beautiful engineering, but it killed its free tier back in 2024 and now starts around $5/month and climbs. Tellingly, in 2025 PlanetScale launched managed Postgres too. Read the room.

Compare that to Postgres, where Neon gives you a real free tier with pause-on-idle — I’ve run seven Postgres databases on Neon for $0 for years — and Supabase bundles auth and storage on top. When you’re counting paisa before your product earns a rupee, “starts free and scales with me” beats “great engineering, $5 minimum” every single time.

---

So Which One? (The Answer You Might Not Want)

Here’s where I have to be honest, even though you came here to compare MariaDB and MySQL specifically.

For a brand-new SaaS in 2026, I wouldn’t start with either. I’d use Postgres. Better JSON with real indexing, the pgvector extension when you bolt AI features on, PostGIS if you ever touch maps, no single corporate owner, and a free tier that survives the long $0-MRR winter. I laid out that full argument in PostgreSQL vs MySQL, and it lands in the same place every deeper guide on this site does — including the advanced database rabbit hole I fell all the way down for Clickly. Your Prisma or Drizzle setup won’t care which you pick, so pick the one that stays cheap and owns itself.

But you didn’t search “should I use Postgres.” You searched MariaDB vs MySQL, which usually means the choice is already half-made — you’re in the MySQL world for reasons that aren’t up for debate. If that’s you: MariaDB. It’s the community-owned branch, it moves faster, and in a year where Oracle looks less interested in MySQL than ever, betting on the fork that’s actually being developed is the low-regret move.

MySQL still wins the narrow cases — you inherited it, your platform is MySQL-native, a tool you depend on assumes it, or you specifically need the PlanetScale/Vitess sharding lineage at a scale you can prove is coming. Those are real. “Big companies use it” and “I heard it’s faster” are not, and those were exactly my reasons at 2 AM in 2023.

---

The Bottom Line

MariaDB and MySQL are the same database that split in 2009 over a question of who gets to own the future. Fifteen years later, MySQL sits inside Oracle with a thinner team, and MariaDB runs on a foundation whose entire reason to exist is not being Oracle. They’ve drifted enough that “drop-in replacement” is now a polite fiction, so test before you migrate anything real.

If you’re building something new and free to choose, run Postgres and go ship. If you’re already living in MySQL-land and just need to pick a side of the fork, run MariaDB. And whatever you land on, remember the thing 2023-me forgot: your database is the least interesting decision you’ll make this month. Nobody ever churned because you picked the twin.

This is the Broken Engineer Guide — I over-engineer everything, fail at business, and hand you the story so you don’t have to read migration threads at 2 AM. Now close the tab and go build.