Camunda Modeler: what the tool does, and the decisions that stay with you

The Camunda Desktop Modeler is an application for your own machine that you use to draw BPMN diagrams, DMN decision tables and forms. Camunda describes it in one sentence: “Desktop Modeler (also known as Camunda Modeler) is a desktop application for modeling BPMN, DMN, and Forms.” It is open source under the MIT licence, and the same application serves Camunda 7 and Camunda 8.

One point clears up most of the confusion around it. One application serves both generations, and a model drawn for Camunda 7 goes through conversion before it runs on Camunda 8. Camunda offers a separate Diagram Converter to “Analyze and convert BPMN, DMN, and Camunda 7 form files”, and the expression language changes from JUEL in Camunda 7 to FEEL in Camunda 8 (docs.camunda.io, Conceptual differences).

What the Desktop Modeler does, in Camunda’s words

The feature list in the documentation (docs.camunda.io, Desktop Modeler) reads:

• “Design BPMN, DMN, and Forms”
• “Implement process applications for Camunda 7 and 8”
• “Deploy and run processes directly from the application”
• “Validate your diagrams using configurable lint rules”
• “Customize and extend the application”
• “Work against the local file system”

Two items on that list matter more in practice than the other four. The configurable lint rules are the mechanism that catches modelling errors before a process runs. And working against the local file system means your .bpmn files can sit in the same repository as your code, with the same history and the same review process.

That second point is why we keep process models in the code repository. A process model is source code. It belongs in the same version control as everything else that runs in production.

Download, platforms and the current release

Camunda offers the app for Windows, Linux and macOS from its downloads page. After you extract the archive you can start it directly, and on Windows and Linux you can register it as the default editor for BPMN, DMN and form files (docs.camunda.io, Desktop Modeler).

The Modeler ships often. Release 5.52.0 was published on GitHub on 6 October 2026. According to its changelog, it marks Camunda 8.10 as the latest stable engine profile and drops support for 32-bit Windows distributables. Camunda lists October 2026 as the release month of Camunda 8.10 (Camunda 8 release notes). On the Camunda 7 side, the changelog records support for Camunda 7.24 from Modeler 5.35.0 and marks 7.24 as stable from 5.40.0.

The Camunda 7 documentation now points elsewhere for the Modeler. Its Modeler page for 7.24 says: “This content has moved to docs.camunda.io and is available here for all future versions” (docs.camunda.org, Camunda Modeler). The current Modeler documentation for both generations therefore lives on docs.camunda.io.

Licence: the Desktop Modeler and the Web Modeler sit on different terms

The repository camunda/camunda-modeler carries the MIT licence and is not archived, and its most recent push was on 19 October 2026. We checked all three through the GitHub API that day. Camunda’s licensing page confirms it: “The source code of Desktop Modeler is licensed under the MIT license as stated in the LICENSE file in the root of the source code repository.” The same page adds: “This file is also shipped as LICENSE.camunda-modeler.txt with each modeler distribution.” You need no commercial licence to use the Desktop Modeler.

The Web Modeler has its own terms. On the same page Camunda writes: “The source code for the Web Modeler and Console is licensed to our users and customers under a proprietary license and is only available to users or customers on demand.” For production use of the compiled software, the page points to the Camunda Self-Managed Enterprise Edition (docs.camunda.io, Licensing). A procurement document that lists the two as one product files two different licensing positions under one name.

What the Modeler leaves for you to decide

Three questions in a Camunda project sit outside the tool. Here they are, in the order they tend to come up.

The expression row deserves a closer look. Camunda’s migration guide states: “Camunda 7 uses Java Unified Expression Language (JUEL) as the expression language.” And: “Camunda 8 uses Friendly-Enough Expression Language (FEEL) and expressions can only access the process instance data and variables.” The guide adds that in the embedded engine scenario, Camunda 7 expressions “can even read into beans (Java object instances) in the application”. It also says “Most expressions can be converted” and that “you may need to completely rewrite others”. A gateway condition that reads a bean in Camunda 7 is a candidate for that rewrite before it runs on Camunda 8 (docs.camunda.io, Conceptual differences).

The third row rests on the same guide. It explains that Camunda 7 allows embedding the engine in your application, while in Camunda 8 the engine is “always a remote resource for your application”, and that “Camunda 8 only allows storage of primary data types or JSON as process variables.” Those differences land in Java code. For the models themselves, Camunda describes the Diagram Converter as a tool to “Analyze and convert BPMN, DMN, and Camunda 7 form files”, available for local installation or as a free hosted service.

Where Camunda 7 stands while you model for it

Camunda 7 Community Edition reached end of life in October 2025. Camunda had scheduled its final feature release, 7.24, for 14 October 2025 (Camunda forum), and the Maven Central record for camunda-engine 7.24.0 reads: “Note: 7.24.0 is the last community edition release published on Maven Central” (Maven Central, camunda-engine 7.24.0). For the Enterprise Edition, Camunda writes on its migration page: “Camunda 7 Enterprise Edition remains supported through April 2030, but we recommend all new projects be developed on Camunda 8” (camunda.com/platform-7/migrate). The Modeler documentation still lists Camunda 7 and 8 as targets. Every date by version is listed in Camunda 7 end of maintenance, and the wider product picture is in What is Camunda?.