Install Camunda with Helm

Camunda 8 Self-Managed can be installed on Kubernetes using Helm charts. Choose the installation path that best matches your use case:

Choose your installation path

Use case	Installation guide	Secondary storage	Complexity	Best for
Testing & evaluation	Quick install	Elasticsearch/OpenSearch	Low	Local development, POCs, learning
Production with RDBMS	Install with RDBMS	PostgreSQL, Oracle, MariaDB, MySQL, SQL Server	Medium	RDBMS-first organizations, no ES/OS license
High-scale production	Install for production	Elasticsearch/OpenSearch or RDBMS	High	High-throughput, multi-team, OIDC, HA, monitoring

Decision criteria

• Don't have a database yet? Start with quick install to evaluate Camunda with Elasticsearch/OpenSearch.
• Planning to use RDBMS? Follow install with RDBMS for step-by-step instructions, JDBC driver management, and schema setup guidance.
• Ready for production? See install for production for enterprise-grade security, authentication, multi-namespace deployments, and operational hardening. You can use either Elasticsearch/OpenSearch or RDBMS for secondary storage based on your infrastructure and requirements.

Installation guides

• Quick install with Helm:
  Get up and running with default Helm chart values. Ideal for testing, evaluation, or early development.

• Install with RDBMS as secondary storage:
  Deploy Camunda 8 using an external relational database (PostgreSQL, Oracle, MariaDB, etc.) instead of Elasticsearch or OpenSearch. Includes step-by-step instructions, JDBC driver setup, and configuration examples.

• Install for production:
  Deploy Camunda 8 in a secure, production-ready Kubernetes environment with TLS, OIDC authentication, multi-namespace deployments, and enterprise monitoring. You can choose Elasticsearch/OpenSearch or RDBMS for secondary storage based on your infrastructure and requirements.