Camunda 8 orchestrates complex business processes that span people, systems, and devices

Camunda 8 delivers scalable, on-demand process automation as a service. Camunda 8 is combined with powerful execution engines for BPMN processes and DMN decisions, and paired with tools for collaborative modeling, operations, and analytics.

This repository contains the Orchestration cluster components of Camunda 8 and Optimize:

• Zeebe - The cloud-native process engine of Camunda 8.
• Tasklist - Complete tasks that require human input.
• Operate - Manage, monitor, and troubleshoot your processes.
• Identity - Manage integrated authentication and authorization.
• Optimize - Improve your processes by identifying constraints in your system.

In addition, the Camunda 8 stack also includes:

• Console - Configure and deploy clusters with Console.
• Web Modeler - Web Application to model BPMN, DMN, & Forms and deploy or start new instances.
• Desktop Modeler - Use Desktop Modeler as a desktop application for modeling BPMN, DMN, and Forms with your local process application project.
• Connectors - Integrate with an external system by using a Connector.
• Management Identity - Manage authentication, access, and authorization for components outside the Orchestration cluster (Console, Web Modeler, and Optimize)

Using Camunda 8, you can:

• Define processes visually in BPMN 2.0
• Choose your programming language
• Deploy with Docker and Kubernetes
• Build processes that react to messages from Kafka and other message queues
• Scale horizontally to handle very high throughput
• Fault tolerance (no relational database required)
• Export process data for monitoring and analysis
• Engage with an active community

Learn more at camunda.com.

Status

To learn more about what we're currently working on, check the GitHub issues and the latest commits.

Helpful Links

• Releases
• Pre-built Docker images
• Building Docker images for other platforms
• Blog
• Documentation Home
• Issue Tracker
• User Forum
• Contribution Guidelines

Documentation

This repository includes comprehensive documentation in the docs/ directory. The content is served via a Docusaurus site located in monorepo-docs-site/.

Running the Documentation Site

cd monorepo-docs-site
npm install
npm start

The documentation site will be available at http://localhost:3000/camunda/.

Adding Documentation

1. Add new markdown files to the docs/ directory
2. Update the sidebar configuration in monorepo-docs-site/sidebars.js to include your new documentation file in the appropriate array position. For example:

// in monorepo-docs-site/sidebars.js
module.exports = {
  docs: [
    'introduction',
    'getting-started',
    // add your new doc ID here
    'your-doc-id',
  ],
};

For more details, see the documentation site README.

Recommended Docs Entries for New Users

• What is Camunda Platform 8?
• Getting Started Tutorial
• Technical Concepts
• BPMN Processes
• Installation and Configuration
• Java Client
• Camunda Spring Boot Starter

Contributing

Read the Contributions Guide.

Code of Conduct

This project adheres to the Camunda Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior as soon as possible.

Release Lifecycle

Please refer to our Release Policy to learn about our release cadence, maintenance periods, etc.

License

Zeebe, Operate, and Tasklist source files are made available under the Camunda License Version 1.0 except for the parts listed below, which are made available under the Apache License, Version 2.0. See individual source files for details.

Available under the Apache License, Version 2.0:

• Java Client (clients/java)
• Camunda Spring Boot Starter (camunda-spring-boot-starter)
• Exporter API (exporter-api)
• Protocol (protocol)
• Gateway Protocol Implementation (gateway-protocol-impl)
• BPMN Model API (bpmn-model)

Clarification on gRPC Code Generation

The Zeebe Gateway Protocol (API) as published in the gateway-protocol is licensed under the Camunda License 1.0. Using gRPC tooling to generate stubs for the protocol does not constitute creating a derivative work under the Camunda License 1.0 and no licensing restrictions are imposed on the resulting stub code by the Camunda License 1.0.