By continuing to browse or by clicking “Accept All Cookies,” you agree to the storing of first- and third-party cookies on your device to enhance site functionality, analyze site usage, and assist in our marketing efforts. Cookie Policy.

Accept All Cookies

Hazelcast IMDG Hazelcast Jet Blog Training Hazelcast.com

Download Deploy in Cloud Contact Us

Get Hazelcast Enterprise

Download Hazelcast IMDG Open Source
from hazelcast.org

Download Hazelcast Jet Open Source
from jet.hazelcast.org

What's the difference?

Hazelcast IMDG Annual Subscription Plans

Pricing		Hazelcast IMDG Enterprise HD	Hazelcast IMDG Enterprise	Hazelcast IMDG Professional Support
Annual Price Per Node A Hazelcast node is a JVM on which an instance of Hazelcast is in operation: There is no charge per CPU or CPU core. The charge is based on the number of JVMs. Minimum purchase is 3 nodes. Which nodes count as Hazelcast nodes? The node count is calculated as the number of JVMs which are running a Hazelcast instance. An instance may be run on its own from the command line (server) or started from within in an application server (embedded). It is also possible to run multiple Hazelcast instances in one JVM. Multiple instances running in one JVM count as one node. A production node or hot-standby node or warm-standby node is a JVM where the Hazelcast software is running. These are counted. Non-production nodes include cold standby (power is off), or QA, Test and Dev nodes. These are not counted. Contact us for microservices pricing option. A Hazelcast node is a JVM on which an instance of Hazelcast is in operation: There is no charge per CPU or CPU core. The charge is based on the number of JVMs. Minimum purchase is 3 nodes. Which nodes count as Hazelcast nodes? The node count is calculated as the number of JVMs which are running a Hazelcast instance. An instance may be run on its own from the command line (server) or started from within in an application server (embedded). It is also possible to run multiple Hazelcast instances in one JVM. Multiple instances running in one JVM count as one node. A production node or hot-standby node or warm-standby node is a JVM where the Hazelcast software is running. These are counted. Non-production nodes include cold standby (power is off), or QA, Test and Dev nodes. These are not counted. Contact us for microservices pricing option. Hazelcast offers competitive pricing. We also have an OEM program. Please Contact Us for a quote.		Hazelcast offers competitive pricing. We also have an OEM program. Please Contact Us for a quote.
Feature Comparison
Service & Support Support Window Service-level Agreement HD: 24x7 support window, 1hr Service-Level Agreement E: 24x7 support window, 1hr Service-Level Agreement P: 24x7 support window, 2hr Service-Level Agreement Quarterly Review of Feature Requests HD E P Quarterly Review of the Hazelcast Roadmap HD E P Email, IM, phone support contacts HD: 30 E: 30 P: 5 Access to Hot Fix Patches HD E P Simulation of your production Hazelcast profile for upgrade/config change verification HD E P Black Duck Clean IP Report HD E P	Support Window Service-level Agreement	24x7 support window, 1hr Service-Level Agreement	24x7 support window, 1hr Service-Level Agreement	24x7 support window, 4hr Service-Level Agreement
	Quarterly Review of Feature Requests
	Quarterly Review of the Hazelcast Roadmap
	Email, IM, phone support contacts	30	30	5
	Access to Hot Fix Patches
	Simulation of your production Hazelcast profile for upgrade/config change verification
	Black Duck Clean IP Report

Click here for a product feature comparison »

Next Steps:

Legend:

HD = Hazelcast Enterprise HD
E = Hazelcast Enterprise
P = Hazelcast Professional Support