Skip to main content
Version: 8.5

Camunda 8 installation overview

This guide contains information for users who want to install, deploy, and upgrade Camunda 8 Self-Managed, typically in their self-controlled cloud (public or private) or on their own hardware.

Components​

All components except Web Modeler and Console are single Java applications. Depending on your needs, you might not need all of the above components to successfully use Camunda 8.

Camunda 8 Self-Managed users may also use Desktop Modeler as an addition to these components. Desktop Modeler can be used by process developers to build BPMN diagrams, DMN diagrams, or Camunda Forms for automation.

note

To obtain or retrieve your Camunda 8 credentials for Enterprise licenses, visit the contact page.

Supported environments​

For details on supported environments (e.g. Java or Elasticsearch versions), see supported environments.

Deployment options​

  • Helm/Kubernetes: We recommend using Kubernetes and Helm to deploy and run Camunda 8 Self-Managed in production. With the right configuration, Camunda 8 Self-Managed can be deployed on any Certified Kubernetes distribution (cloud or on-premises). We also officially support a variety of providers like Red Hat OpenShift and Amazon EKS.
  • Docker: Component Docker images are available for use in production on Linux systems. Windows or macOS are only supported for development environments.
  • Manual: The Java applications can run on a local or virtual machine if it provides a supported Java Virtual Machine (JVM). This allows you to run Camunda on virtual machines or bare metal and offers a significant amount of flexibility. However, you will need to configure the details for the components to interact correctly yourself. We consider this a last resort. Note that Windows/Mac is not supported for production usage of Zeebe.

A Docker Compose configuration file is also provided for local development, and is not optimized for production usage. You can find setup instructions in the camunda-platform repository.

For more details on deployment, see sizing your environment.