MySQL and MariaDB Support Providers Compared (2026)

The short answer

MySQL 8.0 left Oracle Premier Support in April 2025, and Oracle moved it to Sustaining Support on 21 April 2026, which brings no new fixes. Percona, OpenLogic, TuxCare and OSSeva sell fixes for 8.0 itself, Amazon RDS does it inside RDS, Oracle sells support and an upgrade path, and MariaDB plc supports MariaDB. This list is alphabetical and was checked on each provider's own site on 30 October 2026. OSSeva publishes this guide and is one of the entries.

The providers at a glance

The dates that frame the choice

• MySQL 5.7: community end of life 31 October 2023, Oracle Sustaining Support from 25 October 2023.
• MySQL 8.0: Oracle Premier Support ended April 2025 and Extended Support April 2026. Oracle's EOL notice puts 8.0 in Sustaining Support from 21 April 2026; endoflife.date lists 30 April 2026. See MySQL 8.0 end-of-life dates.
• MySQL 8.4 and 9.7 LTS: Premier Support to April 2029 and April 2031, Extended Support to April 2032 and April 2034.
• MariaDB 10.6: community end of life 6 July 2026. See MariaDB 10.6 end-of-life dates.

Oracle's Lifetime Support Policy says Sustaining Support does not include new updates, fixes, security alerts, data fixes or critical patch updates. That is the gap the other providers here fill, or sidestep by moving you to a newer version.

Amazon RDS Extended Support

For databases on RDS for MySQL, AWS sells Extended Support past the RDS end of standard support. For 8.0 that date was 31 July 2026, with Extended Support from 1 August 2026 to 31 July 2029 and a higher price from 1 August 2028. It provides security updates for critical and high CVEs and critical bug fixes, and it costs extra. It applies only inside RDS. The RDS Extended Support comparison has the rates. Fits when: your MySQL runs on RDS and will stay there. Does not fit when: it runs on EC2, Kubernetes or your own hardware.

MariaDB plc

MariaDB plc sells MariaDB Enterprise Server subscriptions in two tiers, Standard and Premium, with 24x7 support for urgent issues. First response for Urgent issues is 30 minutes on Standard and 15 minutes on Premium. Its engineering policy gives Enterprise Server 10.6 standard support to 23 August 2027 and end of life on 23 August 2029, and says Extended Support is available for additional fees. Its page says support staff are experts in MariaDB as well as MySQL but does not list MySQL server versions. No prices are published. Fits when: your estate is MariaDB and you want the vendor that builds it. Ask first: whether MySQL 8.0 servers are in scope.

OpenLogic by Perforce

OpenLogic lists long-term support for MySQL 5.7 and 8.0 until 30 September 2028, covering CVSS 7 and higher. Its patch objectives are within 14 days of disclosure for critical (CVSS 9 and up) and within 30 days for high, offered as service level objectives rather than SLAs for MySQL. Premium LTS adds gold-level support with a one-hour response. Pricing is on request. See OSSeva compared with OpenLogic. Fits when: you also need LTS for other technologies on its list. Ask first: whether the service level is an objective or a contract term.

Oracle MySQL Enterprise Edition

Oracle writes MySQL and sells Enterprise Edition with 24x7 support, Enterprise Backup, Firewall, Audit and other components. Its price list of 11 September 2025 shows $5,350 per server per year for servers with one to four sockets and $10,700 for five or more. The catch for 8.0 is the Lifetime Support Policy: Sustaining Support brings no new fixes, so Oracle's route is an upgrade to 8.4 LTS or 9.7 LTS. The MySQL Enterprise Edition comparison has the details. Fits when: you can upgrade, or you depend on Enterprise-only components.

OSSeva

OSSeva ships patched, signed MySQL 5.7 and 8.0 Community builds after each quarterly Oracle update, on the same major version and data directory, and supports 8.4 and 9.7 LTS. For MariaDB it patches 10.4 to 10.6 and supports 10.11 to 12.3. Critical CVEs are patched within 48 hours and High within 7 days; Operate adds 24/7 operations with a 15-minute P1 response. Every engine runs self-managed: OSSeva does not host databases, and MySQL has no drop-in container images yet. The plan is priced per cluster. See MySQL 8.0 extended support and OSSeva for MySQL. Fits when: you run Community MySQL or MariaDB yourself and want fixes without a commercial MySQL license. Does not fit when: you need a hosted database or Oracle's Enterprise-only components.

Percona

Percona sells paid support for Percona Server for MySQL 8.0 for up to three years after end of life: expert-engineered fixes for detected, reproducible CVEs, reports on additional CVE testing, 24x7x365 monitoring and support, and SLAs as fast as 15 minutes for critical issues. Its page names Percona Server and does not say Oracle's MySQL builds are covered, and no price is published. See OSSeva compared with Percona. Fits when: you run or will move to Percona Server and want the vendor that builds it. Ask first: whether your exact distribution is in scope.

TuxCare

TuxCare's end-of-life applications page lists CVE patches for MySQL 8.0 and MariaDB 10.6, with MySQL 5.7 not listed, and says pricing is tailored on request. It is strongest on operating systems and runtimes; see OSSeva compared with TuxCare. Fits when: you already buy TuxCare for the operating system. Ask first: which minor versions and which fix timing apply.

Questions to ask any provider

1. Which exact version and distribution is covered? Oracle's MySQL, Percona Server and MariaDB are different builds.
2. Is the fix a patched build or advice to upgrade? Ask for a sample CVE record.
3. What is the fix time, and is it in the contract? Response time is not fix time.
4. Does coverage end on a stated date? RDS, MariaDB plc and OpenLogic publish one; ask the others.
5. Who operates it? Support, patching and 24/7 operations are separate products at some vendors.

Frequently asked questions

Who supports MySQL 8.0 after end of life?

Amazon RDS (inside RDS, to 31 July 2029), OpenLogic (LTS to 30 September 2028), Percona (up to three years, for Percona Server for MySQL 8.0), TuxCare (8.0 listed) and OSSeva (patched 8.0 builds). Oracle moved 8.0 to Sustaining Support on 21 April 2026, which includes no new fixes. Check the version, build and fix time with each provider.

Which providers cover both MySQL and MariaDB?

Percona lists both, TuxCare lists MySQL 8.0 and MariaDB 10.6, and OSSeva patches both. MariaDB plc supports MariaDB and describes its staff as experts in MySQL too; ask whether MySQL servers are in scope.

Do I need MySQL Enterprise Edition to get support?

No. MySQL Community Edition is free under the GPL, and Enterprise Edition is a commercial product that only Oracle sells. Percona, OpenLogic, TuxCare and OSSeva support Community or Percona builds without an Oracle license, and Oracle recommends upgrading to 8.4 LTS or 9.7 LTS. See the MySQL 8.0 options for upgrade, switch and patch compared.

Sources, checked 30 October 2026

• Amazon RDS: MySQL versions and release calendar
• MariaDB plc: support and engineering policies
• OpenLogic: long-term support
• MySQL: end-of-life notice and Oracle Lifetime Support Policy
• Percona: MySQL 8.0 end-of-life support and database support
• TuxCare: applications end-of-life support
• endoflife.date: MySQL and MariaDB