MySQL Community vs Enterprise in 2026. The three cases where you must pay Oracle.

MySQL Community Edition is free under GPLv2 for any internal workload at any scale. You pay Oracle only for Enterprise features, for distributing MySQL inside a product, or for indemnified support, at $2,140 to $21,400 per server per year.

Is MySQL Community Edition free for commercial use?

Yes. MySQL Community Edition is released under GPLv2, and Oracle does not enforce payment for GPL compliant use. A company can run it internally, at any scale and for any workload including production, without paying Oracle anything.

Community and Enterprise share the same core engine, so a paid subscription does not buy a faster or more capable database. It buys specific plugins, specific tools and Oracle Premier Support. This page pairs with our Oracle MySQL Enterprise licensing buyer guide and the feature detail in the MySQL Enterprise tools that trigger a subscription.

What are the three triggers that make you pay for MySQL?

Three events turn free Community Edition into a paid obligation. If none of them applies, you owe Oracle nothing, at any scale, for as long as you run it.

1. You deploy an Enterprise only feature. Installing or running one of the paid plugins or tools, such as Enterprise Backup, Audit, Firewall or Transparent Data Encryption (TDE), requires a subscription for that server.
2. You distribute MySQL inside a product. If you ship MySQL to a third party together with your own code, the GPLv2 copyleft would reach that code unless you buy a commercial license.
3. You want Oracle's indemnified support. Oracle Premier Support with a contractual SLA comes only with a paid subscription.

Server count is not on that list. Nor are data volume, company size, or production workloads your business depends on. Internal use at any scale is exactly what GPLv2 permits, and much of the fear around it comes from sales conversations that present the GPL as a trap for internal servers.

Server count, data volume and workload criticality are not triggers. Only paid features, distribution copyleft and indemnified support are.

How does your situation map to the triggers?

What does MySQL Community Edition include for free?

Community Edition includes the full core engine and the high availability stack most production designs need. Buyers often subscribe to Enterprise because they assume replication and clustering sit behind the paywall, and they do not.

• Engine. The core InnoDB engine, identical to Enterprise, with no performance difference in the engine itself.
• Replication. Asynchronous and semisynchronous replication, plus Group Replication for single primary and multi primary clusters.
• InnoDB Cluster. Group Replication, MySQL Shell and MySQL Router combined, with automated failover.
• MySQL Shell. Administration and orchestration, including dump and load utilities for logical backups.
• Connectors and Router. The standard connectors, MySQL Router and the query optimizer.
• Basic encryption at rest. InnoDB tablespace encryption with component_keyring_file, which keeps the master key in a local file.

If your requirement is resilience, throughput or scale, Community almost certainly meets it. What it leaves out is the compliance and operational tooling that regulated industries are asked to show.

Which MySQL features require an Enterprise subscription?

Enterprise Edition adds a bounded set of paid components. Running any of them without a subscription is the core compliance exposure and the evidence Oracle looks for in an audit, so treat the list as a checklist.

• MySQL Enterprise Backup. Hot, online backups with incremental support. The free routes are mysqldump, MySQL Shell dumps and Percona XtraBackup.
• Enterprise Audit. Policy based audit logging for compliance evidence.
• Enterprise Firewall. Blocks SQL outside an approved allowlist of query digests.
• TDE and Enterprise Encryption. Encryption at rest with the Enterprise keyrings, plus the encryption functions.
• Enterprise Authentication. PAM, LDAP, Kerberos and Windows integration.
• Data Masking and De-Identification. Masking of sensitive values for test data and reporting.
• Thread Pool. The scalability plugin for high concurrency workloads.
• Monitoring. Enterprise Telemetry and Oracle Enterprise Manager for MySQL.

Oracle presents the security group (TDE, Encryption, Masking, Firewall and Audit) as the way to meet GDPR, PCI DSS and HIPAA obligations. That is the real pull toward Enterprise, because a regulated buyer whose auditor asks for encryption at rest and audit trails reaches for these plugins by default.

Where does encryption at rest stop being free?

InnoDB encryption is free, and the charge starts with key management. Community ships only the file keyring, which stores the master key on the database host. Oracle's documentation lists the encrypted file keyring and the OCI Vault, KMIP, AWS KMS and HashiCorp Vault keyrings as Enterprise only.

So ask your auditor a narrow question. If a local key file protected by operating system controls satisfies the control, Community is enough. If policy requires keys in an external vault or HSM, you need an Enterprise keyring or a free build that provides one.

Which free tools replace each Enterprise feature?

