MySQL Enterprise Edition prices a 64-core server at $5,350 a year while the same hardware costs over $1.5M under Oracle Database Enterprise Edition
Oracle sells MySQL by the server in exactly two socket bands, ignoring cores entirely, which makes dense hardware nearly free to license and turns server count, not compute, into the only cost driver. That single structural fact decides your consolidation strategy, your Standard Edition cap exposure, and whether the April 2026 move of MySQL 8.0 to Sustaining Support is worth renewing at all.
Prepared by Redress Compliance · August 17, 2026 · Oracle advisory. MySQL subscription and renewal engagements, 2024 to 2026.
Executive summary
MySQL Enterprise Edition lists at $5,350 per year for a 1-to-4-socket server and $10,700 for 5-plus sockets, and core count is irrelevant to both numbers.
Oracle's price list footnotes define a socket as a slot housing a chip regardless of the number of cores inside it, so a 128-core two-socket machine and a 4-core two-socket machine carry identical list cost.
The metric gap against the flagship is roughly 285 to 1 on a dense server: 32 processor licenses at $47,500 equals over $1.5M for a 64-core box, versus $5,350 under MySQL EE.
That gap is the single strongest argument in any workload-placement business case, and it also explains why Oracle sales compensation pushes so hard toward the flagship and toward HeatWave.
Support is not a separate 22 percent line on MySQL, it is welded into the subscription, so you cannot buy Enterprise Backup or TDE without the full $445.83 per server per month wrapper.
There is no unsupported license, no Software Update line item to drop, and no way to run a feature-only entitlement, which removes the usual renewal lever of shedding support on shelfware.
As of April 21, 2026 MySQL 8.0 sits in Sustaining Support, meaning a full-price renewal buys no new security fixes at any severity level.
Oracle called 8.0.46 the last 8.0 release, so any 2026 renewal quote for an 8.0 estate should be priced against 8.4 LTS (Premier to April 2029) or 9.7 LTS (Premier to April 2034) migration commitments, not accepted as-is.
The metric in full: two socket bands, three editions, one bundled support wrapper
Oracle sells MySQL commercially in exactly two price classes: servers with 1 to 4 sockets, and servers with 5 or more sockets. Nothing else about the machine matters.
Oracle's own footnote defines a socket as "a slot housing a chip or multi-chip module containing one or more cores," and states that regardless of the number of cores, each chip counts as a single socket.
A Server is "the computer on which the programs are installed," and a Server license permits use on a single specified computer. Every occupied socket on which the programs are installed or running must be licensed, which in practice means you license the box, not the workload.
The Annual Subscription bundles the right to use plus Oracle Software Update License and Support, and Oracle Premier Support for MySQL is included at no additional cost.
So there is no separate 22 percent support line to negotiate and no way to buy Enterprise Backup or TDE without the support wrapper.
All environments require a commercial agreement, not just production, and 5-plus socket purchases are quote-only through the MySQL Sales Team. The grid below is Oracle's September 11, 2025 MySQL Global Price List, cross-checked against the MySQL Enterprise Edition per-server pricing breakdown.
| Edition / SKU | 1 to 4 sockets, per year | 5+ sockets, per year |
|---|---|---|
| MySQL Standard Edition Subscription | $2,140 | $4,280 |
| MySQL Enterprise Edition Subscription | $5,350 | $10,700 |
| MySQL Cluster Carrier Grade Edition Subscription | $10,700 | $21,400 |
| Cluster CGE perpetual license (plus SULS) | $32,100 (+$7,062 SULS) | $64,200 (+$14,124 SULS) |
| MySQL AI Subscription | $625 per Processor, 8-processor minimum per server (approx. $5,000 floor) | Same metric, quote-only above 4 sockets |
Read the grid for what is missing. There is no core count, no memory ceiling, no user count, no named-user floor, no instance limit, and no separate support percentage.
The price does not scale with a single variable a capacity planner actually measures, which means your entire MySQL cost model reduces to one integer: how many physical boxes have MySQL installed on them.
A 16-core server and a 256-core server in the same 2-socket chassis pay the identical $5,350 on Enterprise Edition.
That has a second consequence buyers routinely miss. Because the metric is blind to consumption, Oracle has no revenue mechanism inside MySQL that grows as your workload grows.
Growth revenue has to come from somewhere else: edition upsell (Standard to Enterprise to Cluster CGE), server sprawl in your own estate, or a new metric entirely.
The MySQL AI SKU is the first crack in the wall, priced at $625 per Processor with an 8-processor minimum, which is a per-Processor metric wearing MySQL branding.
Why cores being free changes where you should put the workload
MySQL Enterprise Edition is not best understood as a cheap database. It is best understood as the last high-density metric Oracle still sells at scale, and that framing changes what you do with it. Set the two grids side by side.
On the Technology Global Price List effective April 16, 2026, Oracle Database Enterprise Edition lists at $47,500 per Processor, where Processor equals cores times core factor, with $950 per Named User Plus and a floor of 25 NUP per Processor.
A two-socket Intel server with 32 cores per socket, 64 cores total, converts to 32 Processor licenses at the 0.5 core factor, which is over $1.5M of list cost for one machine.
Push density to a two-socket, 256-core server and you are at 128 Processor licenses, $6,080,000 at list, with $1,337,600 a year in support behind it. The same physical box, running MySQL Enterprise Edition, sits in the 1-to-4-socket band at $5,350 a year with Premier Support included.
That is not a discount. It is a different theory of what you are buying.
The gap widens once you add option packs. On the flagship, Partitioning at $11,500 per Processor and RAC at $23,000 per Processor stack on top of the base rate, and a fully optioned Enterprise Edition Processor lists at $122,000 with $26,840 in annual support.
Multiply that by 32 Processors on the 64-core box and the arithmetic stops being a licensing question and becomes a capital planning question. MySQL EE bundles its feature set, backup, TDE, audit, monitoring, firewall, into the single rate.
The only structural cousin anywhere in the Oracle database portfolio is Standard Edition 2 at $17,500 per occupied socket, cores ignored entirely, and even that carries a hard two-socket-per-server cap that makes it unusable above modest density.
MySQL EE is the only place in the catalog where you can buy a 128-core socket and pay nothing extra for the 127 cores past the first.
The arbitrage is obvious once stated, and buyers systematically underuse it. If cost is per box, then every consolidation decision that reduces box count is directly rewarded, and every decision that increases box count is directly punished.
That inverts the discipline most database teams have been trained into. Under the core-based metric, the correct behavior is compute discipline: pin the instance, cap the cores, hard-partition the VM, keep the licensable footprint as small as you can defend in an audit.
Under the per-server metric, compute discipline buys you nothing at all. Trimming a MySQL instance from 32 cores to 8 saves zero dollars. What saves dollars is server-count discipline: fewer, denser, better-utilized machines, each one paying the same $5,350 whether it runs one schema or forty.
The collision is where the money actually gets lost. Standard Edition, at $2,140 per server, is capped at 4 CPU sockets and 2 physical servers in any HA cluster, and exceeding either limit creates unlicensed exposure rather than a graceful overage.
So the consolidation instinct that the metric rewards, push everything onto fewer big boxes, walks straight into a topology ceiling if you bought the cheap edition to save $3,210 per server.
Resilience requirements push the same direction: three-node groups, cross-site replicas, and quorum arbitrators all add servers, and each added server is a full-price server regardless of how little it does. A read replica that idles at 3 percent CPU costs exactly what the primary costs.
That is the real optimization problem, and it is not a technical one. It is an inventory problem.
Most estates we review carry between 15 and 40 percent more licensed MySQL servers than the architecture requires, almost all of it legacy replicas, decommissioned-but-still-installed hosts, and dev boxes nobody removed from the count.
The Oracle MySQL enterprise licensing guide walks the boundary cases where an install that nobody uses is still a licensable server.
Now read MySQL AI in that light. Oracle priced it at $625 per Processor with an 8-processor minimum per server, and the metric word matters more than the number. Processor is the flagship metric, cores times core factor, the thing MySQL has never been exposed to.
An 8-processor minimum on a 2-socket, 64-core box is not 8, it is 32, because the minimum is a floor and not a cap. That is roughly $20,000 per server for the same chassis that carries $5,350 of Enterprise Edition. Treat MySQL AI as a repricing attempt, not a feature release.
It is the mechanism by which core-based economics enter the MySQL estate, one workload at a time, and once a per-Processor SKU is normalized in your MySQL contract the argument for keeping the per-server bands on everything else gets structurally weaker at every renewal.
Oracle Analytics Server licensing, decoded for buyers
A buyer-side walk-through of Processor and Named User Plus metrics, the breakeven that decides which one you buy, and the virtualization rules that turn two processors into two hun
Get the white paper →Where the per-server metric quietly costs you more than you modeled
The socket band is generous. The scope is not. Oracle's own edition comparison states that all installations of Enterprise Edition, Standard Edition, and Cluster Carrier Grade Edition require an appropriate commercial agreement, which includes development, test, staging, QA, and standby.
There is no free non-production allowance the way buyers habitually assume from other vendors, and there is no cold-DR exemption in the MySQL price list footnotes.
In 25 years of counting Oracle estates, the ratio we see most often is roughly one non-production or standby instance per production instance, sometimes two.
That is where a tidy model breaks: 20 production servers at Enterprise Edition list is $107,000 a year, and the same estate with dev, test, and DR attached at a 3x total footprint is $321,000. Three other traps sit alongside it.
First, the socket rule counts all occupied sockets on which the program is installed and/or running, so a lightly used four-socket box in the low band is fine but a fifth occupied socket doubles the rate to $10,700.
Second, Standard Edition is capped at 4 sockets and 2 physical servers in any HA cluster, so the moment a third node joins for quorum or read scaling, the whole cluster needs Enterprise, a jump from $2,140 to $5,350 per server plus the newly licensed node.
Third, you cannot buy features without the support wrapper: a team that wants only Enterprise Backup or TDE pays the full $445.83 per server per month, as covered in our MySQL Community versus Enterprise breakdown.
| Exposure point | Modeled assumption | Contractual reality | List delta |
|---|---|---|---|
| 20 production servers, EE, 1 to 4 sockets | $107,000/yr | Baseline | Baseline |
| Dev, test, and DR added (3x footprint) | Free or discounted | All installations require a commercial agreement | $321,000/yr |
| Fifth socket occupied on one server | Same band | 5+ socket band applies | $5,350 to $10,700 |
| Third node in an SE HA cluster | SE at $2,140/server | SE capped at 2 physical servers, 4 sockets | Forced move to EE |
| Feature-only need (Backup or TDE) | Buy the feature | Support is bundled, no à la carte | Full EE rate |
The table understates one thing: your true socket count is not what your CMDB says, it is what Oracle's audit script finds installed.
Occupied sockets on machines where MySQL is merely installed and not running are licensable, and that catches decommissioned-but-not-wiped hosts, golden images, and containers baked onto multi-socket hypervisors. Before any renewal, run the inventory yourself and delete rather than argue.
Practical move: treat non-production as a first-class line in the model, then negotiate it down deliberately.
Oracle has no published non-production discount for MySQL, but bundled uplift on a consolidated server count is routinely available at renewal because the vendor prefers volume to per-instance disputes.
The 2026 lifecycle reset: what a renewal on MySQL 8.0 actually buys
As of April 21, 2026, MySQL 8.0 sits in Oracle Sustaining Support. Extended Support ended April 30, 2026, and Oracle has named 8.0.46 the final 8.0 release. Read that plainly: a renewal on an unchanged 8.0 estate buys you the right to open tickets and read existing documentation.
It does not buy security fixes. Oracle's own language is that no new server vulnerabilities will be fixed regardless of severity. The subscription rate, however, does not drop.
You pay the same $5,350 per server on Enterprise Edition for a materially thinner product than you bought in 2024, which is the cleanest price-for-value argument you will get all cycle.
The upgrade targets and their horizons are the frame for your ask. MySQL 8.4 LTS carries Premier Support to April 2029 and Extended Support to April 2032. MySQL 9.7 LTS, released April 21, 2026, carries Premier Support to April 2034. The LTS pattern is 5 years Premier plus 3 years Extended.
Innovation releases, by contrast, ship quarterly and are supported only until the next one arrives, which makes them unsuitable for anything you do not want to touch every 90 days.
Choose 9.7 if you can absorb the jump, because 8.4 gives you barely three years of Premier and puts you back at this table in 2029.
The NDB Cluster track has its own cliff, and it is often missed because it renews on a different line item. NDB Cluster 7.6 moves to Sustaining Support on May 31, 2026, and NDB Cluster Manager 8.0 is retired in favor of 8.4.
Cluster CGE buyers at $10,700 per 1-to-4-socket server should confirm which NDB stream their subscription actually covers before signing.
Price the migration effort into the renewal ask, not after it. Quantify the engineering days for the 8.0 to 9.7 jump, connector and query compatibility testing, and any NDB Manager rework, then present that number as the cost Oracle's lifecycle decision transferred to you.
In our experience, that framing supports a meaningful multi-year discount or a fixed-price commitment, and it pairs well with the consolidation math set out in our MySQL Enterprise Edition pricing analysis.
The cloud boundary: where the subscription stops applying
The subscription follows the installation, not the workload, and that single rule draws a hard line through your cloud estate.
If you run Amazon RDS for MySQL, Azure Database for MySQL, Google Cloud SQL, or Oracle's own HeatWave MySQL Database Service, there is no separate Oracle MySQL subscription to buy, because the license sits inside the hourly service rate. Oracle does not get a second bite.
If instead you install MySQL Enterprise Edition on an EC2, Azure, or Compute Engine VM, you are in bring-your-own-license territory and the per-server metric applies exactly as it does on iron: the license definition is the computer on which the programs are installed.
And every occupied socket on which the programs are installed or running must be licensed.
On a cloud VM, the socket band follows the shape of the instance as the provider presents it, and this is where buyers get hurt. A small or mid-size VM sits comfortably in the 1-to-4-socket band at $5,350 a year for Enterprise Edition.
Move that same database to a very large instance whose topology surfaces more than four sockets and the rate doubles to $10,700, quote-only, for no functional gain. In our experience the surprise almost always arrives after an infrastructure team resizes for memory, not for MySQL.
The negotiation consequence is about sequencing. Every workload you move to a managed service permanently removes a countable server from the estate, so those migrations should land before the renewal quote is built, not in the quarter after you sign.
Oracle prices from the server list you hand over. Hand over the post-migration list, and reconcile the BYOL VMs against instance topology first, using the boundaries set out in our Oracle MySQL Enterprise licensing buyer guide.
What we see in the deals: recurring patterns from MySQL renewals
The same server class ranges threefold across terms, which means term length, not volume, is the discount lever.
Any third node in an HA topology puts the deployment outside Standard entirely.
Five patterns repeat across renewal and audit-defense work, and each one traces back to a question nobody asked.
First, estates renew on unchanged server counts long after consolidation happened: the quote is built from a list drafted three years earlier, and because cores are free, the buyer never had a reason to recount.
The question: how many of these servers still exist, and who verified that this year? Second, Standard Edition deployments quietly breach the two-physical-server HA cap, usually when a DR replica or a third read node is added by a platform team that has no visibility into the license terms.
That is unlicensed exposure, and it converts to Enterprise at $5,350 per server the moment Oracle finds it.
The question: does any Standard cluster have more than two physical nodes or more than four sockets? Third, buyers pay the full Enterprise rate for a single feature, most often MySQL Enterprise Backup or TDE, because Oracle will not sell the feature without the bundled support wrapper.
At $445.83 per server per month, that is a deliberate choice, not an accident, and it deserves a build-versus-buy comparison against open-source tooling.
The question: what would we pay to replace this one feature? Fourth, the Standard spread from $2,140 to $6,420 per 1-to-4-socket server tells you Oracle prices term commitment, not volume, so a one-year renewal is the worst instrument you can hold.
Fifth, and most costly in 2026, we see MySQL 8.0 estates renewed at full rate with no adjustment requested, despite 8.0 sitting under Sustaining Support since April 21, 2026, which buys no new fixes and no security patches regardless of severity.
The question: what exactly does this subscription deliver for the next twelve months, and if the answer is nothing beyond access to the download portal.
Why is the price unchanged? Read the version and topology exposure together with our note on when free MySQL becomes a paid Oracle subscription, because the same server inventory drives both conversations.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
Your first five moves
- Count physical servers and occupied sockets before Oracle does, building a single inventory that includes development, test, QA, and DR boxes, because Oracle's own terms require every installation of Enterprise, Standard, or Cluster CGE to be licensed, not just production, and in our audit-defense work the non-production estate is where the unbudgeted server count usually surfaces.
- Test every deployment against the two boundaries that actually price the deal, the 1 to 4 socket band at $5,350 versus the 5-plus band at $10,700 for Enterprise Edition, and the Standard Edition hard caps of 4 sockets and 2 physical servers in any HA cluster, since a third node or a fifth occupied socket converts a compliant estate into unlicensed exposure overnight.
- Consolidate and decommission before you request a quote, not after, because each box removed from the inventory is a clean $5,350 to $10,700 off the annual subscription and cores are free inside the band, which makes dense two-socket hardware the correct consolidation target as explained in our MySQL Enterprise Edition pricing analysis.
- Price the MySQL 8.0 Sustaining Support position into the renewal, since as of April 21, 2026 the 8.0 track receives no new fixes and no security patches regardless of severity, with 8.0.46 named as the final release, so demand either funded migration assistance to 8.4 LTS or 9.7 LTS, or a discount that reflects a support wrapper delivering nothing.
- Treat any MySQL AI or HeatWave proposal as a metric change, not an upsell, because MySQL AI lists at $625 per Processor with an 8 processor minimum per server, an effective $5,000 floor per box that abandons the per-server model entirely; model it at 8 processors minimum against your full server count before signing, and read our MySQL Enterprise licensing buyer guide on how these clauses migrate estates onto core-based counting.
Frequently asked questions
How much does MySQL Enterprise Edition cost per year?
List price is $5,350 per year for a server with 1 to 4 sockets and $10,700 per year for a server with 5 or more sockets. Both figures include Oracle Premier Support for MySQL at no additional charge, so there is no separate support line.
Cores are not counted, so a 4-core and a 128-core server in the same socket band cost the same.
Does MySQL Enterprise Edition pricing depend on how many CPU cores I have?
No. Oracle's price list footnotes define a socket as a slot housing a chip or multi-chip module containing one or more cores, and state that regardless of the number of cores, each chip counts as a single socket.
Only the number of occupied sockets on the machine matters, and only to decide whether you fall in the 1-to-4 band or the 5-plus band. This is the opposite of Oracle Database Enterprise Edition, where the Processor count is cores multiplied by the core factor.
What is the difference between MySQL Standard, Enterprise, and Cluster Carrier Grade Edition pricing?
Standard Edition starts at $2,140 per year for a 1-to-4-socket server, Enterprise Edition is $5,350, and Cluster Carrier Grade Edition is $10,700 at the same socket band. At 5-plus sockets, Enterprise is $10,700 and Cluster CGE is $21,400.
Standard also carries hard topology caps of 4 CPU sockets and 2 physical servers in any HA cluster, so it is not simply a cheaper Enterprise.
Do I need to license MySQL Enterprise Edition in development, test, and DR?
Yes. Oracle states that all installations of MySQL Enterprise Edition, Standard Edition, and Cluster Carrier Grade Edition must be licensed under an appropriate commercial agreement, including production and other environments.
In practice a 20-server production estate with matching dev, test, and DR becomes 60 licensable servers, which is $321,000 at Enterprise list rather than $107,000. Count non-production before you quote, not after.
Can I buy MySQL Enterprise Backup or TDE without the full subscription?
No. Oracle sells an Annual Subscription as a single bundle of usage rights plus Software Update License and Support, with no à la carte feature purchase.
A buyer who wants only Enterprise Backup or Transparent Data Encryption still pays the full Enterprise rate, roughly $445.83 per server per month at 1 to 4 sockets. That removes the usual renewal lever of dropping support on features you no longer use.
Does MySQL 8.0 still get security patches in 2026?
No. As of April 21, 2026 MySQL 8.0 moved to Oracle Sustaining Support, Extended Support ended on 2026-04-30, and Oracle has designated 8.0.46 as the last 8.0 release. No new server vulnerabilities will be fixed regardless of severity.
If you are renewing an 8.0 estate at full price, you are paying the same rate for a materially reduced service and should either negotiate against that or commit to 8.4 LTS or 9.7 LTS.
Do I need a MySQL subscription on AWS RDS, Azure Database for MySQL, or Google Cloud SQL?
No. Cloud-managed MySQL services carry no separate Oracle MySQL commercial license because the licensing is embedded in the service price, and the same is true of the managed MySQL HeatWave service layer.
Bring-your-own-license MySQL Enterprise Edition installed on a cloud VM does require a subscription, and the socket band then follows the shape of that instance. Sequence any migration to managed services before renewal so the servers leave your countable estate.
There Is No EBS Licence: Only Lines
Session 1 of the Oracle EBS Licensing Series. Oracle E-Business Suite is licensed module by module, each with its own metric, and the metric you accept at purchase governs your cost for a decade. The foundation session: why the module is the entitlement, why support is 72 percent of the ten year bill, and why the database underneath is usually the bigger number.
