Skip to main content
Version: 8.0

Camunda Platform 8 deployment

This chapter contains information for users who want to deploy and run Camunda Platform 8 Self-Managed, typically in your self-controlled cloud (public or private) or even on your own hardware.

Components

Camunda Platform 8 includes the following components as Java applications:

  • Zeebe Broker and Gateway
  • Operate (requiring Elasticsearch)
  • Tasklist (requiring Elasticsearch)
  • Optimize (requiring Elasticsearch)
  • Identity (requiring Keycloak)

Depending on your needs, you might not need all the above components to successfully use Camunda Platform 8.

Supported environments

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

Deployment options

You have the following options to run the above components in a self-managed fashion:

  • Kubernetes: We strongly recommend using Kubernetes to run Camunda Platform 8 in production. Using minikube, Kubernetes can also be an interesting environment to run Camunda Platform 8 locally on developer machines.
  • OpenShift: You can run Camunda Platform 8 on OpenShift in much the same way you would on a standard Kubernetes cluster, with some configuration based on your desired security context constraints.
  • Docker: You can run the provided Docker images of the components, also in production. For your convenience, we provide a Docker Compose configuration to run Camunda Platform 8 on developer machines. Note that the Docker Compose configuration is not optimized for production usage, but for local development.
  • Local installation: You can run the Java applications 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.

Deployment recommendation

As you can see below, we recommend SaaS whenever possible, as Camunda does the heavy lifting and provides everything as a service for you. This provides peace of mind and allows you to concentrate on the important work. If SaaS is not an option, we have a strong opinion on how you should install Camunda Platform 8, depending on the goal (production or development).

Production

For production usage, we highly recommend using a real Kubernetes cluster and our Helm charts if SaaS provided by Camunda is not an option for you.

We support the following deployment options (the sequence expresses preference) for production:

  1. SaaS
  2. Helm on a real Kubernetes cluster (independent of where this is hosted, for example GKE), including a dedicated guide to deploy with Helm on OpenShift.
  3. Docker images together with the infrastructure as code (IaC) tool of your choice.
  4. Local installation using the infrastructure as code (IaC) tool of your choice.

Development

For development usage, we highly recommend using our Helm charts on KIND if SaaS provided by Camunda is not an option for you. Those Helm charts are battle-tested and give you an experience close to production.

We support the following deployment options (the sequence expresses preference) for production:

  1. SaaS
  2. Helm charts on KIND or Helm on a managed Kubernetes offering (like GKE) or Helm on a local Kubernetes installation like minikube.
  3. Docker Compose
  4. Local installation as a last resort if you only need the Zeebe broker. We don't recommend setting up the whole toolchain in this fashion.

Getting help

If you have questions or feedback about deployment with Zeebe, we encourage you to visit: