Who Provides Extended Support for Apache Ignite 2.x and Ignite 3?

The short answer

Two companies publish support for Apache Ignite. GridGain, whose engineers contribute to Ignite, sells support for Ignite and for its own GridGain editions: GridGain 8, which pairs with Ignite 2, and GridGain 9, which pairs with Ignite 3. OSSeva ships patched builds of Apache Ignite 2.8, 2.9, 2.13 and 2.16 with the API and storage format unchanged, for clusters that cannot move to a newer 2.x release or to Ignite 3.

The deciding question is whether you will move to GridGain's commercial editions or stay on the Apache Ignite release you run. GridGain's published support packages list GridGain Enterprise and Ultimate Edition as the supported products.

Where Apache Ignite stands

The Ignite project does not publish an end-of-life date for any line. Fixes ship in new releases, and older 2.x lines do not receive patch releases, so a fix for 2.13 or 2.16 means moving to a newer minor.

Ignite 3 is not an in-place upgrade from 2.x. Applications written against the 2.x cache and compute APIs have to be ported, and data has to be migrated. The Ignite release chart tracks every line, and Ignite vulnerabilities by version shows which advisories reach older releases.

Apache Ignite support providers compared

Each row reflects what the provider publishes on its own site as of 6 October 2026.

GridGain's support lifecycle gives each minor version at least two years of standard support, and after that no new releases or patches. Perforce OpenLogic and HeroDevs are not in the table because neither lists Ignite in its published catalogue; HeroDevs covers Hazelcast instead.

How the providers differ

GridGain

GridGain is the right call when you want support from the people who build Ignite, and you are prepared to run GridGain's editions. Its support page is titled for both Apache Ignite and GridGain, and its engineers contribute to Ignite. The published packages list GridGain Enterprise and Ultimate Edition, so expect the commercial path to involve moving onto GridGain 8.9 or 9.1 rather than keeping a community 2.13 build. Ask GridGain directly what it offers for a cluster that stays on Apache Ignite binaries.

OSSeva

OSSeva for Apache Ignite patches the 2.x line in place, so the cache API, persistence format and client protocol your applications use do not change. That matters for Ignite more than for most data stores, because the compute grid runs user code on every node, so a weakness in discovery or node authentication can become cluster-wide code execution. Coverage includes native persistence as well as in-memory caches. Assure adds a baseline topology review, a discovery port exposure audit, an inventory of cache and compute API usage and an Ignite 3 migration assessment with an effort estimate. Operate adds 24/7 heap, off-heap and topology monitoring, a 15-minute P1 response, checkpointing, WAL and rebalance tuning, and migration execution to Ignite 3 or another grid. Pricing is per cluster, not per node or gigabyte.

How to choose

If the estate is mostly distributed caching, Ignite 3 may not be the shortest path. Our Ignite 2 to 3 migration guide covers the port, and OSSeva also supports Hazelcast and GemFire and Geode, so the comparison can cover all three.

Where OSSeva fits

OSSeva keeps Apache Ignite 2.x clusters patched on the release they run, and can operate them while the Ignite 3 or alternative-grid decision is made. See Ignite 2.x extended support for the offer and the extended support vendor roundup for how OSSeva compares across other technologies.

Frequently asked questions

Who provides extended support for Apache Ignite?

GridGain sells support for Apache Ignite and its GridGain editions, with GridGain 8.9 and 9.1 in standard support. OSSeva ships patched Apache Ignite 2.8, 2.9, 2.13 and 2.16 builds with the API and storage format unchanged.

Is Apache Ignite 2.x still supported?

The 2.x line still gets new releases, most recently 2.18.0 in 2026. Older 2.x minors do not get patch releases, and the project publishes no support window, so staying on 2.13 or 2.16 means relying on a vendor for fixes.

What is the difference between GridGain and Apache Ignite?

Ignite is the Apache open source project. GridGain sells commercial editions and support, with GridGain 8 aligned to Ignite 2 and GridGain 9 aligned to Ignite 3, and its engineers contribute to Ignite.

Can we upgrade from Ignite 2 to Ignite 3 in place?

No. Ignite 3 replaced the storage engine, SQL engine, client protocol and configuration model, so code has to be ported and data migrated. Plan it as a migration project.

Does OpenLogic support Apache Ignite?

Ignite does not appear in OpenLogic's published list of supported technologies. OpenLogic does list GemFire.