Oracle MySQL Licensing Guide 2026: Enterprise, Standard Edition & Community Cost Compared

MySQL Edition Breakdown: What Oracle Actually Sells

Oracle acquired MySQL AB in 2010 through its acquisition of Sun Microsystems. Since then, MySQL has operated as a dual-license product: an open-source GPL version and a commercial enterprise stack. The distinction matters enormously once your deployment reaches any scale or commercial context.

Oracle offers three commercial MySQL tiers. MySQL Enterprise Edition is Oracle's flagship commercial offering, bundled with high-availability tools, security features, audit plugins, and enterprise monitoring. MySQL Standard Edition 2 (SE2) targets smaller deployments with basic clustering support removed — it caps at four CPU sockets and two physical machines in a replication group. MySQL Cluster Carrier Grade Edition (CGE) is a separate, telco-grade product designed for continuous availability in high-transaction environments.

None of these are cheap. And none of them are appropriate for organizations that believe they are using "free" MySQL. If your application is proprietary and distributed, or if you deploy MySQL for internal commercial use and require commercial support, Oracle will argue you need a commercial license. Former Oracle LMS team members consistently confirm that MySQL is an active audit target — particularly where large clusters or cloud deployments are involved.

Pricing approximate. Actual Oracle list prices vary by region and are negotiated through your Oracle sales rep or CSI account.

The Community GPL Trap: When "Free" Becomes Expensive

MySQL Community Edition is released under the GNU General Public License version 2 (GPLv2). For most enterprise buyers, this creates a deceptively simple-sounding proposition: if you use the GPL version, you pay nothing. Oracle does not enforce payment for GPL-compliant use.

The trap is in what GPLv2 requires. If you distribute software that links to or incorporates MySQL, your software must itself be released under a GPL-compatible license. This is the copyleft requirement — and it is the mechanism Oracle uses to drive enterprises from Community to commercial licenses. The moment your proprietary application integrates with or embeds MySQL and you distribute that application externally — whether to customers, SaaS users, or even other business units in different legal entities — Oracle's license team argues that your application must comply with GPLv2. The commercial alternative: purchase an OEM or Enterprise license.

For organizations that run MySQL entirely on internal systems, for internal-only applications with no distribution, and without any redistribution of MySQL binaries, GPL use is defensible. But "internal use" is narrower than most IT teams assume. The moment a subsidiary, contractor, or cloud-hosted SaaS touches the stack, Oracle's legal team has grounds to challenge the arrangement.

MySQL Enterprise Edition Pricing 2026: What Enterprises Actually Pay

Oracle does not publish MySQL Enterprise Edition pricing. Like its database products, MySQL commercial licenses are negotiated through Oracle's sales organization or through authorized resellers. Oracle sells MySQL Enterprise Edition on a per-server, annual subscription basis. There is no perpetual license option for MySQL — all commercial editions are subscription-based, meaning termination of your subscription returns you to GPL terms (with all the compliance implications that entails).

Based on market intelligence from Oracle renewal negotiations, MySQL Enterprise Edition typically lists at approximately $5,000 to $10,000 per server per year, depending on the number of MySQL instances per server, the size of the deployment, and Oracle's assessment of your negotiating leverage. Multi-year agreements typically unlock discounts in the 15–30% range. Organizations with broader Oracle relationships — existing Oracle master agreement or ULA coverage — sometimes negotiate MySQL at lower effective rates when bundled into larger renewals.

What Oracle rarely discloses proactively: MySQL Enterprise Edition licenses are per physical server, not per instance. Running 10 MySQL instances on a single physical server still counts as one server license — but each physical host in your environment requires coverage. In containerised and virtualised deployments, Oracle's position becomes more aggressive, typically arguing that each physical host running containers with MySQL requires a server license regardless of how MySQL instances are distributed across pods.

MySQL Standard Edition 2: Where the Restrictions Bite

MySQL Standard Edition 2 (SE2) entered the picture in 2015 when Oracle retired MySQL Standard Edition and MySQL Standard Edition One. SE2 is positioned as a cost-effective option for enterprises with modest deployments, but its restrictions create meaningful limitations that many buyers do not fully evaluate before signing.

SE2 is licensed per physical server, with a hard cap of four CPU sockets per server. More restrictively, SE2 limits your InnoDB Cluster configuration to a maximum of two physical servers in any replication group. This is not a soft guideline — Oracle's license terms explicitly prohibit SE2 deployment across more than two machines in a high-availability cluster. Enterprises that start with SE2 for a modest application and then scale that application into multi-node HA configurations will find themselves in an unlicensed position under SE2 — and Oracle's LMS scripts are designed to detect this.

In practice, SE2 is appropriate for standalone or simple master-replica deployments on modest infrastructure. The moment your MySQL architecture introduces multiple primary nodes, Galera-style clustering, or NDB Cluster features, you are outside SE2's boundaries and into Enterprise Edition territory.

OEM and ISV Licenses: When You Distribute MySQL-Based Applications

If your organization develops and distributes software applications that include MySQL, the commercial license you need is an OEM (Original Equipment Manufacturer) license, not the standard Enterprise Edition. OEM licenses cover the redistribution of MySQL binaries embedded in or shipped with proprietary applications. They are priced entirely differently from standard server licenses and are negotiated directly with Oracle's OEM licensing team.

