GridGain is an in-memory data grid and database built on Apache Ignite, for teams that need low-latency data at cluster scale. Part of MariaDB.
GridGain holds an application's working data in the RAM of many servers at once, so reads and writes do not wait on a disk-bound store. It is built on Apache Ignite and runs as a distributed cache, an in-memory data grid or an in-memory database, depending on how a team deploys it. GridGain Systems became a part of MariaDB in March 2026, and the homepage now presents the product as MariaDB GridGain. The platform ships in two generations, GridGain 8 and GridGain 9, each in Community, Enterprise and Ultimate editions. Data is partitioned across server nodes in a balanced way, so capacity grows by adding machines. Native persistence appends every update to a write-ahead log and keeps the full dataset on disk, with memory holding the hot set. Full and incremental snapshots and point-in-time recovery cover backup and restore. Caches take expiry policies and Random-LRU eviction, SQL APIs define indexes on stored fields, and publish-subscribe messaging passes topics between nodes. Control Center is the operations console, with a cluster dashboard, an SQL explain tool, request tracing and a snapshot list. The platform suits enterprises whose applications need low-latency access to large datasets, from real-time analytics and hybrid transactional and analytical processing to high-performance computing. Teams already running open-source Apache Ignite get a commercial path, either by moving to an edition with support or by attaching their clusters to GridGain Nebula for monitoring. Buyers choose between running the software on their own infrastructure and handing cluster operations to Nebula, which provisions and runs managed clusters. Organisations running IBM z/OS have GridGain for z/OS. Most deployments start as a cache in front of a slower system of record and grow into a digital integration hub that serves several applications from one in-memory layer. Change feeds arrive through the Kafka sink connector in GridGain 9 or through Debezium change data capture, which keeps the in-memory copy current as source databases change. Analysts and reporting tools reach the same data over JDBC and ODBC, while Spring applications work with it directly. For a team whose bottleneck is the database round trip, GridGain becomes the layer that answers first.
Pricing
View plans-
Nebula Managed Cluster S
Custom pricing
- $1.98 per cluster per hour, billed by usage
- For a high-speed cache or a development sandbox
- 4 CPU, 30.5 GB RAM, 16 GB off-heap storage, 400 GB SSD
- Cluster size cannot be changed once provisioned
-
Nebula Managed Cluster M
Custom pricing
- $3.96 per cluster per hour, billed by usage
- For larger caching and compute workloads
- 8 CPU, 61 GB RAM, 32 GB off-heap storage, 800 GB SSD
- Cluster size cannot be changed once provisioned
-
Nebula Managed Cluster L
Custom pricing
- $7.92 per cluster per hour, billed by usage
- For high-traffic applications and large storage
- 16 CPU, 122 GB RAM, 64 GB off-heap storage, 1600 GB SSD
- Cluster size cannot be changed once provisioned
-
Nebula Attached Cluster, Apache Ignite
Custom pricing
- $0.11 per server node per hour, billed at the largest cluster size in the hour
- Monitoring of an Apache Ignite cluster on your own hardware
- 3 GB monitoring storage per server node
- Client nodes are not counted
Features
- Included: Rich data structures beyond strings
- Included: Per-key expiration and eviction policies
- Included: Snapshot persistence to disk
- Included: Append-only log persistence
- Not included: Replica failover with automatic promotion
- Included: Horizontal clustering of the keyspace
- Not included: Active-active geo replication
- Included: Pub/sub messaging channels
- Not included: Atomic server-side scripting
- Included: SSD tiering beyond available RAM
- Included: Secondary indexes on stored values
- Not included: Native JSON value type
- Included: Multi-threaded request handling
- Not included: Per-user command and key ACLs
- Included: Client-side caching invalidation
- Not included: Streams with consumer groups
- Not included: Keyspace memory reporting
Additional Features
- Native persistence with a write-ahead log
- Full and incremental snapshots
- Point-in-time recovery
- Data partitioning across server nodes
- Expiry policies and Random-LRU eviction
- SQL indexes on stored fields
- JDBC and ODBC drivers
- Publish-subscribe messaging between nodes
Best for
- Enterprises that need low-latency access to large datasets
- Teams already running Apache Ignite clusters
- Teams that want Ignite as a managed service through Nebula
- Architects building a digital integration hub
- Real-time analytics and HTAP workloads
- High-performance computing on in-memory data
- Mainframe teams on IBM z/OS
Use cases
- Caching data in front of a disk-based database
- Running an in-memory data grid across a cluster
- Using an in-memory database with SQL queries
- Building a digital integration hub
- Real-time analytics on operational data
- High-performance computing on in-memory data
- Monitoring Apache Ignite clusters with Nebula
- Loading changes from Kafka or Debezium
- Restoring a cluster to a point in time from snapshots
- Explaining and tracing SQL queries in Control Center
Screenshots & Videos
Explore GridGain in action
User Reviews
Compare with Similar Software
Click to compare side by side with GridGain