Skip to main content
Version: 8.9 (unreleased)

Supported environments

The following 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:

Recommendations are denoted with [recommended], however, other listed options are also supported.

Minimum versions

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
  • 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 correct 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:

Helm chart compatibility

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.
  • Doesn't 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.

Helm charts version matrix​

Camunda Helm chart version 13.x.x works with Camunda version 8.8.x. Check the Helm chart version matrix for more details.

Component requirements​

Requirements for components are as follows:

ComponentJava versionOther requirements
Orchestration Cluster (Zeebe, Operate, Tasklist, Identity)OpenJDK 21+
OptimizeOpenJDK 21+
  • OpenSearch 2.17+
  • Elasticsearch 8.18.6+
ConnectorsOpenJDK 21+–
Management IdentityOpenJDK 17+
Web Modeler–
Self-Managed Console––
RDBMS support

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​

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.

DesignAutomateImprove
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
note

You can also use newer versions of Desktop and Web Modeler with older Zeebe versions.