Percona Server for MySQL, which is free and open source, provides most of the paid list, including audit logging and encryption at rest. We cover what switching costs in the cost of leaving MySQL Enterprise for MariaDB, Percona or Postgres.

Why we disagree that regulated workloads need Enterprise Edition

The usual advice is that any database in scope for PCI DSS, HIPAA or GDPR should run Enterprise Edition. We disagree, because those rules require controls such as encryption, audit trails and access control, and none of them names a vendor product. An auditor tests whether the control works and is evidenced.

List each control your auditor names, test the free route against it on one server, and buy Enterprise only where the substitute fails. That confines the subscription to the in scope systems where Oracle's tooling is the simplest answer.

When does distributing MySQL require a commercial license?

You need Oracle's commercial OEM license when you distribute a product that links to or incorporates MySQL and will not release your own code under a GPL compatible license. This trigger catches software vendors far more often than internal IT.

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 to that use.

Does running MySQL behind a SaaS application count as distribution?

No. Distribution means handing the combined software to a customer to run. A SaaS model where you operate MySQL yourself and expose only an application over the network is outside it, because GPLv2 has no network use clause. That clause belongs to the AGPL, which Oracle does not use for MySQL Community.

What about client libraries and hybrid products?

The MySQL connectors are GPL licensed too, with Oracle's Universal FOSS Exception covering open source applications under other licenses. A proprietary product that bundles a connector raises the same copyleft question as one that bundles the server.

Hybrid cases need the closest reading: an on premises edition of a SaaS product, an appliance, or an installer your customer runs. ISVs should read the OEM and ISV distribution licensing guide before they ship, and have counsel confirm in writing which products leave the company.

How much do MySQL Standard, Enterprise and Cluster CGE cost?

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.

Oracle Premier Support is bundled into every subscription at no extra charge. The metric is explained in how Oracle prices MySQL Enterprise Edition per server, and cost tactics in the 2026 MySQL Enterprise pricing breakdown.

Standard Edition does not include MySQL Enterprise Backup. Oracle's edition comparison places Backup, Thread Pool and the whole security group in Enterprise and Cluster CGE only.

Standard also leaves out Group Replication, InnoDB Cluster, ReplicaSet, MySQL Router and partitioning. These are free under the GPL in Community, but on a commercial subscription they come only with Enterprise. Standard therefore fits a standalone or classically replicated server that needs Oracle support and nothing more.

How are sockets counted when MySQL runs in a VM?

Count the sockets of the physical host underneath the VM. A VM reports vCPUs, and Oracle sales quotes have counted those vCPUs, often a thread count, as hardware. That pushes the server into the 5+ socket band when the host sits at one to four sockets, and it doubles the price.

The price list defines a server as the computer on which the programs are installed and gives no separate rule for virtual machines. Ask Oracle to write the VM counting rule into the order before you agree any server count.

How do you check which MySQL servers need a subscription?

Build a two column inventory before your next renewal. Column one lists every server running MySQL. Column two records which of them loads an Enterprise plugin or tool: Backup, Audit, Firewall, TDE, Encryption, Thread Pool or Enterprise Monitor.

• Edition. SELECT @@version_comment returns MySQL Community Server - GPL on Community builds and MySQL Enterprise Server - Commercial on Enterprise ones.
• Plugins and components. SHOW PLUGINS reveals audit_log, thread_pool or MYSQL_FIREWALL, and the mysql.component table shows newer features such as data masking.
• Keyrings. The file keyring is Community. Any vault or KMIP keyring is Enterprise.
• Backups. Look for the mysqlbackup binary in job schedulers and rows in mysql.backup_history.
• Host sockets. Take socket counts from the hypervisor host inventory, because the guest shows only vCPUs.

Any server that crosses no trigger is a candidate for Community Edition. The difference between the two columns is your immediate refund or reduction target.

What does a mixed MySQL footprint cost once you apply the triggers?

Say a renewal quote covers 36 servers, all on Enterprise Edition. Oracle bills 24 at the 1 to 4 socket rate and 12 VMs at the 5+ rate because each shows 16 vCPUs, yet every host underneath has two sockets.

Your inventory finds 6 servers in PCI DSS scope that load Enterprise Audit and keep TDE keys in an external vault. Another 4 are standalone servers under a packaged application whose vendor requires Oracle support. The remaining 26 load no Enterprise feature.

The two corrections take $216,140 a year off list, about 84 percent, before any discount is discussed. The 26 servers still carry work: Enterprise binaries must be swapped for Community builds and backup jobs moved to XtraBackup, and that effort belongs in the business case.

