MySQL Enterprise Edition pricing in 2026. Priced per server, often paid on servers that never use it.

MySQL Enterprise Edition is an annual Oracle subscription priced per server in two socket tiers. Most buyers pay it on far more servers than the workloads that use any Enterprise feature.

What is the MySQL Enterprise Edition price per server in 2026?

MySQL Enterprise Edition is an annual subscription priced per server, in two socket tiers. At list it costs $5,350 per server per year with 1 to 4 sockets and $10,700 with 5 or more, Oracle Premier Support included.

• Who sells it. Oracle, through its MySQL commercial program. The MySQL Global Price List on Oracle's price list page is the public reference for what a server costs before discount.
• What cores do to the price. Nothing. A 2 socket, 64 core server pays the same $5,350 as a small 1 socket box.
• Where it sits in the lineup. Standard Edition sits below Enterprise and Cluster Carrier Grade Edition (CGE) sits above it, as the MySQL products page lays out.

Choose the edition server by server, from the features each one runs. The edition your team ordered last time is a starting point for review.

Monitoring in the Enterprise column now means Oracle Enterprise Manager for MySQL. MySQL Enterprise Monitor reached end of life on January 1, 2025, so a renewal quote that still lists it as a benefit is out of date.

For the full definition of a server and how sockets are counted, see our breakdown of the MySQL per server metric.

What do the socket tiers mean for cost?

The price doubles when a server crosses from 4 sockets to 5 or more, so dense multi socket hosts pay more per server. Consolidating MySQL onto fewer large hosts can raise the per server tier even as it cuts the server count, which is why you should model both before you change topology.

• Consolidation that saves. Four 2 socket servers cost 4 x $5,350, or $21,400. Run the same MySQL instances directly on one 8 socket host and the line costs $10,700. Put them in four virtual machines instead and Oracle may count four servers.
• Consolidation that saves nothing. Two 4 socket servers cost $10,700 together. Merged onto one 8 socket host they still cost $10,700, with a larger single point of failure.
• A refresh that doubles the bill. Replace one 4 socket server with a 6 socket model and that line goes from $5,350 to $10,700 with no change in workload.

Virtual machines are where tier disputes usually start. Before you sign, get the rule for counting sockets on virtualized hosts written into the ordering document. Otherwise the tier depends on which Oracle representative reads your hardware list.

Does a multi year term lower the price?

Not at list. The MySQL store prices a three year Enterprise term for a 1 to 4 socket server at $16,050, exactly three times $5,350. Any multi year discount is something you negotiate, so ask for it as a percentage off list plus a cap on the renewal after the term ends.

Which servers need MySQL Enterprise Edition?

A server needs Enterprise when it carries a regulatory audit requirement, an encryption mandate, or a backup window that community tooling cannot meet. In our engagements those servers were a minority of the subscribed fleet.

• Needs Enterprise. Databases under PCI, SOX, or healthcare audit obligations that use MySQL Enterprise Audit and transparent data encryption (TDE) with managed keys.
• Needs Enterprise. Large databases that rely on MySQL Enterprise Backup for hot backups and point in time recovery at scale.
• Needs Enterprise. Internet facing databases where security has specified the Enterprise Firewall or data masking as a control.
• Standard is enough. Workloads that use none of the enterprise features but where operations wants a vendor support line.
• Does not need it. Stateless application databases, dev and test, and replicas that use none of the paid features.

Do development and test servers count toward the subscription?

They count whenever they run a commercial edition, and drop out only on Community binaries. Oracle's edition comparison states that every installation of a commercial edition must be licensed, including development, testing, backup and disaster recovery. If your build pipeline pulls the Enterprise packages everywhere, every test server is a subscribed server.

Is encryption at rest an Enterprise only feature?

Only partly. Community MySQL can encrypt InnoDB tablespaces using the file based keyring component. What Enterprise adds is the keyring integration with external key stores such as Oracle Key Vault, KMIP servers and cloud key services, plus the encrypted file keyring. If your auditors accept a local keyring file, the encryption mandate alone does not justify Enterprise.

How do you check which servers use Enterprise features?

