What often goes unmentioned in discussions of open source software governance is the structural tension between corporate ownership and community stewardship.In February, MariaDB plc appeared to remove Galera, a database clustering technology it acquired with Codership Oy in May 2025, from future MariaDB Server versions, the open source version run by the MariaDB Foundation. The strategic calculus here involves several competing considerations.Federico Razzoli, director of MariaDB consultancy Vettabase, noted that the community reacted because Galera is important for building highly available architectures.
What is often overlooked in the public discourse surrounding such moves is the opacity that preceded them.Razzoli complained that "Galera dependencies are being removed even from the binaries, without a commit message or a task description. From the GitHub discussions, those who should know what is happening appear to be in the dark." This absence of transparency created legitimate concern among users and developers who depend on Galera for production workloads. The diplomatic terrain is considerably more complex than the headlines suggest, however.MariaDB subsequently announced that MariaDB Community Server 12.3 would continue to include Galera Cluster libraries.
Max Mether, co-founder and vice president for product management at MariaDB Corporation, stated that "Community feedback is an important part of MariaDB, and recently, you made your voices heard regarding the inclusion of Galera Cluster in the 12.3 series. We've thoroughly considered your feedback and decided that now is not the time for a major change." The reversal reflected genuine community mobilisation.According to the MariaDB Foundation, the company "engaged with input from multiple directions and responded with a concrete statement that reduces near-term uncertainty for users relying on Galera today."
Yet concerns about long-term commitment warrant serious scrutiny.Razzoli noted the community needs reassurance that the company will not encourage users onto proprietary code, saying "I would like to see a promise from [MariaDB plc] on their website, saying 'our open source software will remain open.'" Three factors merit particular attention. First,MariaDB plc intends to concentrate new development efforts on its Enterprise Cluster and the newly developed Advanced Cluster. Second,uncertainty remains about what will happen when more advanced forms of Galera become available, with observers asking: "Will the Community edition continue to get Galera updates, or will this be held in place as a way to convince people to move to other versions of MariaDB?" Third, the broader history of the relationship complicates confidence:MariaDB was forked from MySQL after Oracle bought then-owner Sun Microsystems in 2010.
The historical precedent suggests caution.MariaDB Foundation CEO Kaj Arnö and community advocate Frederic Descamps both emphasised that there had been open dialogue and mutual respect, describing the relationship as undergoing a "friendly reset." YetMariaDB plc deserved credit for not simply forking Galera code after acquisition, which would have been cheaper. While it would be premature to conclude that MariaDB plc intends to abandon its open source obligations, the evidence suggests that the community's ability to mobilise pressure remains its most effective tool for ensuring that commitment.
The strategic implications extend beyond one company.The incident has left observers with several unanswered questions about the long-term relationship between MariaDB and its open source foundation. From the wider ecosystem's perspective, the reversal demonstrates both the power and the fragility of open source governance. The outcome reveals that coordinated community action can still check corporate decisions, even when those corporations have legitimate commercial interests to pursue. What remains uncertain is whether reassurance today translates into genuine long-term stability.