Does running MySQL in the cloud remove Oracle licensing?

Only if the provider supplies the build. 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, since you are running the same binaries under the same triggers. If Premier Support is your only reason for Enterprise, a managed service transfers support to the provider. How Oracle finds commercial use, including on cloud VMs, is in how Oracle audits MySQL and checks commercial use.

What does MySQL 8.0 end of life mean for your subscription?

An 8.0 server under subscription now buys less than it did. Since April 21, 2026, MySQL 8.0 has been in Oracle Sustaining Support under the Lifetime Support policy, so paid subscribers get no new fixes and Community users get no more security patches at all.

Oracle directs everyone to 8.4 LTS or 9.7 LTS. Each LTS release carries five years of Premier Support plus three years of Extended Support, so upgrading to 8.4 LTS buys Premier Support to April 2029 and Extended Support to April 2032.

How do the cloud timelines differ?

• Amazon RDS. Standard support for RDS for MySQL 8.0 ended July 31, 2026. Since August 2026, remaining 8.0 instances run on RDS Extended Support, a paid tier billed per vCPU hour.
• Oracle HeatWave. Oracle extended 8.0 support to April 2027, after which remaining instances are upgraded to 8.4 LTS in their maintenance window. The cost side is in the Oracle MySQL HeatWave and Database Service cost model.

How should the 8.0 date change your renewal?

A per server renewal on servers still running 8.0 buys no new fixes, so its value has dropped. Treat every 8.0 renewal as an upgrade conversation, and if Oracle asks for a flat renewal on servers that receive only Sustaining Support, press for a discount.

It is the same reasoning buyers apply when they move Oracle products to third party support and recapture roughly 50 percent of the support cost.

What have we seen in recent MySQL subscription reviews?

Two patterns recur in the MySQL renewals we review. In our reviews, Enterprise subscriptions covered two to four times more servers than the workloads using any paid feature, and some buyers paid six figure sums for that coverage.

The second is the vCPU misread, which has been the single biggest quote inflator we see. The first comes from Oracle's preference for one edition on every server, and the answer to both is to price only the triggers you have actually crossed, on the sockets the hosts actually have.

Which mistakes cost MySQL buyers the most?

• One need sets the edition for everything. A single backup or audit requirement ends up putting the whole footprint on Enterprise.
• Non production Enterprise installs treated as free. Oracle requires a commercial agreement for development, testing, backup and disaster recovery installs of the paid editions.
• Binaries left behind. An Enterprise build or plugin still on a server after its subscription ends is exactly what an audit finds.
• OEM rights priced with internal servers. Mixed into one order, the distribution deal ends up setting the internal price.

What will Oracle's account team say, and how should you answer?

• "Community is unsupported, so production needs Enterprise." Support and license are separate decisions. Buy Standard Edition where you want Oracle behind a standalone server that uses no Enterprise feature, and keep InnoDB Cluster systems on Community unless they need Oracle support.
• "The GPL means your applications have to be open source." That applies only if you distribute them with MySQL, and a SaaS service you host yourself is not distribution.
• "These VMs show 16 vCPUs, so they fall in the 5+ socket band." Send the hypervisor host summary showing the physical sockets.
• "Dev, test and DR need licenses too." True for Enterprise binaries, so run Community builds on those servers.

Which contract terms should you ask for?

• A written VM counting rule. Socket bands follow the physical host, so a resize or migration cannot move a server into the 5+ band.
• A named server list. Each subscription tied to a hostname and edition, so a later reduction is an edit to that list.
• A reduction right. The option to drop servers, or step them down to Standard, at each anniversary without repricing the rest.
• A price hold. A fixed per server rate for every renewal year you commit to.

What to do next

1. Build the inventory. List every MySQL server and mark which ones load an Enterprise plugin or tool.
2. Check for distribution. Confirm no product you ship embeds MySQL binaries. If one does, scope the OEM license separately so it cannot affect internal pricing.
3. Correct the sockets. Validate every count against physical host sockets, and reject any quote built on a thread or vCPU count.
4. Tier the editions. For standalone servers that need Oracle support but no Enterprise feature, price Standard Edition against Enterprise instead of defaulting everything to Enterprise.
5. Test the free routes. For encryption, audit and firewall requirements, check whether Percona Server or a managed cloud service satisfies your auditor before you subscribe.
6. Decide every 8.0 server. Upgrade, migrate or retire it, and discount its subscription value while it sits on Sustaining Support.

Frequently asked questions