MySQL Community Edition is free under the GPL at any scale, yet most enterprises overpay Oracle for servers that never touch a commercial feature. This guide draws the exact line between free and paid, decodes the per-server and HeatWave cost models, and hands you the artifacts that cut MySQL spend 30 to 60 percent.
How to Negotiate the Oracle Java Employee Agreement: Honest Leverage in a Captive Deal
Priced per employee, every employee, from $15 down to $5.25. At renewal your leverage is thin and OpenJDK threats rarely land. The one-year runway, trading through the wider Oracle relationship, and containing what you sign.
MySQL Community Edition is free under the GPL at any scale, yet most enterprises overpay Oracle for servers that never touch a commercial feature. This guide draws the exact line between free and paid, decodes the per-server and HeatWave cost models, and hands you the artifacts that cut MySQL spend 30 to 60 percent.
MySQL is the most misunderstood asset in the Oracle portfolio. Buyers who negotiate Oracle Database at the core level, who scrutinize Java at the employee metric, and who model OCI credit burn to the OCPU routinely leave MySQL unexamined because someone once said the words 'it's open source.' That instinct is half right and expensive. MySQL Community Edition is genuinely free under the GNU General Public License (GPL) for internal use at any scale, on any number of servers, forever. MySQL Enterprise Edition is a paid Oracle subscription priced per server per year, and the moment your team installs a commercial-only tool or accepts indemnified Oracle support, you have crossed a licensing line that Oracle's account teams are well trained to find and monetize.
This is a pillar guide to the whole commercial MySQL landscape under Oracle: the free Community Edition versus the paid Enterprise, Standard, and Cluster subscriptions, the per-server socket-tier metric, HeatWave and MySQL Database Service pricing in OCI, the open-source trap that turns 'free MySQL' into a mandatory Oracle contract, and the negotiation levers that let you flatten or shrink the bill. It is deliberately separate from our Oracle Database (EE, SE2, 23ai) coverage. MySQL is a different product, a different metric, and a different set of traps. Treat it as such.
Oracle ships MySQL along two distinct commercial tracks, and the distinction is the single most important fact in this entire guide. Track one is MySQL Community Edition, distributed under the GPL. You can download it, run it in production, replicate it across a thousand servers, and pay Oracle nothing. Cloud-hosted MySQL on AWS RDS, Azure Database for MySQL, or Google Cloud SQL sits in the same free zone from an Oracle licensing standpoint, because the hyperscaler carries any commercial obligation, not you.
Track two is the paid subscription family: MySQL Enterprise Edition, MySQL Standard Edition, MySQL Cluster Carrier Grade Edition, and the newer MySQL AI subscription. These are commercial contracts that bundle Oracle Premier Support, ship closed-source tooling that Community Edition does not include, and carry an OEM distribution right that Community Edition explicitly does not grant. The whole discipline of MySQL licensing is knowing which track each of your servers genuinely belongs on, and refusing to pay the paid-track rate for servers that live comfortably on the free track. As we detail in our breakdown of when free MySQL becomes a paid Oracle subscription, the majority of estates we review are running paid subscriptions on servers that never touch a commercial feature.
MySQL Community Edition is free for internal production use at any scale. The subscription buys features and distribution rights, not the right to run the database.
Oracle publishes MySQL list pricing in its MySQL Global Price List. As of the September 11, 2025 edition, the paid subscriptions are priced per server, tiered by socket count, and every tier bundles Oracle Premier Support at no extra charge. Here is the current list, which you should treat as the ceiling, not the expectation, in any negotiation.
| Edition (Subscription) | 1 to 4 socket server / year | 5+ socket server / year | Metric |
|---|---|---|---|
| MySQL Standard Edition | $2,140 | $4,280 | Server |
| MySQL Enterprise Edition | $5,350 | $10,700 | Server |
| MySQL Cluster Carrier Grade Edition | $10,700 | $21,400 | Server |
| MySQL AI Subscription | $625 (Processor, min. 8 per server) | $625 (Processor, min. 8 per server) | Processor |
Two things deserve immediate attention. First, the socket tier is a cliff, not a slope: a one-socket server and a four-socket server pay identical list prices, while jumping to a fifth socket doubles the fee. Second, the MySQL AI subscription breaks the pattern with a per-processor metric and an eight-license minimum per server, which means a minimum floor of $5,000 per server before you have run a single query. We unpack the mechanics in full in our deep dive on the per-server subscription metric, and you can compare against the summary on our MySQL Enterprise Edition pricing page.
Precision here is your defense. Oracle defines a Server as the single specified computer on which the programs are installed; a Server license authorizes use on that one machine only. A Socket is a physical slot that houses a chip or multi-chip module containing one or more cores. The buyer-friendly part: regardless of how many cores that chip contains, each occupied socket counts as one socket. A modern two-socket server with 64 cores per socket is still a two-socket server under this metric, which lands it in the cheaper 1-to-4 band. On dense physical hardware, MySQL's socket metric is one of the most favorable Oracle metrics in the entire portfolio.
All occupied sockets on which the program is installed or running must be licensed. That word 'running' is where virtualized estates get into trouble, which we address directly below.
If you take one operational rule from this guide, take this one: internal use, however large, is never the trigger. Three specific things cross the line from free Community Edition to a required paid subscription.
Note what is not on that list: running Community Edition in production, running it on hundreds of servers, running it to power a customer-facing SaaS application. None of those, on their own, require a dime to Oracle, because internal use is not distribution. We catalogue the exact tools that silently trip the wire in our guide to the MySQL Enterprise tools that trigger a subscription, and it should be required reading for every DBA and procurement lead in your organization.
Oracle publishes a FOSS License Exception, and buyers occasionally reach for it hoping to sidestep the OEM license. Read the fine print. Oracle's own legal text states that the FOSS License Exception does not apply to the MySQL database server itself; the GPL applies in full to the use and distribution of the database server alongside any other software. The exception covers connectors and client libraries in narrow cases, not the engine. If you are embedding the MySQL server in a distributed product, the FOSS exception is not your escape hatch, the commercial OEM license is. Our OEM and ISV distribution guide works through the decision tree for software vendors and device makers.
The socket metric that is so friendly on physical hardware becomes a weapon on virtualized estates. When MySQL runs inside a virtual machine, the guest reports vCPUs, not sockets. An account team that chooses to read those vCPUs as sockets can push a guest reporting eight vCPUs straight into the 5-plus-socket band and bill Enterprise Edition at $10,700 instead of $5,350. That is a 100 percent overcharge produced entirely by counting threads as sockets.
There is no clean, published Oracle rule that forces the correct reading in every hypervisor scenario, which is precisely why it is a negotiation battleground. Your defense is documentation: know the physical socket count of every host, know how your hypervisor pins or presents CPUs, and refuse to accept a per-vCPU or per-vThread count dressed up as a socket count. In our experience across recent Oracle engagements, the virtualization socket argument is one of the two most common ways MySQL bills get inflated. Model your true physical socket footprint before Oracle models it for you.
An eight-vCPU guest priced as an eight-socket server doubles your rate on a fiction. Count physical sockets, and make Oracle prove otherwise.
The larger and quieter money leak is not virtualization. It is paying Enterprise rates on servers that never run a single Enterprise feature. Across roughly 30 to 45 Oracle engagements we advised on in 2024 and 2025, the pattern was consistent: organizations were billing Enterprise Edition on two to four times more servers than ever touched an Enterprise feature. The driver is almost always a 'consistency' argument, either self-imposed ('we standardize on Enterprise everywhere') or Oracle-encouraged, that has no basis in actual feature consumption.
The fix is a feature-usage inventory, not an edition badge. For every server nominally on Enterprise Edition, ask: does this server actually run Enterprise Monitor, Enterprise Backup, Audit, TDE, or the Firewall? If the honest answer is no, that server is a candidate to drop to Community Edition, drop to Standard Edition, or move to third-party support. The badge on the contract is not the same as the requirement in the workload.
| Server profile | What it actually needs | Common billing error | Action |
|---|---|---|---|
| Runs Community, no commercial tools | MySQL Community Edition (free) | Billed Enterprise for 'consistency' | Drop from subscription entirely |
| Needs backup + basic support only | MySQL Standard Edition | Billed Enterprise at 2.5x the rate | Downgrade edition |
| Uses TDE, Audit, or Firewall | MySQL Enterprise Edition | Correctly licensed | Verify socket tier only |
| Embedded in distributed product | OEM commercial license | Ignored / unlicensed | License or accept GPL copyleft |
When a feature-usage inventory, a live third-party support quote, and a flat or declining subscription count all sit on the table at renewal, estates routinely cut MySQL spend by 30 to 60 percent. That is not a promotional figure; it is the observed range from the engagements above, and it is achievable because the starting position is so often subscription by habit rather than subscription by need.
Oracle's cloud MySQL story flips the licensing model entirely. MySQL Database Service (MDS) is a fully managed MySQL 8.x instance in OCI, priced per OCPU and per unit of storage. There is no separate MySQL license fee; the license cost is bundled into the OCI consumption price. That is a genuinely cleaner model than the on-prem subscription, and it removes the socket-counting and feature-audit anxiety in one move. But it introduces a different risk: cost stacking through optional layers.
HeatWave sits on top of MDS as an in-memory analytics accelerator, letting you run OLAP queries against your transactional data without a separate ETL pipeline into a data warehouse. It is charged per node as an add-on cluster. Above that sit the machine learning and generative AI layers. Each layer is optional, and each layer bills separately. Our full HeatWave and Database Service cost decode works through the OCPU math node by node.
Here is the trap in the HeatWave pitch. Oracle positions HeatWave as a single platform that replaces both your transactional database and a separate analytics warehouse, and on paper the consolidation argument is attractive. In practice, a HeatWave deployment sized to replace both workloads can cost three to five times the base MDS cost once the HeatWave cluster and the ML/GenAI layers are switched on. The base MDS OCPU price is the entry ticket, not the total. Model the fully loaded stack, all layers on, at your real peak node count, before you sign a consumption commit, because the commit will be sized to the loaded number, not the base.
OCI bills MySQL in OCPUs. An OCPU represents one physical CPU core. On x86 and most modern architectures, one physical core runs two threads, so 1 OCPU equals 2 vCPUs. When you compare an OCI HeatWave quote against an AWS or Azure quote expressed in vCPUs, you must convert or you will misjudge the price by a factor of two. Oracle quotes in the unit that makes its number look smaller; do the conversion yourself and compare on identical footing.
MDS bundles the license into OCPU pricing. HeatWave then stacks analytics and AI layers that can multiply the base cost three to five times over.
Timing is leverage, and the MySQL lifecycle just handed buyers a lever. As of April 21, 2026, MySQL 8.0 moved to Oracle Sustaining Support under the Lifetime Support policy. Sustaining Support means no new fixes and, critically for the free Community Edition, no more security patches. The practical consequence is stark: a per-server renewal on an 8.0 estate buys you no new fixes, which turns every 8.0 renewal conversation into an upgrade conversation whether Oracle frames it that way or not.
Use this. If you are being asked to renew Enterprise Edition on an 8.0 estate at list or near-list rates, the value you are receiving from the support component has materially dropped, because the version underneath is in Sustaining Support. That is a concrete, defensible basis for a price reduction or for accelerating a decision you were going to make anyway: upgrade, move to third-party support, or migrate off Oracle MySQL entirely. Do not renew 8.0 quietly at the old number.
Oracle now runs MySQL on a dual-track release model, and choosing the wrong track creates a self-inflicted patching problem. Long-Term Support (LTS) releases are built for production stability, each carrying five years of Premier Support plus three years of Extended Support. MySQL 8.4 is the current LTS release. Anyone moving to 8.4 LTS now has Premier Support through April 2029 and Extended Support through April 2032, a predictable eight-year runway.
Innovation releases are the opposite. They ship quarterly with the newest features and are supported only until the next Innovation release arrives, which makes them unsuitable for any production system that needs a predictable patching window. On April 21, 2026, Oracle shipped three releases at once: the final 8.0.46 build entering Sustaining Support, the 8.4.9 LTS maintenance release, and 9.7.0, which graduated from the Innovation track into LTS. The buyer discipline is simple: run production on LTS, keep Innovation releases confined to test and evaluation, and plan upgrades against the LTS support dates rather than the Innovation cadence.
| Release | Track | Premier Support until | Extended Support until | Status |
|---|---|---|---|---|
| MySQL 8.0.46 | Legacy | Ended | Ended | Sustaining Support (no patches) |
| MySQL 8.4 LTS | LTS | April 2029 | April 2032 | Current recommended LTS |
| MySQL 9.7 LTS | LTS | ~2031 | ~2034 | New LTS (from Innovation) |
| Innovation releases | Innovation | Until next release | None | Test / eval only |
Yes, though the mechanics differ from an Oracle Database audit. Because Community Edition is free and requires no license keys, Oracle cannot audit your MySQL footprint the way it audits a licensed product with LMS scripts and phone-home telemetry. What Oracle can do is infer commercial use from adjacent evidence: a support ticket referencing an Enterprise-only feature, a download of MySQL Enterprise Backup tied to your Oracle account, a sales conversation where a DBA casually mentions using the Enterprise Firewall, or a discovery tool run during a broader Oracle audit that finds Enterprise binaries installed.
The defense is behavioral and documentary. Keep Community and Enterprise deployments clearly separated. Never download Enterprise tooling to a server you intend to keep on the free track. Maintain the feature-usage inventory described earlier, because it is also your audit-defense artifact: it proves, server by server, which machines run commercial features and which do not. We walk through Oracle's actual discovery methods in our analysis of how Oracle checks MySQL commercial use. The short version: Oracle finds commercial MySQL through your own footprints, so control the footprints.
Oracle cannot license-key its way into your Community estate. It infers commercial use from your downloads, tickets, and conversations. Control those, and you control the audit.
The strongest negotiation position on any Oracle product is a credible willingness to leave, and MySQL has unusually clean exits. MariaDB began as a MySQL fork and remains close enough for many workloads to migrate with modest effort. Percona Server for MySQL is a drop-in-compatible distribution that pairs with Percona's third-party support, giving you the enterprise-grade support and tooling without an Oracle subscription. PostgreSQL is a larger migration but a durable one, and it removes you from the Oracle relationship entirely.
You do not need to complete a migration to benefit from it. A single credible third-party support quote from Percona or a comparable provider, placed on the renewal table, reframes the entire conversation from 'what will Oracle charge' to 'what will keep us from leaving.' We size the real switching costs in our guide to leaving MySQL Enterprise for MariaDB, Percona, or Postgres. Even where migration is not the right answer, the option's existence is worth double-digit percentage points at renewal.
Pull this together into a sequence you can execute before your next MySQL renewal or purchase.
Executed together, these steps consistently deliver the 30 to 60 percent reduction range we see in practice. The savings do not come from squeezing a discount out of Oracle's list price. They come from refusing to pay the paid-track rate for free-track servers, from reading the socket metric correctly, and from arriving at the table with a documented, defensible view of what you actually need. MySQL rewards the buyer who does the inventory work. The vendor is counting on you not doing it.
Yes. MySQL Community Edition is licensed under the GPL and is free for internal use at any scale, including production and customer-facing applications, on any number of servers. You owe Oracle nothing unless you install Enterprise-only tools, distribute MySQL embedded in a product you ship, or accept indemnified Oracle support. Internal use is not distribution and never triggers a fee.
On Oracle's September 2025 price list, MySQL Enterprise Edition is $5,350 per year for a 1-to-4-socket server and $10,700 for a 5-plus-socket server, with Premier Support bundled. Pricing is per server and tiered by socket count, not by core, so a dense two-socket server with many cores still lands in the cheaper band.
Installing any Enterprise-only tool triggers the requirement: Enterprise Monitor, Enterprise Backup, Enterprise Audit, Transparent Data Encryption, the Enterprise Firewall, and the Enterprise Authentication or Masking plugins. None of these ship with Community Edition, so their presence is direct evidence of commercial use and requires an Enterprise Edition subscription on that server.
HeatWave and MySQL Database Service in OCI are priced per OCPU and storage with the license bundled into consumption, unlike the on-prem per-server subscription. HeatWave adds an analytics cluster and optional ML/GenAI layers that bill per node, and a full deployment replacing both a transactional database and an analytics platform can cost three to five times the base MDS price. Remember 1 OCPU equals 2 vCPUs when comparing clouds.
As of April 21, 2026, MySQL 8.0 moved to Oracle Sustaining Support, meaning no new fixes and no security patches even for Community Edition. Renewing an Enterprise subscription on an 8.0 estate buys no new value, so every 8.0 renewal is really an upgrade or exit decision. Use the diminished support value as leverage for a price reduction or migration to 8.4 LTS.
Not in the same way, because Community Edition is free and uses no license keys. Oracle instead infers commercial use from support tickets, downloads of Enterprise tooling tied to your account, sales conversations, and discovery tools run during broader audits. Keep Community and Enterprise deployments separate and maintain a feature-usage inventory as your audit-defense record.
Oracle SE2 licenses per occupied socket at 17,500 dollars, two sockets maximum, 16 thread cap. Free paper on the metric choice and Enterprise Edition trap.
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.
