When people compare MariaDB and PostgreSQL, most focus on performance, indexing, or JSON support. But beneath those metrics lies a deeper question, one about freedom patterns and how open-source software evolves when power, profit, and community intersect.
This is not just a database comparison, it’s a story about two philosophies that shaped how open source survives in the age of cloud giants.
The Fork that Saved Openness
MariaDB was born out of rebellion. When Oracle bought Sun Microsystems, and with it, MySQL, the open-source world panicked.
What if Oracle slowly closed off MySQL, turning it into a corporate product?
Michael “Monty” Widenius, MySQL’s original creator, didn’t wait to find out. He forked the code and launched MariaDB, named after his daughter.
But this wasn’t just a technical fork, it was an ideological one.
MariaDB Foundation was created with a single purpose, to keep the database free forever, every commit, every new feature, had to align with that principle.
That philosophy speaks to me deeply. I choose MariaDB for most of my project is not because it’s faster or lighter, but because it embodies the idea that open source must protect itself.
It’s the same instinct that keeps communities free from corporate capture, a belief that openness isn’t just about code, it’s about governance and continuity.
The Quiet Strength of Continuity
PostgreSQL took an unusual path. It wasn’t born from a corporation but from the POSTGRES research project at UC Berkeley, and it matured under the PostgreSQL License, permissive in the same family spirit as BSD/MIT, built to invite adoption, forks, experiments, and strange new ideas without asking permission first.
Its governance is still profoundly community-shaped, a small core team, a long tail of contributors, and decisions hammered out through consensus rather than executive decree.
That gives PostgreSQL a quiet kind of legitimacy, earned, not marketed. But let’s not romanticize the consequence, permissive licensing also means anyone can take the core, wrap it in a proprietary control plane, and sell you “PostgreSQL” as a product while the real value, monitoring, automation, scaling knobs, guardrails, lives behind a curtain.
You see it everywhere, AWS RDS for PostgreSQL, Azure Database for PostgreSQL, Google Cloud SQL for PostgreSQL, the same familiar engine, but the steering wheel is locked in a vendor’s glovebox.
And you see a more explicit version of the same gravity in projects like TimescaleDB, where part of the stack stays permissively open, and another part shifts into a more restrictive, source-available reality depending on the feature set.
Perfectly legal, perfectly rational and exactly the kind of “open on the brochure, closed in the cockpit” pattern that makes my skin itch.
Licenses as Philosophy
Here’s where the difference stops being academic and becomes personal. MariaDB lives under GNU GPL v2, strong copyleft, not as a vibe, but as a weaponized boundary.
It doesn’t mean you must publish your code just because you run MariaDB. It means this, if you ship a modified MariaDB as a product, if you distribute the derivative, you don’t get to hoard the source like a dragon.
You either give back, or you don’t play.
PostgreSQL, on the other hand, is permissive by design. It lets you modify, embed, repackage, and yes, close your version if that’s what your business model demands.
That freedom is powerful, sometimes beautiful, but it also leaves a wide-open door for enclosure, rebranding, and “innovation” that never comes home.
So when people say, “It’s just a license,” I laugh.
MariaDB enforces openness through law, PostgreSQL relies on culture.
One is a contract you can take to court. The other is hope, and I’ve been in this industry long enough to know hope is not a strategy, especially when corporate gravity starts pulling.
Copyleft isn’t a limitation. It’s a seatbelt, You don’t wear it because you plan to crash, You wear it because eventually someone will.
Ecosystem and Commercial Gravity
MariaDB’s ecosystem stays closer to its roots, Galera Cluster, Aria, ColumnStore, there’s an insistence that the heart remains shareable, inspectable, forkable.
While there’s a commercial company in the picture, the MariaDB Foundation exists as a custodian of the server project, an upstream anchor that’s meant to keep “open” from becoming a marketing costume the moment a quarterly report gets nervous.
PostgreSQL thrives in a much wider commercial universe, and that’s both its triumph and its vulnerability. The ecosystem is full of excellent work, some fully open source, some open-core, some unapologetically proprietary, especially at the hosted layer where the money really lives.
You get compatible engines, managed platforms, proprietary acceleration, closed operational tooling, and branded “Postgres” experiences that are mostly about everything around Postgres.
The database becomes the seed crystal, the vendor layer becomes the cathedral.
MariaDB feels more deliberate. It keeps the core under GPL even when that choice makes monetization harder, slower, less seductive.
That philosophy resonates with how I build systems, I’d rather pay the price of discipline now than pay the ransom of lock-in later.
Openness first, business second, and if business can’t survive that order, maybe the business model is the problem.
Freedom vs Flexibility
MariaDB’s copyleft model offers a legal shield against enclosure. PostgreSQL’s permissive model offers freedom to innovate but leaves the door open for fragmentation.
To me, it comes down to what kind of freedom you value. PostgreSQL gives you freedom to close. MariaDB gives you freedom to stay open.
I personally prefer the second, because once your foundation is closed, rebuilding openness becomes almost impossible.
Choosing the Path
When I build systems that I want to last, that others can audit, fork, and improve, I want that permanence to be enforced, not assumed. GPL gives that.
PostgreSQL trusts the world to stay kind, MariaDB assumes the world will change and protects itself accordingly.
That’s why, when I architect systems using Node.js, MongoDB, and Debian, MariaDB feels like a natural fit, philosophically consistent with how I see open source, not as a license choice, but as a commitment to the next generation of developers.
Two Patterns, One Goal
Both MariaDB and PostgreSQL are pillars of open-source freedom. One preserves it through law, the other through trust, both work, both matter.
But in my journey, I choose MariaDB, not because it’s easier or faster, but because its very existence is a reminder, freedom in software doesn’t just survive by trust, it survives by design.
