MySQL licensing, when free becomes an Oracle subscription
MySQL Community is free under the GPL, and most estates never owe Oracle a cent for it. The paid editions exist for three reasons, commercial features, OEM embedding rights, and indemnified support, and the buyers who overpay are almost never overusing MySQL. They are overcounting it.
Prepared by Redress Compliance · August 6, 2026 · Oracle licensing advisory. Based on 15 to 25 commercial reviews touching MySQL 2024 to 2026.
Executive summary
The free boundary is clean: MySQL Community Edition is free under the GPL, for internal use at any scale, and cloud MySQL, RDS, Azure Database, Cloud SQL, needs no Oracle subscription either.
You cross into paid territory for one of three reasons: the Enterprise only features, monitoring, audit, TDE, firewall, and the backup tooling, an OEM right to embed MySQL in a product you distribute, where the GPL's copyleft would otherwise reach your code, or indemnified vendor support.
Paid MySQL prices per server by socket count, not by core. Enterprise Edition lists at $5,350 per year for a 1 to 4 socket server and $10,700 for 5 plus sockets, with Standard below it and Cluster CGE above.
The socket construction is buyer friendly on modern dense hardware and dangerous on virtualized estates, where a guest reporting eight vCPUs gets priced into the 5 plus socket band, at double the rate, by an account team counting threads as sockets.
The overcounting is the whole story of MySQL commercial reviews.
Across ours, more than half of subscribed servers had no Enterprise only plugin loaded at all, the plugin table returned nothing beyond shipped defaults, and the single largest quote inflator was that socket arithmetic on virtual machines.
The estates that renegotiated best arrived with one artifact: a per instance inventory naming which Enterprise feature each paid server actually loads.
The calendar adds a fresh lever: MySQL 8.0 moved to Sustaining Support on April 21, 2026, which means a per server renewal on 8.0 buys no new fixes.
Every renewal conversation on an 8.0 estate is really an upgrade conversation, and the subscription's value on unupgraded servers deserves to be priced accordingly, by you, before Oracle prices it.
Where free ends, the three real triggers
The Community edition carries the full database engine. What it does not carry defines the commercial conversation:
| Trigger | What it means | The honest test |
|---|---|---|
| Enterprise features | Monitoring, Enterprise Backup, TDE, audit, authentication, and firewall plugins | Query the plugin table: a server loading none of them is a Community workload with an invoice |
| OEM embedding | Distributing MySQL inside a commercial product, where GPL copyleft would reach your code | A genuine legal trigger: shipping software with MySQL inside needs the commercial license |
| Indemnified support | Oracle standing behind the database contractually | Worth paying for on the estate's critical core, not on every instance that happens to run MySQL |
The GPL fear is oversold for internal use. Running Community MySQL inside your own company, at any scale, for any workload, is what the license permits. The copyleft question is real only when MySQL ships inside something you distribute.
Buying subscriptions as copyleft insurance for internal workloads is the most common unforced purchase in the MySQL estate.
The paid editions, and the socket math that prices them
Three paid tiers: Standard, for basic commercial features, Enterprise, the tier most subscriptions land on, and Cluster CGE for the carrier grade cluster. All price per server per year by socket band, and the Enterprise pricing analysis carries the current per edition detail.
The socket construction rewards accuracy. Physical servers are unambiguous. Virtual estates are where quotes inflate: a VM reports vCPUs, not sockets, and the correct count is the underlying host's sockets applied per the subscription terms, not a thread count read as hardware.
In our reviews the vCPU misread was the largest single quote inflator, doubling the band on servers whose physical hosts sat comfortably at 1 to 4 sockets.
- 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
The overcounting problem, what the reviews actually found
Fredrik Filipsson ran roughly 15 to 25 Oracle commercial reviews touching MySQL between 2024 and 2026, and the repeating problem was never overuse. It was overcounting, in three forms:
More than half of subscribed servers loaded no Enterprise only plugin, the plugin table showing nothing beyond shipped defaults.
Guests reporting eight vCPUs priced into the 5 plus socket band at double the 1 to 4 socket rate.
The third form was subscription sprawl: coverage bought estate wide years ago for a project that needed Enterprise Backup on six servers, renewed annually ever since on all sixty.
The renegotiation artifact that beat all arguments was the per instance inventory: each paid server, the Enterprise features it actually loads, the sockets its physical host actually carries.
Servers loading nothing move to Community; servers miscounted move down a band; and the renewal prices what remains.
The Redress white paper library
150 plus buyer side negotiation and audit defense playbooks across Oracle and every major vendor, including the database estate playbooks the MySQL review sits inside.
Browse the library →The 8.0 support cliff, and what a renewal now buys
MySQL 8.0, still the deployed base in most estates, moved to Sustaining Support on April 21, 2026: no new fixes, no new security patches, existing knowledge base access only.
A per server subscription renewed on an 8.0 estate is buying markedly less than the same subscription bought a year earlier, and the renewal conversation should say so.
The buyer side sequencing: inventory which servers can move to the 8.4 LTS or later trains, price the subscription only for the servers that keep earning it after the upgrade plan, and use the cliff as the renegotiation moment for the whole MySQL line.
The same review naturally scopes the neighboring question of whether workloads belong on managed cloud MySQL, where the Oracle subscription question disappears entirely, and how the estate sits inside the wider Oracle database licensing position.
Your first five moves
- Query the plugin table on every subscribed server. The Enterprise features actually loaded, per instance, is the artifact the whole renegotiation stands on.
- Correct the socket math on virtual estates: physical host sockets per the terms, never vCPU counts, and move the misbanded servers down.
- Move the silent Community workloads off subscription, and keep paid coverage where Enterprise features or indemnity genuinely earn it.
- Answer the OEM question precisely. Distribution triggers the commercial license; internal use does not, at any scale.
- Use the 8.0 cliff as the renegotiation moment: upgrade plan first, then a subscription sized to the post upgrade estate. The Oracle practice runs the review with you, on your side of the table.
Frequently asked questions
Is MySQL free for commercial use?
MySQL Community Edition is free under the GPL for internal use at any scale, including commercial companies.
The paid obligation arises from three triggers: needing the Enterprise only features, embedding MySQL in a product you distribute, where the GPL's copyleft would reach your code, or wanting Oracle's indemnified support.
How much does MySQL Enterprise Edition cost?
List runs $5,350 per server per year at 1 to 4 sockets and $10,700 at 5 plus sockets, with Standard below and Cluster CGE above. Pricing is per server by socket count, not per core, which makes the socket arithmetic, especially on virtualized hosts, the most consequential number on the quote.
How is MySQL licensed on virtual machines?
By the underlying host's socket count per the subscription terms, not by the guest's vCPU count. The most common quote inflator in our reviews was a VM reporting eight vCPUs priced into the 5 plus socket band at double the rate, when the physical host sat at two sockets.
Do we need an Oracle subscription for MySQL on AWS, Azure, or Google Cloud?
No. Managed cloud MySQL, RDS, Aurora MySQL, Azure Database for MySQL, and Cloud SQL, is licensed through the cloud provider's service, and no separate Oracle MySQL subscription applies. Moving workloads to managed cloud is one of the standard ways the Oracle MySQL line shrinks at review.
When does embedding MySQL require a commercial license?
When you distribute a product with MySQL inside it. The GPL's copyleft terms would otherwise reach the distributing product's code, so ISVs and device makers buy the OEM commercial license. Internal use, however large, is not distribution and carries no such requirement.
What does the MySQL 8.0 support change mean for renewals?
MySQL 8.0 moved to Sustaining Support on April 21, 2026: no new fixes or security patches.
A subscription renewed on an unupgraded 8.0 estate buys materially less than before, which makes the cliff the natural moment to build the upgrade plan and resize the whole subscription against the servers that still earn it.
