MariaDB Launches Enterprise Platform 2027 for Agent Workloads

MariaDB announced Enterprise Platform 2027 on November 4, 2026, making its combined transactional, analytics, in-memory and AI platform generally available. The release adds agent memory, retrieval and response-caching tools, and the company reported 56% higher peak throughput for Enterprise Server 12.3 than version 11.8 in sponsored testing.

The release packages Enterprise Server 12.3 with Exa, GridGain, MaxScale, Enterprise Manager and the Enterprise Kubernetes Operator. It can run on premises, in any cloud or as a managed MariaDB Cloud service. A redesigned logo, color palette and website accompany MariaDB’s effort to position itself as a unified data platform rather than only an operational database.

Agent Tools Use the Same Live Data

A launch post divides the agent features into development and runtime functions. Agent Memory stores an agent’s state in memory after every step and shares it across agents and sessions. An agent paused for human approval or interrupted can resume from its saved state rather than restart; LangGraph is supported out of the box.

Semantic Cache addresses repeated model calls by recognizing when a differently worded question has the same meaning as an earlier one and returning the stored response. MariaDB says this can shorten response times and reduce token costs for applications whose users ask similar questions.

AI Retrieval provides one managed retrieval layer across documents and live operational data. It parses, chunks, embeds and reranks documents, while natural-language questions about MariaDB data become read-only SQL queries against the live database. Follow-up questions retain earlier context. The design is intended to ground answers without maintaining separate warehouse or vector-store copies and their security controls.

The open-source AI Plugins supply MariaDB-specific guidance to coding agents. They support Claude Code, Codex, OpenCode and Pi.

Analytics, Clustering and Deployment Controls

MariaDB Exa is now generally available on premises, running real-time analytics directly against live operational data without a separate warehouse or ETL pipeline. Vector search remains native to the core database engine; MariaDB reports up to 30% more vector queries per second than Enterprise Server 11.8 at the same accuracy, with no schema or query changes.

For multi-region deployments, the generally available Raft Cluster commits a write after a majority of nodes confirm it, preventing one slow or distant node from setting the pace for every write. Conflict detection and resolution let each region serve local updates, with customer-defined business rules settling cases where two sites change the same record.

Enterprise Manager combines the database, MaxScale and GridGain in one observability console with single sign-on. Bring Your Own Cloud is also generally available: the MariaDB Cloud data plane runs inside a customer’s AWS, Microsoft Azure or Google Cloud account while MariaDB operates the database.

Role-based access controls apply across transactional, analytical and vector workloads. FIPS 140-3 support is enabled through the Enterprise Kubernetes Operator using NIST-validated cryptographic modules from Red Hat.

Benchmark Conditions Define the Performance Claim

The October 2026 McKnight Consulting Group report behind the headline throughput figure measured 2,653,370 new orders per minute for Enterprise Server 12.3.3-0 at its peak, compared with 1,702,758 for 11.8.3-1. Version 12.3 peaked at 152 virtual users; version 11.8 peaked at 88. At those respective peaks, 99th-percentile New Order response times were 3.60 milliseconds and 6.54 milliseconds.

Both versions ran separately on the same Google Cloud c4d-highmem-192-lssd instance with 96 physical cores and 192 vCPUs. The in-memory HammerDB TPROC-C workload used 768 warehouses and was derived from TPC-C, but was not an official TPC-C result.

Those controls isolate engine scalability, but other choices limit how directly the numbers transfer to production. Durable commits, binary logging and doublewrite buffering were disabled. MariaDB selected its own configurations, while McKnight chose the tests, configured the databases and testing applications, and ran the tests.

Enterprise Platform 2027 ties MariaDB’s agent strategy to fewer data copies, shared access controls and common operational infrastructure. Its published performance evidence supports higher throughput under the disclosed test conditions; the production question is how the combined platform performs when durability, workload mix and regional requirements differ from that controlled environment.