Oracle's OEM licensing framework for MySQL is opaque by design. There is no published price list. Pricing depends on your application's distribution volume, the pricing model you use (per seat, per transaction, per server deployed), and Oracle's view of the commercial value your application extracts from MySQL. Enterprises and ISVs building commercial products on MySQL routinely discover that Oracle's OEM pricing makes the economics of MySQL-based products considerably less attractive once they reach commercial scale.

The commercial license exception is broad. If you bundle MySQL with your application in any form — including as an optional component, a recommended dependency, or an auto-installed database — Oracle will argue you need OEM coverage for every copy of your application that goes out the door. This applies to SaaS products where Oracle MySQL runs in your infrastructure to serve customer data. The "you're not redistributing the software, you're just running it" argument has been challenged successfully by Oracle's legal team in multiple enforcement actions.

MySQL Audit Risk: How Oracle's LMS Scripts Target MySQL Deployments

MySQL is an active audit target. Oracle's LMS team runs specialized scripts against enterprise environments that identify MySQL installations alongside their Oracle Database, Java, and middleware deployments. If you receive an Oracle LMS audit letter and your environment includes MySQL, assume that MySQL will be part of the scope — even if the audit letter does not explicitly mention it.

LMS MySQL discovery scripts look for installed MySQL binaries, running MySQL processes, connected applications, and MySQL configuration files. They also correlate MySQL with other Oracle products in the environment — WebLogic applications that connect to MySQL backends, for example, or Oracle middleware that routes queries through MySQL datastores. The LMS team uses this correlation to build a picture of the commercial context of your MySQL deployment and to determine whether GPL use is defensible or whether commercial licenses are required.

The highest-risk MySQL scenarios are large-scale internal deployments without commercial licenses, containerised MySQL (particularly Kubernetes-based) where the GPL argument is complex, MySQL as a backend for distributed proprietary applications, and environments where MySQL Enterprise features (audit logging, monitoring) have been used without the accompanying Enterprise Edition license — a situation analogous to the Diagnostics Pack trap in Oracle Database.

MySQL on AWS, Azure, GCP & OCI: Cloud Deployment Licensing Rules

Cloud-managed MySQL services introduce their own licensing complexity. AWS RDS for MySQL, Azure Database for MySQL, and Google Cloud SQL for MySQL all provide managed MySQL based on the GPL Community Edition. Using these managed services avoids Oracle commercial license requirements — you are not deploying Oracle's commercial MySQL binaries. Oracle cannot audit your use of AWS RDS for MySQL the same way it audits your on-premise deployments.

However, if you bring your own MySQL Enterprise binaries to cloud infrastructure — running MySQL Enterprise Edition on AWS EC2 instances, Azure VMs, or GCP Compute Engines — you need a valid MySQL Enterprise Edition subscription covering each physical host running MySQL. Oracle's standard BYOL (Bring Your Own License) rules apply. Unlike Oracle Database, where BYOL to OCI has specific support rewards incentives, MySQL on OCI follows the same per-server subscription model as on-premise.

Oracle's own OCI MySQL HeatWave Database Service is a managed MySQL service that includes the MySQL HeatWave in-memory analytics accelerator. OCI MySQL HeatWave is licensed on a consumption basis through OCI Universal Credits — and Oracle actively promotes migration to this service as a way to consolidate Oracle spend. If your organization is an OCI customer, HeatWave may be an alternative to managing your own MySQL licenses — but evaluate the data transfer and storage costs carefully before treating OCI MySQL as a cost-saving move.

For organizations using the Oracle Cloud & OCI Advisory service, we regularly evaluate MySQL cloud licensing as part of broader OCI strategy reviews — particularly for clients weighing the costs of managed vs self-managed MySQL at scale.

Reducing Oracle MySQL Costs Without Migrating Away

The most common advice offered to enterprises with Oracle MySQL costs is to migrate to open-source alternatives: MariaDB, PostgreSQL, or cloud-native managed services. That is often the right long-term answer. But migration is not a quick fix — large MySQL estates can take years to migrate safely, and in the short term, you still need to manage Oracle's licensing claims.

The most effective immediate cost-reduction strategies within Oracle MySQL do not involve migration. The first is to accurately count your licensable servers. Enterprises consistently over-license MySQL by counting virtual machines, containers, and instances rather than physical hosts. Oracle's per-server model means you may be paying for many fewer servers than you think — if you map your environment correctly before negotiations.

The second lever is bundling. If your organization already has an Oracle contract negotiation with Oracle — whether an Oracle agreement, ULA, or annual renewal — MySQL Enterprise Edition can sometimes be bundled into that negotiation at rates significantly below list. Oracle's sales team is more willing to discount MySQL when it is part of a broader multi-product commitment than when it is negotiated in isolation.

The third lever is challenging audit findings before they become invoice demands. Our Oracle Audit Guide covers the full defense strategy. For MySQL specifically, the key challenge points are: whether your use qualifies as GPL-compliant, whether MySQL Enterprise features were actually used (versus installed), and whether Oracle's server counting methodology maps to your actual physical infrastructure.

Clients who have worked with us on MySQL license disputes have consistently achieved reductions in Oracle's initial compliance claims of 40–70% — with several avoiding commercial license obligations entirely by demonstrating defensible GPL use. See our Telecom Java Audit Defense case study for an example of how forensic license analysis defeats Oracle's initial audit position.