Query each server directly. Your CMDB will tell you where MySQL is installed, but it rarely records which plugins are loaded or who runs backups with which tool. These checks cover most of what matters:

• Edition. SELECT @@version_comment; returns "MySQL Enterprise Server - Commercial" on Enterprise binaries and "MySQL Community Server - GPL" on Community.
• Plugins. SHOW PLUGINS; shows whether audit_log, MYSQL_FIREWALL or thread_pool are active.
• Components. SELECT * FROM mysql.component; lists newer Enterprise components such as enterprise encryption, masking and the encrypted keyrings.
• Backup. A populated mysql.backup_history table means someone runs MySQL Enterprise Backup against that server.
• Encrypted tables. Search INFORMATION_SCHEMA.TABLES for tables whose CREATE_OPTIONS include ENCRYPTION, then check which keyring serves them.
• Sockets. lscpu on Linux reports Socket(s). For virtual machines, record the physical host as well as the guest.

Tag each server with the features it uses and the owner who asked for them. The list of Oracle tools that pull a server into the paid count is longer than most teams expect. We cover it in MySQL Enterprise tools that trigger a subscription.

What does tiering save on a real renewal?

Tiering means paying Enterprise rates only where enterprise features run, and it is the biggest single saving on a MySQL renewal. The example below is hypothetical, priced at 2026 list.

Say you subscribe 48 servers to Enterprise: 40 with 1 to 4 sockets and 8 with 5 or more. The inventory shows 20 servers using an Enterprise feature, 10 more where operations wants Oracle support, and 18 dev, test and replica servers that use nothing paid.

The subscription drops by $155,150 a year, about 52 percent, before any negotiated discount. Subtract whatever third party support you buy for the Community servers you still want covered. In this example 48 subscribed servers against 20 that use Enterprise features is a ratio of 2.4, in line with what we see.

How the answer changes with the size of your MySQL footprint

With 5 to 10 servers, the saving from tiering is real but small in absolute terms. The stronger case is often moving a whole application off Enterprise at its next release. With 100 servers or more, the inventory work pays for itself many times over, and the socket tier on each large host deserves its own review.

Can community MySQL plus third party tools replace Enterprise?

For most workloads, yes. Percona and other open source tooling cover backup, monitoring and much of the audit surface. The residual case for Enterprise is a single support line accountable to Oracle, plus specific certified features that a regulator or auditor has named.

• Backup. Percona XtraBackup takes hot InnoDB backups of Community MySQL, and binary logs give you point in time recovery.
• Audit. Percona Server for MySQL, a GPL build of MySQL, ships its own audit log plugin.
• Monitoring. Percona Monitoring and Management and general tools such as Prometheus exporters cover what most teams used Enterprise Monitor for.
• Support. Percona and other providers sell MySQL support by server or by incident, which gives you a real price to compare at renewal.

If you are weighing a move off MySQL altogether, our comparison of MySQL Enterprise, MariaDB and PostgreSQL migration cost puts numbers on it.

Why we advise against standardizing every server on Enterprise

The usual advice is to run MySQL Enterprise on every server for consistency and single vendor support. We think that is wrong for most buyers.

Across roughly 30 to 45 Oracle engagements in 2024 to 2025, Fredrik Filipsson saw standardization put Enterprise rates on 2 to 4 times more servers than used an Enterprise feature. That serves Oracle's revenue more than your operations. Tier by demonstrated feature need instead, run Community or Standard elsewhere, and let a third party support quote price the difference.

How does MySQL show up in Oracle audits and negotiations?

MySQL Enterprise enters broader Oracle events in two ways: as an upsell concession inside a larger settlement, and as a support coverage question when Community installs sit next to subscribed servers. Neither creates exposure on the scale of Oracle Database, but both cost money.

• Bundle padding. MySQL subscriptions added to a settlement at a nominal discount inflate the deal Oracle reports, and you renew them every year after.
• Support scope creep. Renewals that extend subscriptions to servers that never used Enterprise features, often because a server list was copied forward.
• The HeatWave push. Oracle positions MySQL HeatWave as the modernization answer. Price it against your actual query profile, storage and egress before you commit.

