Supported environments
Learn which browsers, operating systems, clients, deployment options, and component requirements are tested and supported for compatibility with Camunda 8.
About supported environments
If a particular technology is not listed below, Camunda cannot resolve issues caused by its usage.
You can:
- Raise a feature request that will be evaluated by our product teams to provide official support from Camunda.
- Make a help request to work with Camunda consulting services.
Recommendations are denoted with [recommended]. Other listed options are also supported.
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 browsers
- Google Chrome latest [recommended]
- Mozilla Firefox latest
- Microsoft Edge latest
Desktop Modeler
- Windows 10 / 11
- macOS 13 / 14 / 15 / 26
- Ubuntu LTS (latest)
Clients
- Zeebe Java Client: OpenJDK 8+
- Connector SDK: OpenJDK 17+
- Camunda Spring Boot Starter: OpenJDK 17+, Spring Boot 3.5.x, 4.0.x, 4.1.x
- Helm CLI: 4.x [recommended], 3.19.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. See the installation guide to learn more about the available installation options.
Deployment options
With the correct configuration, Camunda 8 Self-Managed can be deployed on any Certified Kubernetes distribution (cloud or on-premises), and is not tied to a specific Kubernetes version. The Helm chart supports the Kubernetes official support cycle.
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,linux/arm64) - 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.
Persistent volumes
Camunda supports different types of storage volumes, including block storage and network file systems (NFS).
For details on typical volume usage, refer to these examples:
Network File Systems
Camunda guarantees support for Amazon Elastic File System (EFS).
If you want to use another NFS, it must meet these requirements:
- Be POSIX-compliant.
- Never reorder file operations.
- Retry I/O operations across temporary network failures, instead of failing on timeout.
- Do not surface network-related failures in the client process.
- Only one container may mount the disk in write mode at a time. Two containers mounting the same disk in write mode could cause data corruption.
Performance
Regardless of the type, the network storage volumes you use must meet these requirements:
- They must be capable of at least 1,000 IOPS.
- The latency of write/msync operations must be in the low single digit milliseconds under normal conditions. Ideally, it's in the order of microseconds.
- The p99 latency must be lower than 300 milliseconds.
- They must be SSD-backed. HDD-backed volumes typically sustain only tens to a few hundred IOPS with multi-millisecond seek latency, well below the 1,000 IOPS minimum and single-digit-millisecond latency required for Zeebe, so they are not supported.
Helm charts version matrix
Camunda Helm chart version 14.x.x works with Camunda version 8.9.x. Check the Helm chart version matrix for more details.
Component requirements
Requirements for components are as follows:
| Component | Java version | Other requirements |
|---|---|---|
| Orchestration Cluster (Zeebe, Operate, Tasklist, Identity) | OpenJDK 21–25 |
|
| Optimize | OpenJDK 21–25 |
|
| Connectors | OpenJDK 21–25 | – |
| Management Identity | OpenJDK 17+ |
|
| Web Modeler | – |
|
| Self-Managed Console | – | – |
When running Optimize, make sure you use an Elasticsearch exporter or OpenSearch exporter version that is compatible with your Optimize version.
For a complete list of supported RDBMS versions, JDBC driver information (bundled vs. user-supplied), and component compatibility when using relational databases as secondary storage, see the RDBMS support policy.
OpenSearch and Elasticsearch support
- Camunda 8 supports both Amazon OpenSearch and the open-source OpenSearch distribution.
- Due to a limitation for the index refresh interval, OR1 instances are not supported with Amazon OpenSearch. See use Amazon OpenSearch Service with the Helm chart.
- When running Elasticsearch, you must have the appropriate Elasticsearch privileges.
- Camunda 8 works with the Elasticsearch default distribution available with the Free or Gold+ Elastic license.
Component version matrix
The following matrix shows which component versions work together. Components within the same column must share the same minor and patch version.
For Helm-managed deployments, use the Helm chart version matrix as the source of truth for the component versions bundled in a supported chart release. Do not manually override bundled component image tags unless a specific upgrade guide or release note instructs you to do so.
| Orchestration Cluster | Management | Design |
|---|---|---|
| Orchestration Cluster 8.9.x Connectors 8.9.x Optimize 8.9.x | Management Identity 8.9.x Self-Managed Console 8.9.x | Web Modeler 8.9.x Desktop Modeler 5.46+ |
You can use newer versions of Desktop and Web Modeler with older versions of the Orchestration Cluster.