MariaDB Enterprise Server enhances the community version with advanced features, security, high availability, support, and tools for enterprise use.
Procedures are provided to download, install, set-up, configure, and test MariaDB products.
Upgrade instructions are also available.
MariaDB products can be deployed in many different topologies. The topologies on this page are representative. MariaDB products can be deployed to form other topologies, leverage advanced product capabilities, or combine the capabilities of multiple topologies.
• Primary/Replica Topology
• MariaDB Replication• Highly available• Asynchronous or semi-synchronous replication• Automatic failover via MaxScale• Manual provisioning of new nodes from backup• Scales reads via MaxScale• Enterprise Server 10.3+, MaxScale 2.5+
• Galera Cluster Topology
• Galera Cluster Topology Multi-Primary Cluster Powered by Galera for Transactional/OLTP Workloads• InnoDB Storage Engine• Highly available• Virtually synchronous, certification-based replication• Automated provisioning of new nodes (IST/SST)• Scales reads via MaxScale Enterprise Server 10.3+, MariaDB Enterprise Cluster (powered by Galera), MaxScale 2.5+
• ColumnStore Object Storage Topology
• Columnar storage engine with S3-compatible object storage• Highly available• Automatic failover via MaxScale and CMAPI• Scales reads via MaxScale• Bulk data import• Enterprise Server 10.5, Enterprise ColumnStore 5, MaxScale 2.5• Enterprise Server 10.6, Enterprise ColumnStore 23.02, MaxScale 22.08
• ColumnStore Shared Local Storage Topology
• Columnar storage engine with shared local storage • Highly available• Automatic failover via MaxScale and CMAPI• Scales reads via MaxScale• Bulk data import• Enterprise Server 10.5, Enterprise ColumnStore 5, MaxScale 2.5• Enterprise Server 10.6, Enterprise ColumnStore 23.02, MaxScale 22.08
• HTAP Topology
• Single-stack hybrid transactional/analytical workloads• ColumnStore for analytics with scalable S3-compatible object storage• InnoDB for transactions• Cross-engine JOINs• Enterprise Server 10.5, Enterprise ColumnStore 5, MaxScale 2.5• Enterprise Server 10.6, Enterprise ColumnStore 23.02, MaxScale 22.08
• Spider Federated Topology
• Read from and write to tables on remote ES nodes• Spider Node uses Spider storage engine for Federated Spider Tables• Federated Spider Table is a "virtual" table• Spider uses MariaDB foreign data wrapper to query Data Table on Data Node• Data Node uses non-Spider storage engine for Data Tables• Supports transactions• Enterprise Server 10.3+, Enterprise Spider
• Spider Sharded Topology
• Shard tables for horizontal scalability• Spider Node uses Spider storage engine for Sharded Spider Tables• Sharded Spider Table is a partitioned "virtual" table• Spider uses MariaDB foreign data wrapper to query Data Tables on Data Nodes for each partition• Data Node uses non-Spider storage engine for Data Tables• Supports transactions• Enterprise Server 10.3+, Enterprise Spider
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB Enterprise Server is a premium version of MariaDB Community Server that focuses on stability, robustness, and predictability. For more information about MariaDB Enterprise Server in general please look here.
MariaDB Enterprise Server enables a predictable development and operations experience through an enterprise lifecycle. This enterprise lifecycle incorporates optimized builds, predictable release behavior, and vendor support. For more information about the Enterprise Server Lifecycle look here.
In addition to different release cycle, QA, and etc..., there are also feature differences. MariaDB Enterprise Server has different default settings to be more secure from the start and also only includes features that are fully supported and maintained.
In addition to this there are Enterprise Features and some backported features. The following are features that are in MariaDB Enterprise Server 10.4 but not in MariaDB Community Server 10.4:
Enterprise Features:
Index limit increased to 128 indexes
Slow master shutdown as default
MariaDB Enterprise Cluster (powered by Galera)
Backported Features:
New option --require_secure_transport
GTID support for MariaDB Enterprise Cluster (powered by Galera)
Crash recovery for semi-synchronous replication
mariadb-dump option --as-of to dump data as of a given time for system versioned tables
JSON functions
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB Enterprise Server is a premium version of MariaDB Community Server that focuses on stability, robustness, and predictability. For more information about MariaDB Enterprise Server in general please look here.
MariaDB Enterprise Server enables a predictable development and operations experience through an enterprise lifecycle. This enterprise lifecycle incorporates optimized builds, predictable release behavior, and vendor support.
In addition to different release cycle, QA, and etc..., there are also feature differences. MariaDB Enterprise Server has different default settings to be more secure from the start and also only includes features that are fully supported and maintained.
In addition to this there are Enterprise Features and some backported features. The following are features that are in MariaDB Enterprise Server 10.5 but not in MariaDB Community Server 10.5:
Enterprise Features:
Index limit increased to 128 indexes
Slow master shutdown as default
MariaDB Enterprise Cluster (powered by Galera)
Non-Blocking operation for DDLs
Dynamic resize of InnoDB redo log
Dynamic change of InnoDB purge threads
Sybase SQL mode for extended aliases
Backported Features:
Crash recovery for semi-synchronous replication
mariadb-dump option --as-of to dump data as of a given time for system versioned tables
Option for SQL thread to limit maximum execution time per query
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB Enterprise Server is a premium version of MariaDB Community Server that focuses on stability, robustness, and predictability. For more information about MariaDB Enterprise Server in general please look here.
In addition to different release cycle, QA, and etc..., there are also feature differences. MariaDB Enterprise Server has different default settings to be more secure from the start and also only includes features that are fully supported and maintained.
In addition to this there are Enterprise Features and some backported features. The following are features that are in MariaDB Enterprise Server 10.6 but not in MariaDB Community Server 10.6:
Enterprise Features:
Index limit increased to 128 indexes
Slow master shutdown as default
MariaDB Enterprise Cluster (powered by Galera)
XA Support
Non-Blocking operation for DDLs
TLS certificate expiration monitoring
SSL/TLS enabled by default
Dynamic resize of InnoDB redo log
Dynamic change of InnoDB purge threads
Sybase SQL mode for extended aliases
Backported Features:
mariadb-dump option --as-of to dump data as of a given time for system versioned tables
CONVERT_PARTITION / CONVERT_TABLE
Option for SQL thread to limit maximum execution time per query
Allow innodb_undo_tablespaces to be changed after database creation
Make the optimizer handle UCASE(varchar_col)=...
Easier way to retrieve all users that have privileges on a specific table
Make s3_debug dynamic
Add timezone information to DATE_FORMAT
Autoshrink option for innodb_data_file_path
system variable
New, Detailed Replication Lag Representation
New Information Schema Table For Password Related Data
GTID binlog events now include the thread ID
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB Enterprise Server is a premium version of MariaDB Community Server that focuses on stability, robustness, and predictability. For more information about MariaDB Enterprise Server in general please look here.
In addition to different release cycle, QA, and etc..., there are also feature differences. MariaDB Enterprise Server has different default settings to be more secure from the start and also only includes features that are fully supported and maintained.
In addition to this there are Enterprise Features and some backported features. The following are features that are in MariaDB Enterprise Server 11.4 but not in MariaDB Community Server 11.4:
Enterprise Features:
Index limit increased to 128 indexes
Slow master shutdown as default
MariaDB Enterprise Cluster (powered by Galera)
XA Support
Non-Blocking operation for DDLs
TLS certificate expiration monitoring
SSL/TLS enabled by default
Dynamic resize of InnoDB redo log
Dynamic change of InnoDB purge threads
Sybase SQL mode for extended aliases
Backported Features:
New, Detailed Replication Lag Representation
New Information Schema Table For Password Related Data
GTID binlog events now include the thread ID
Automatic SST user account management for Galera
PARSEC authentication plugin
Extending timestamp range to 2106
Limit size of created disk temporary files and tables
This page is: Copyright © 2025 MariaDB. All rights reserved.
Data-at-rest encryption secures data on the file system.
MariaDB Enterprise Server and MariaDB Community Server support data-at-rest encryption, which secures data on the file system. The server and storage engines encrypt data before writing and decrypt it during reads, ensuring that the data is only unencrypted when accessed directly through the server.
Encryption Plugins
HashiCorp Vault
Amazon Web Services (AWS) KMS
File Key Management
Binary Logs
Additional information is available on the MariaDB documentation.
MariaDB Enterprise Server and MariaDB Community Server support data-at-rest encryption, which secures data on the file system. The server and storage engines encrypt data before writes and decrypt it during reads, ensuring that the data is only unencrypted when accessed directly through the server.
In many versions of MariaDB Server, the GCache used by Galera Cluster does not support data-at-rest encryption.
However, MariaDB Enterprise Server 10.4 and later support an enterprise version of Galera 4, which adds support for encrypting the GCache.
In those versions, the GCache supports the following data-at-rest encryption features:
The GCache can be automatically encrypted.
For more information, see the following resources:
Enabling GCache Encryption
Disabling GCache Encryption
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB's encryption plugins provide transparent data encryption (TDE) for stored data, securing tablespaces and logs to protect sensitive information and meet compliance.
The AWS KMS Encryption Plugin (aws_key_management) integrates with Amazon Web Services (AWS) KMS.
The AWS KMS Encryption Plugin (aws_key_management) allows you to:
Use AWS KMS to manage MariaDB's encryption keys.
Encrypt MariaDB data using those keys, including:
Rotate encryption keys.
Additional information is available here.
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB Enterprise Server and MariaDB Community Server support data-at-rest encryption, which secures data on the file system. The server and storage engines encrypt data before writing and decrypt during reads, ensuring that the data is only unencrypted when accessed directly through the server.
They support multiple encryption plugins, which are suited for different use cases.
• It integrates with HashiCorp Vault • It supports key rotation • It securely communicates with the remote KMS using TLS.
• It integrates with AWS KMS. • It supports key rotation. • It must be compiled from source.
• stores encryption keys in a local plain-text key file. • The plain-text key file can be encrypted. • It does not support key rotation.
Supported by MariaDB Enterprise Server
Yes
Yes
Yes
Supported by MariaDB Community Server
No
Yes
Yes
Supports key rotation
Yes
Yes
No
This page is: Copyright © 2025 MariaDB. All rights reserved.
MariaDB Enterprise Server and MariaDB Community Server support data-in-transit encryption, which secures data transmitted over the network. The server and clients encrypt data using the Transport Layer Security (TLS) protocol, a newer version of the Secure Socket Layer (SSL) protocol.
Additional information is available on the MariaDB documentation.