HeatWave runs on OCI, natively on AWS, and on Azure through Oracle Database Service for Azure. Our HeatWave cost model shows how to compare it with what you pay on premises.

Is community MySQL ever a licensing risk?

Running Community MySQL for internal use is free under the GPL, and no subscription is owed for servers Oracle does not support. The risk is contractual rather than copyright. Some support agreements require matching coverage across defined environments, so read the support scope clause before you assume.

Distribution inside a product you sell is a separate question, covered in when you must pay for MySQL.

What the account team will say, and what to say back

• "Standardizing on Enterprise keeps you supportable." Support is sold per server. Ask Oracle to support the servers on your list and nothing else.
• "We can add MySQL to the database deal at a deep discount." Ask for MySQL on its own order with its own price. A discount on servers you do not need is still spend.
• "Those Community installs next to your subscribed servers are a compliance issue." Ask which clause in your agreement says so. Community under the GPL owes nothing on its own, provided those servers run Community binaries with no Enterprise plugins or components loaded, which is exactly what Oracle will check.
• "HeatWave will cost less than your on premises subscriptions." Ask for the shape, storage and egress pricing run against your real workload, in writing.

If Oracle opens a formal review of MySQL, our guide to how Oracle checks MySQL commercial use explains what they look for.

What have we seen in recent MySQL Enterprise renewals?

MySQL spend gets far less scrutiny than Oracle Database spend. Across roughly 30 to 45 Oracle licensing engagements Fredrik Filipsson advised in 2024 and 2025, three patterns came up again and again:

• MySQL Enterprise subscriptions covered 2 to 4 times more servers than the workloads that used any Enterprise only feature.
• Tiering cut MySQL subscription spend by 30 to 60 percent at the next renewal without removing a single required capability.
• In most engagements, MySQL line items appeared inside broader Oracle negotiations, priced as a concession the customer had not asked to make.

Pay Enterprise rates only on the servers that run Enterprise features, and make Oracle price everything else on its own merits.

What contract terms should a MySQL renewal include?

Ask for terms that tie the subscription to a known server list and let you shrink it. List prices move little from year to year, so most of the savings come from these clauses.

• A server schedule. Name each subscribed server and its socket tier in the order, so coverage cannot drift to unlisted machines.
• A written socket counting rule. State how sockets are counted on virtualized hosts, so a hardware refresh does not trigger a tier argument.
• A reduction right at renewal. Allow servers to come off without repricing the servers that stay.
• A narrow support scope clause. Limit support obligations to the listed servers, with no language requiring matching coverage across other environments.
• A renewal cap. Fix the maximum increase on the next renewal as a percentage of the current price.
• A separate order. Keep MySQL out of Oracle Database, Java or settlement paperwork unless it is priced line by line.

Our MySQL Enterprise licensing guide covers the ordering documents in more detail.

What does a strong MySQL renewal position look like?

It rests on three documents: a server list tiered by feature need, a third party support quote, and a subscription count that is flat or falling. Customers who arrived with that package got the savings described above. Our Oracle third party support guide explains how to get a quote Oracle will take seriously.

Mistakes that keep MySQL spend high

• Renewing from last year's server list. Decommissioned servers stay on the invoice until someone removes them.
• Letting a hardware refresh set the tier. A move to 5 or more sockets doubles the line with no warning in the renewal quote.
• Installing Enterprise binaries in every pipeline. Dev and test then count as subscribed servers.
• Accepting MySQL as a sweetener. The discount lasts one year and the subscription renews every year.

What to do next

1. Six months before renewal. Inventory every MySQL server and tag which Enterprise features each one uses.
2. Five months out. Reclassify servers with no Enterprise feature use to Standard, Community, or the decommission list.
3. Four months out. Check each socket tier against the real hardware inventory, including virtualization hosts.
4. Three months out. Request a third party support quote to price the alternative.
5. Two months out. Renegotiate the subscription count with the tiered server list and the contract terms above.
6. At every Oracle negotiation. Refuse MySQL bundle padding in unrelated Oracle settlements.

Frequently asked questions