Supported environments
The supported environments page lists browsers, operating systems, clients, deployment options, and component requirements, which are tested and supported for compatibility with Camunda 8.
If the particular technology is not listed, we cannot resolve issues caused by the usage of that unlisted technology.
You may raise a feature request that will be evaluated by our product teams to provide official support from Camunda, or you can make a help request to work with Consulting services.
Recommendations are denoted with [recommended], however, other listed options are supported as well.
The versions listed on this page are the minimum version required if appended with a +.
Pay attention to where the + falls, as most of our dependencies follow semantic versioning (semver), where x.y.z correspond to MAJOR.MINOR.PATCH. Higher or more recent versions will be compatible with Camunda, with respect to semver.
For example, 1.2+ means support for the minor version 2, and any higher minors (1.3, 1.4, etc.) and patches (1.2.1, 1.2.2, etc.), but not majors, like 2.x.
Web Browser
- Google Chrome latest [recommended]
- Mozilla Firefox latest
- Microsoft Edge latest
Desktop Modeler
- Windows 10 / 11
- macOS 13 / 14 / 15
- Ubuntu LTS (latest)
Clients
- Zeebe Java Client: OpenJDK 8+
- Spring Zeebe SDK: OpenJDK 17+
- Connector SDK: OpenJDK 17+
- Spring SDK: Check the version matrix
- Helm CLI: 3.14.x (for the exact version, check the version matrix.)
Camunda 8 Self-Managed
We recommend running Camunda 8 Self-Managed in a Kubernetes environment. We provide officially supported Helm Charts for this. Please follow the Installation Guide to learn more about installation possibilities.
Deployment options
With the right configuration, Camunda 8 Self-Managed can be deployed on any Certified Kubernetes distribution (cloud or on-premises). However, we officially test and support a specific list of platforms.
The following are tested and supported deployment options for Kubernetes, Docker, and manual installation:
- Stock Kubernetes
- Cloud service providers [recommended]
- Red Hat OpenShift
- Docker (
linux/amd64) - Manual
Ensure the Camunda component versions are compatible with the Helm chart version as defined in the matrix.
Sizing
The sizing of a Camunda 8 installation depends on various influencing factors. Ensure to determine these factors, and conduct benchmarking to validate an appropriate environment size for your test, integration, or production environments.
Volume performance
As a minimum requirement, the persistent volumes for Zeebe should use volumes with an absolute minimum of 1,000 IOPS. NFS or other types of network storage volumes are not supported.
To ensure an appropriate sizing, determine your influencing factors (e.g., throughput), and conduct benchmarking to validate an appropriate environment sizing.
For details on typical volume type usage, refer to the following examples specific to cloud service providers:
Helm charts version matrix
Camunda Helm chart version 12.x.x works with Camunda version 8.7.x. Check the Helm chart version matrix for more details.
Component requirements
Requirements for the components can be seen below:
| Component | Java version | Other requirements |
|---|---|---|
| Zeebe | OpenJDK 21+ | Elasticsearch 8.13+ Amazon OpenSearch 2.9+ (requires use of OpenSearch exporter) |
| Operate | OpenJDK 21+ | Elasticsearch 8.13+ Amazon OpenSearch 2.9+ |
| Tasklist | OpenJDK 21+ | Elasticsearch 8.13+ Amazon OpenSearch 2.9+ |
| Identity | OpenJDK 17+ | Keycloak 25.x, 26.x PostgreSQL 14.x, 15.x or Amazon Aurora PostgreSQL 13.x, 14.x, 15.x (required for certain features) |
| Optimize | OpenJDK 21+ | Elasticsearch 8.13+ Amazon OpenSearch 2.9+ |
| Connectors | OpenJDK 21+ | |
| Web Modeler | - | PostgreSQL 13.x, 14.x, 15.x, 16.x, 17.x or Amazon Aurora PostgreSQL 13.x, 14.x, 15.x, 16.x |
| Console | - | - |
*Not all Optimize features are supported when using OpenSearch as a database. For a full list of the features that are currently supported, refer to the Camunda 8 OpenSearch features.
When running Elasticsearch, you must have the appropriate Elasticsearch privileges.
When running Amazon OpenSearch 2.11 or higher, we do not support OR1 instances due to the limitation for the index refresh interval. More information on configuring Amazon OpenSearch can be found here.
Camunda 8 works with the default distribution of Elasticsearch, which is available under the Free or Gold+ Elastic license.
Component version matrix
The following matrix shows which component versions work together.
From version 8.6.0 forward, Zeebe, Operate, and Tasklist must run on on the exact same minor and patch level to ensure compatibility.
| Design | Automate | Improve |
|---|---|---|
| Desktop Modeler 5.31+ Web Modeler 8.7.x | (Zeebe, Operate, Tasklist) 8.7.x, Connectors 8.7.x, Identity 8.7.x, Console 8.7.x, RPA worker 1.0+ | Optimize 8.7.x |
| Desktop Modeler 5.28+ Web Modeler 8.6.x | (Zeebe, Operate, Tasklist) 8.6.x, Connectors 8.6.x, Identity 8.6.x, Console 8.6.x | Optimize 8.6.x |
| Desktop Modeler 5.22+ Web Modeler 8.5.x | Zeebe 8.5.x, Operate 8.5.x, Tasklist 8.5.x, Identity 8.5.x, Connectors 8.5.x, Console 8.5.x | Optimize 8.5.x |
| Desktop Modeler 5.19+ Web Modeler 8.4.x | Zeebe 8.4.x, Operate 8.4.x, Tasklist 8.4.x, Identity 8.4.x, Connectors 8.4.x | Optimize 8.4.x |
| Desktop Modeler 5.16+ Web Modeler 8.3.x | Zeebe 8.3.x, Operate 8.3.x, Tasklist 8.3.x, Identity 8.3.x, Connectors 8.3.x | Optimize 8.3.x |
You can also use newer versions of Desktop and Web Modeler with older Zeebe versions.
Dependency maintenance policies
Camunda provides a standard support policy of 18 months for a particular minor version from the date it is released. During this time, patches are regularly released containing security and bug fixes, some of which may come from dependency updates. Therefore, for the vast majority of dependencies Camunda only applies patch updates.
However, certain dependencies used by Camunda 8 may have a shorter maintenance policy than Camunda itself. Camunda may adopt a different update policy for these dependencies, as listed below.
Spring
Zeebe, Operate, Tasklist, and Optimize are Spring Boot applications, and leverage Spring Boot to execute fundamental functionality such as application configuration, REST infrastructure (including security), production ready features, etc.
However, Spring Boot has a shorter maintenance window than Camunda for its open-source software (OSS) offering. Versions are only supported for 13 months, versus Camunda's 18 months. To circumvent this, patch releases for these server-side components also update Spring Boot minor versions, such that the latest patch release of these components uses a supported Spring version.
As for libraries and SDKs meant to be included in third-party applications, Camunda follows a best effort policy to balance compatibility and secure Spring-dependent libraries.