MySQL — the open source database behind millions of applications worldwide — is opening a new chapter. Today, Oracle announced a community governance model for MySQL that creates pathways for the broader community to participate in the project’s development and direction.
This post explains why AWS supports this move and what it means for the MySQL community.
Open governance makes open source work
Open source projects with diverse contributors and transparent governance produce better software. Open governance gives people a defined path from user to contributor to leader, and it gives organizations the confidence to invest their engineering in a project’s future.
MySQL has been a foundational piece of internet infrastructure for nearly three decades. Hundreds of thousands of businesses — from startups to the world’s largest enterprises — run their most critical workloads on it. Formalizing how the community participates strengthens that foundation and helps people plan for the future and build their businesses.
How the new governance model works
For the first time since Oracle acquired MySQL, organizations outside Oracle have a defined role in how the engine is built and where it goes. The model creates a progression of roles: contributors submit code and fixes, committers review and approve changes, and project leads own major subsystems such as the optimizer or InnoDB.
Above those roles sits a Steering Committee that sets MySQL’s long-term direction and release policy. The committee includes four seats from outside Oracle — held by cloud providers, MySQL customers, and the open source community — alongside an Oracle majority. Oracle names the first members for a two-year term, after which the non-Oracle seats move to community election.
Underpinning all of this, Oracle has launched a public GitHub presence for community MySQL — a channel for outside collaboration and contribution that did not exist before.
Why AWS supports this
AWS has been deeply invested in MySQL for over fifteen years — as users, as contributors, and as builders of services that depend on it. Tens of thousands of customers run MySQL workloads on AWS today. MySQL is one of the most important databases in our ecosystem, and our customers have a direct stake in its long-term health.
At AWS, we believe that open source is good for everyone, and we are committed to bringing the value of open source to our customers and the operational excellence of AWS to open source communities. That commitment shows up in a simple way: when customers run open source databases on AWS and hit a problem, we work upstream to fix it for everyone.
We have a track record of doing exactly that. In PostgreSQL, we made VACUUM six times faster, kept replication slots intact through upgrades, and removed the restart requirement for autovacuum configuration changes. In Valkey, the Linux Foundation fork of Redis, we added full-text search and hybrid query support. And we have already contributed fixes upstream to MySQL itself, including a fix for out-of-memory failures during upgrades on databases with large table counts and a fix for histogram errors.
A healthy upstream project benefits everyone who depends on MySQL — whether they run it themselves, use a managed offering, or build tools and integrations around it. When more engineers review code, more bugs get caught. When design decisions happen in the open, the features that ship reflect a wider range of real-world use cases. When governance is transparent, organizations can invest in the project with confidence that their contributions are valued and their voice is heard.
That’s not theory — it’s what we’ve experienced with OpenJDK, Valkey, and dozens of other projects where broad participation made the software better and the community stronger.
We want that for MySQL too.
What this means for the MySQL community
This governance model is a signal of long-term project health — for users, contributors, and organizations across the ecosystem:
- More eyes on quality and security — A structured review process with committers, project leads, and cross-component oversight means more engineers validating correctness, performance, and security before code ships.
- Faster innovation — Clear contribution paths and public collaboration lower the barrier for the broader ecosystem to propose and deliver improvements.
- Confidence in the project’s future — A Steering Committee with representation from Oracle, end users, and the open source community means MySQL’s direction reflects the interests of the people who depend on it — not just a single vendor.
- Continuity and compatibility — The governance model explicitly prioritizes stability, backward compatibility, and release quality. Users and operators can adopt improvements without worrying about disruptive changes.
A stronger upstream project means a stronger foundation for everything built on MySQL — managed services, self-hosted deployments, tools, and the broader ecosystem alike.
Looking ahead
AWS holds a seat on the MySQL Steering Committee, giving us a direct voice in the project’s roadmap and release decisions. We intend to use that voice for the customers running MySQL with us.
AWS contributes to open source communities for the long haul, and we are actively engaged with the MySQL project across the areas with the most direct impact on customer workloads:
- Performance — We are focused on the parts of the engine that determine how fast real workloads run: the query optimizer, query execution, indexing, the InnoDB storage engine, and the caching layer underneath.
- Vector search and indexing — AWS’s experience enhancing vector capabilities in open source databases is contributing to MySQL’s emerging vector support, building on collaborative work across the community.
- Extensions framework — MySQL’s component infrastructure lets new capability ship as loadable components that connect through defined service interfaces instead of being built into the core server code. This is one of the most open areas for community contribution, and we plan to invest here.
These build on the upstream work we already do. Running mission-critical workloads for hundreds of thousands of customers surfaces real problems — correctness, stability, and reliability issues that affect everyone — and we work through GitHub to fix them for the whole community.
The takeaway is straightforward: MySQL’s development is opening up, AWS has a seat shaping where it goes, and we are already contributing fixes and improvements upstream. Customers benefit wherever they run MySQL.
Get involved
We encourage developers, users, and organizations across the MySQL ecosystem to read the governance model and consider how they want to participate. Open source grows when people participate — and this model makes contributing easier than it’s ever been.