Who Owns Postgres and MySQL? An Honest Look at Governance, Licensing, and Lock-In (2026)

This is the question every senior engineer asks before a long-term DB commitment. Almost no top-10 SERP result answers it honestly. Vendor blogs cannot. We do.

PostgreSQL: Foundation-governed, no single owner

PostgreSQL is governed by the PostgreSQL Global Development Group (PGDG), a volunteer association of contributors and companies. There is no single corporate owner. The license is the PostgreSQL License, a BSD-style permissive license that allows use, modification, and distribution with minimal restrictions. No GPL copyleft, no Oracle commercial.

Major contributors include EnterpriseDB, Crunchy Data, Microsoft (Azure), Amazon Web Services, Google Cloud, 2ndQuadrant (now part of EDB), Pivotal, and hundreds of individual contributors. No single company controls the roadmap. Decisions are made by core contributors through a consensus process.

The standard phrase in the Postgres community: “no single throat to choke”. This is meaningful for teams with long time horizons. PostgreSQL 17 (September 2024 GA) and the forthcoming 18 (beta, September 2026 expected) continue a cadence of annual major releases. The project has shipped a major release every year since 2008 without missing.

MySQL: Oracle-owned since 2010

MariaDB: The open-governance fork

Monty Widenius forked MySQL in 2009 (before Oracle closed the Sun deal) to preserve an open-governance version. MariaDB is named after his younger daughter. The MariaDB Foundation (non-profit) governs the open project. MariaDB plc (commercial company, formerly SkySQL) provides enterprise support and cloud services.

MariaDB 11.x is the current series. Drop-in compatibility with MySQL is declining at the high end: MariaDB has diverged on JSON syntax, storage engines, and some optimiser behaviour. For the LAMP ecosystem, MariaDB remains a “MySQL minus Oracle” option. Wikipedia, some Google internal systems, and ServiceNow's OEM stack run MariaDB.

Source: mariadb.org/foundation

MySQL HeatWave: The proprietary lock-in question

MySQL HeatWave is Oracle's in-memory query accelerator and ML/AutoML layer, launched 2021. It is closed-source and proprietary. Available only on Oracle Cloud Infrastructure (OCI) and AWS (since 2023). It is not available on-premises or on GCP/Azure.

Oracle's HeatWave performance claims for OLAP workloads are real and independently verified in some contexts. The lock-in is also real: schemas tuned for HeatWave do not trivially migrate. For teams committing to OCI or AWS, HeatWave is a genuine option. For teams that want optionality, the open Postgres equivalents are:

• Citus (open, Microsoft-supported) for distributed HTAP
• Hydra (open columnar Postgres) for analytics
• TimescaleDB (open, open-source core) for time-series
• DuckDB as an OLAP sidecar to Postgres

Percona Server: The open MySQL answer

Percona LLC produces Percona Server for MySQL, a binary-compatible MySQL distribution with added observability, additional storage engine improvements, and open-source tooling (Percona XtraBackup, Percona Monitoring and Management). Licensed GPLv2. Used by Etsy, GitHub (historically), and many MySQL-at-scale shops.

Percona's answer to the Oracle question: “use MySQL but depend on Percona's distribution rather than Oracle's.” This works if you trust Percona's long-term commitment. Percona also maintains Percona Server for PostgreSQL (adding additional monitoring and backup tools to vanilla Postgres).

The three-way decision