Community Edition runs any internal workload at any scale for zero dollars, and Oracle does not enforce payment for GPL-compliant use. This page draws the exact line where three narrow triggers convert that free database into a subscription costing $2,140 to $21,400 per server per year.
How to Negotiate Your Oracle SaaS Renewal: The Five Moves at the Table
Scope before price: strip the 18 to 32 percent of inactive bundle modules first. Kill the escalator with a 0 to 3 percent cap that survives the term, trade term for protections, refuse the easiest-path module bundling, and close on Oracle's May 31 clock.
Community Edition runs any internal workload at any scale for zero dollars, and Oracle does not enforce payment for GPL-compliant use. This page draws the exact line where three narrow triggers convert that free database into a subscription costing $2,140 to $21,400 per server per year.
The single most valuable fact for any MySQL buyer is that Oracle does not enforce payment for GPL-compliant use of Community Edition. Community and Enterprise share the same core engine, so the paid tiers do not buy you a faster or more capable database. They buy specific plugins, specific tools, and Oracle Premier Support. The compliance question is therefore not how big is my MySQL estate but have I crossed one of three narrow triggers. Everything else is noise, and most of the noise is generated by sales teams who benefit from you believing the GPL is a trap waiting to spring on your internal servers.
In 25 years negotiating Oracle contracts I have watched buyers hand over six-figure sums for MySQL subscriptions that covered two to four times more servers than actually used any paid feature. This page defines the boundary precisely so you can price only what you are obliged to price. It pairs with the Oracle MySQL Enterprise licensing buyer guide pillar and the deeper feature analysis in the MySQL Enterprise tools that quietly trigger a subscription.
Strip away the marketing and there are exactly three events that convert free Community Edition into a paid obligation. First, you deploy one of the Enterprise-only features (the plugins). Second, you embed MySQL in a product you distribute, and the GPLv2 copyleft would reach your own source code. Third, you want Oracle's indemnified Premier Support with a contractual SLA. If none of these three applies, you owe Oracle nothing, at any scale, forever.
Note what is not on the list. Server count is not a trigger. Data volume is not a trigger. Being a large enterprise is not a trigger. Running mission-critical production workloads is not a trigger. Running MySQL Community inside your own company, at any scale, for any workload, is precisely what the GPLv2 license permits. The copyleft question is real only when MySQL ships inside something you hand to a third party.
Server count, data volume, and workload criticality are not triggers. Only paid features, distribution copyleft, and indemnified support are.
Buyers routinely subscribe to Enterprise because they assume high-availability and clustering features are gated behind the paywall. They are not. Community Edition under GPLv2 already includes the full core engine, native replication, Group Replication, InnoDB Cluster, and MySQL Shell. That covers the vast majority of production high-availability architectures without a single dollar going to Oracle.
The practical takeaway: if your requirement is resilience, throughput, or scale, Community Edition almost certainly meets it. What Community does not include is the compliance and operational tooling that regulated industries need, and that is where the money starts.
Enterprise Edition adds a bounded set of paid components. Installing or running any of these plugins without a subscription is the core compliance exposure, and it is exactly the evidence Oracle looks for in an audit. The list is finite, so treat it as a checklist rather than a vague fear.
Oracle positions the security and compliance cluster (TDE, Encryption, Masking, Firewall, Audit) as the way to satisfy GDPR, PCI DSS, and HIPAA obligations. That framing is where the real pull toward Enterprise sits, because a regulated buyer with an auditor demanding encryption at rest and audit trails will reach for these plugins by default. Before you do, know that Percona Server for MySQL, which is free and open-source, provides most of these capabilities including audit logging and data-at-rest encryption. We treat the open-source substitution path in detail in the cost of leaving MySQL Enterprise for MariaDB, Percona, or Postgres.
The second trigger catches software vendors, not internal IT. If you distribute a product that links to or incorporates MySQL, GPLv2's copyleft requires that your distributed software also be released under a GPL-compatible license. For an ISV shipping proprietary code, that is unacceptable, which is exactly why Oracle sells a commercial OEM license. Oracle's own guidance is blunt: OEMs, ISVs, and VARs that want to embed MySQL binaries without releasing their proprietary source code should buy a commercial license, and buying one means the GPL no longer applies.
This is the one area where the fear is justified, but it is narrow. It applies to distribution, meaning you hand the combined software to a customer to run. It does not apply to a SaaS model where you run MySQL yourself and expose only an application over the network, because GPLv2 has no network-use clause (that is the AGPL, a different license Oracle does not use for MySQL Community). If you are an ISV, read the OEM and ISV distribution licensing guide before you ship. If you run MySQL purely to serve your own application, this trigger does not touch you.
MySQL is priced per server per year, in two socket bands, not per core. A socket is a physical CPU slot, and every occupied socket on which the program is installed or running must be licensed regardless of core count. The figures below are from the Oracle Global Price List dated September 11, 2025. Oracle Premier Support is bundled into every subscription at no extra charge.
| Edition | 1 to 4 socket server / yr | 5+ socket server / yr | What it adds |
|---|---|---|---|
| Standard Edition | $2,140 | $4,280 | Premier Support, Backup, basic tooling |
| Enterprise Edition | $5,350 | $10,700 | Full security stack, Firewall, Audit, TDE, Thread Pool, monitoring |
| Cluster CGE | $10,700 | $21,400 | NDB Cluster carrier-grade features |
| MySQL AI (Processor) | $625 per Processor, minimum 8 per server | AI subscription, processor-metric not socket-metric |
The socket metric is where the largest overcharges appear, and it is entirely avoidable. In advisory reviews the single biggest quote inflator has been the virtualization vCPU misread. A VM reports vCPUs, not sockets, and Oracle sales quotes have counted those vCPUs (often a thread count) as hardware, pushing a server into the 5+ socket band when the physical host sits comfortably at one to four sockets. That misread doubles the price. The correct count is the sockets of the underlying physical host, full stop. We detail the metric mechanics in how Oracle prices MySQL Enterprise Edition per server and the corresponding cost tactics in the 2026 MySQL Enterprise pricing breakdown.
The vCPU misread has been the largest single quote inflator we see, doubling the price on hosts that physically sit at one to four sockets.
How you consume MySQL in the cloud decides whether Oracle commercial licensing applies at all. Fully managed cloud MySQL, meaning Amazon RDS for MySQL, Azure Database for MySQL, and Google Cloud SQL, avoids Oracle commercial licensing because the provider supplies its own build and support. Bring-your-own-license MySQL on plain cloud VMs does not escape: you are running Community or Enterprise binaries and the same feature and support triggers apply.
This matters for the 8.0 end-of-life migration discussed below, because the cloud path can eliminate the entire Enterprise subscription question. If your only reason for Enterprise is Premier Support, moving to a managed service transfers support to the cloud provider and closes the exposure. How Oracle discovers commercial use in the first place, including in cloud VMs, is covered in how Oracle audits MySQL and checks commercial use.
As of April 21, 2026, MySQL 8.0 moved to Oracle Sustaining Support under the Lifetime Support policy. For paid subscribers Sustaining Support means no new fixes. For Community users it simply means no more security patches at all. Oracle directs everyone toward 8.4 LTS or 9.7 LTS. Each LTS version carries five years of Premier Support plus three years of Extended Support, so a move to 8.4 LTS buys Premier Support to April 2029 and Extended Support to April 2032.
Cloud timelines differ and you should map them per platform. AWS moves 8.0 into RDS Extended Support and, starting August 2026, auto-enrolls remaining 8.0 instances into a paid tier billed per vCPU-hour. Oracle Cloud extended 8.0 support in HeatWave to April 2027, after which remaining instances are force-upgraded to 8.4 LTS. The HeatWave and OCI cost mechanics are set out in the Oracle MySQL HeatWave and Database Service cost model.
Here is the negotiation lever. A per-server renewal on an unupgraded 8.0 estate buys no new fixes, so its subscription value is materially degraded. Every 8.0 renewal is really an upgrade conversation, and you should price the subscription on those servers accordingly. If Oracle wants a flat renewal on 8.0 servers that receive nothing but Sustaining Support, that is a discount argument you should press hard. This is the same logic buyers apply when breaking free from Oracle support to recapture roughly 50 percent through third-party alternatives.
Run a two-column inventory before your next renewal. Column one lists every server running MySQL. Column two lists which of those servers actually loads an Enterprise plugin (Backup, Audit, Firewall, TDE, Encryption, Thread Pool, or Enterprise Monitor). In our reviews Enterprise subscriptions covered two to four times more servers than the workloads using any paid feature. That gap is your immediate refund or reduction target.
The discipline is simple. Oracle profits from standardization: one edition, every server, no questions. Your job is to price only the three triggers you have actually crossed. Do that and MySQL stays what its license makes it, which is free for the overwhelming majority of what your organization runs.
Yes. Community Edition is released under GPLv2 and Oracle does not enforce payment for GPL-compliant use. Running it inside your own company, at any scale and for any workload including production, is exactly what the license permits. You owe nothing unless you use an Enterprise-only plugin, distribute MySQL inside a product, or contract for Oracle Premier Support.
The paid features are a finite list: Enterprise Backup, Enterprise Audit, Enterprise Firewall, Transparent Data Encryption, Enterprise Encryption, Data Masking, Enterprise Authentication, the Thread Pool scalability plugin, and Oracle Enterprise Manager monitoring. Installing or running any of these without a subscription is the core compliance exposure Oracle looks for in an audit. The engine, replication, Group Replication, and InnoDB Cluster are free.
No. GPLv2 copyleft is triggered by distribution, meaning you hand the combined software to a third party to run. A SaaS model where you run MySQL yourself and expose only an application over the network does not trigger it, because GPLv2 has no network-use clause. The distribution trigger applies to ISVs and OEMs who ship products embedding MySQL binaries.
Per the Oracle Global Price List dated September 11, 2025, Enterprise Edition lists at $5,350 per year for a 1 to 4 socket server and $10,700 for a 5 or more socket server. Standard Edition is $2,140 and $4,280. Cluster CGE is $10,700 and $21,400. Premier Support is bundled at no extra cost. Pricing is per physical socket, not per core.
As of April 21, 2026, MySQL 8.0 moved to Oracle Sustaining Support, which means no new fixes for paid users and no security patches for Community users. Oracle directs buyers to 8.4 LTS (Premier Support to April 2029, Extended to April 2032) or 9.7 LTS. Because a renewal on 8.0 buys no new fixes, treat every 8.0 server as an upgrade conversation and discount its subscription value.
Fully managed cloud MySQL (Amazon RDS, Azure Database for MySQL, Google Cloud SQL) avoids Oracle commercial licensing entirely because the provider supplies its own build and support. Bring-your-own-license MySQL on plain cloud VMs does not escape, since you are running the same binaries under the same feature and support triggers.
Breaking out of an Oracle PULA in 2026. The five exit traps, the certification math, the support uplift, and the renewal posture that.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
