MySQL Enterprise Edition is the commercial distribution of MySQL. It includes the open source MySQL server plus a set of commercial features delivered through Oracle Lifetime Support, including MySQL Enterprise Backup, Monitor, Audit, Firewall, Transparent Data Encryption, Thread Pool, and Authentication. The commercial features are not available in MySQL Community Edition, which is free under the GPL.
Oracle sells MySQL Enterprise through three commercial subscription tiers. MySQL Standard Edition Subscription, MySQL Enterprise Edition Subscription, and MySQL Cluster CGE Subscription. Each tier is priced per server, with a separate price for unlimited cores and limited core servers. Pricing escalates with the size of the server and the level of support.
Oracle also sells HeatWave, an in memory analytics accelerator that runs alongside MySQL. HeatWave is priced separately, in OCPUs, on a consumption or subscription basis. The HeatWave attach rate is one of the levers Oracle pushes hardest on in MySQL renewals.
Edition tier. The default Oracle proposal is Enterprise Edition. Many workloads sit happily on Standard Edition, which is less than half the list price. We test the feature requirement against the tier requirement and recommend the tier that matches.
Server count basis. MySQL Enterprise is priced per server. The definition of a server in the order document determines whether your virtualised environment counts as one server or many. We tighten the definition.
HeatWave attach. Oracle pushes HeatWave aggressively at renewal as an add on. If your workload does not need in memory analytics, refuse the attach and protect against future bundling.
Cloud parity. MySQL HeatWave Service on OCI is priced in cloud terms while on premises MySQL Enterprise is priced per server. We negotiate parity language that lets you move workloads between on premises and OCI without paying twice.
Renewal escalation. The standard renewal language uplifts the fee by up to four per cent per year. Negotiable to CPI capped at three.
Audit rights. MySQL audits are increasing in frequency. The audit clause in the MySQL subscription agreement can be tightened to a defined scope, a defined frequency, and a buyer funded audit if no shortfall is found.
For broader MySQL licensing context see our MySQL product page.
Because we work for buyers only and never recommend Oracle products by default, every MySQL Enterprise engagement begins with a needs assessment that compares Oracle MySQL Enterprise against the realistic alternatives. The alternatives that come up most often are AWS Aurora MySQL, PlanetScale, MariaDB Enterprise, Percona, and Google Cloud SQL for MySQL.
For workloads that need the MySQL Enterprise features list, the alternatives are limited and we will typically recommend continuing with Oracle MySQL Enterprise at a renegotiated price. For workloads that use Community Edition features only and have selected Enterprise primarily for support, the alternatives are usually competitive on price and capability.
The deliverable on a typical engagement is a head to head comparison with a five year total cost of ownership model and a recommended path. If the path is to stay with Oracle, we then negotiate the renewal. If the path is to migrate, we coordinate the migration RFP and the Oracle exit.
The most common trigger is a MySQL renewal that includes an unexpected price increase or a HeatWave attach. The second most common trigger is a soft audit on MySQL Enterprise where Oracle has identified deployments in non production environments not covered by the subscription. The third is a cloud migration where Oracle is offering MySQL HeatWave Service as the destination.
In all three scenarios we engage within five business days and deliver a counter offer or a defence position within three to four weeks. To start, complete the form below.
Renewal negotiation covers full MySQL Enterprise renewal work. Audit defense covers MySQL audit response. Cloud migration advisory covers HeatWave Service and OCI MySQL deals. For research dossiers see the Negotiation Playbook. For related field notes see database negotiation.