MariaDB announced general availability of Enterprise Platform 2027 on November 4, 2026. The release includes Enterprise Server 12.3 and other platform components. MariaDB says its managed AI Retrieval feature is scheduled for public preview on MariaDB Cloud later in November. If your team needs both, write two test plans so the database upgrade does not depend on a feature that is still due to enter preview.
Test the database change against your own workload
Start with an isolated copy that reflects your current database version, configuration and application queries. Record a baseline for a short list of tasks, such as reading a product record or writing an order. On the new version, repeat the tasks and check that the results, error handling and recovery procedure still meet your requirements. A vendor throughput result cannot tell you how your own workload will behave.
Give the retrieval preview its own acceptance checks
MariaDB describes AI Retrieval as combining documents and live operational data and translating natural-language questions into read-only SQL. Read-only access prevents a query from changing rows, but a read can still return information the person asking should not see. If you join the preview, start with synthetic or approved test data and a narrowly scoped account. Verify what the system returns when asked about records outside that account’s intended scope.
For example, build a fictional order dataset and a separate returns policy document. Ask for the current policy, then ask for the status of one permitted order. Check the answers against both sources. Add a third question about an order the account should not be able to read and record what actually happens. Keep the preview results separate from the decision to upgrade the database.
Check the rollout plan
Source
MariaDB’s November 4 platform announcement and availability details