{"id":5866,"date":"2024-03-11T18:29:14","date_gmt":"2024-03-11T17:29:14","guid":{"rendered":"https:\/\/onlu.ch\/camunda-vs-flowable-a-comparison-of-bpm-engines\/"},"modified":"2025-07-18T12:02:46","modified_gmt":"2025-07-18T10:02:46","slug":"camunda-vs-flowable-a-comparison-of-bpm-engines","status":"publish","type":"post","link":"https:\/\/onlu.ch\/en\/camunda-vs-flowable-a-comparison-of-bpm-engines\/","title":{"rendered":"Camunda vs Flowable: A comparison of BPM engines"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Introduction:<\/strong>
Business process management (BPM) engines such as Camunda and Flowable are core building blocks for automating business processes in companies. Banks and financial companies in Switzerland in particular place high demands on such platforms – from reliable on-premise operation<\/strong> and scalability<\/strong> to compliance<\/strong> in regulated environments. A lot has happened since the original comparison of Camunda and Flowable: Camunda has introduced Camunda 8<\/em>, a completely new, cloud-native BPM platform based on the Zeebe engine<\/strong>, while Camunda 7<\/em> (the classic Java-based engine) is slowly being phased out. This updated comparison looks at Camunda 7, Camunda 8 and Flowable in terms of CMMN support<\/strong>, architecture<\/strong>, scalability\/performance<\/strong>, APIs & integration<\/strong>, licensing\/enterprise features<\/strong> and on-premise suitability<\/strong> – with a particular focus on the needs of banks and insurance companies in Switzerland. <\/p>

CMMN support: clarify Camunda vs. Flowable<\/h2>

One major difference in advance: CMMN (Case Management Model and Notation)<\/strong> is hardly pursued by Camunda anymore. Although the CMMN functionality has been implemented in Camunda 7<\/em>, it is now only in maintenance mode<\/strong> – there will no longer be any new features camunda.com<\/a> . In <\/span>Camunda 8<\/em> is <\/span>CMMN is no longer supported <\/strong>capitalone.com<\/a>. Flowable, on the other hand, offers <\/span>full CMMN support<\/strong> and continues to invest in this standard process <\/span>forum.flowable.org<\/a><\/p>

. For use cases such as complex case processing (e.g. credit cases, compliance checks) that benefit from CMMN, Flowable therefore has an advantage from the outset. Camunda itself recommends implementing such scenarios with BPMN (sometimes with pattern workarounds), but this can be cumbersome depending on the use case. Financial companies that rely on case management<\/strong> should pay particular attention to this difference. <\/p>

Architecture: Camunda 7 (Java engine) vs. Camunda 8 (cloud-native Zeebe)<\/h2>

The architectures of Camunda 7 and Camunda 8 are fundamentally different. Camunda 7<\/em> is a monolithic Java-based process engine<\/strong>, originally a fork of Activiti. It typically runs within a Java application or on an application server and uses a relational database to store process instances, tasks and historical data. You could run Camunda 7 embedded in your own Java code, as a shared engine on a server or as a separate service with a REST API<\/strong>, depending on your needs blog.viadee.de<\/a> . This flexibility allowed banks, for example, to integrate the engine directly into existing core banking applications or to host it as an independent BPM service in their own infrastructure.<\/span><\/p>

Camunda 8<\/em> takes a completely different approach: it is based on the newly developed Zeebe engine<\/strong>, which relies on distributed microservice architecture<\/strong> rst.software<\/a>. Instead of a single Java engine with a shared database, Camunda 8 consists of <\/span>multiple components<\/strong> (Zeebe Broker\/Gateway, Operate, Tasklist, etc.), which are typically orchestrated in a Kubernetes environment <\/span>blog.viadee.de<\/a>. The engine is designed for this, <\/span>horizontally linear scaling<\/strong> and does not require a relational database – the classic DB bottleneck of Camunda 7 is eliminated <\/span>blog.viadee.de<\/a>. This means that Camunda 8 can handle considerably more process instances in parallel without being tied to a central DB transaction. However, there is the Camunda 8 engine <\/span>only as a remote service<\/strong>Embedding in own applications as with Camunda 7 is not intended <\/span>forum.camunda.io<\/a>. Process execution is always decoupled in remote mode – Camunda 8 only orchestrates the order of the tasks, the execution of the task steps takes place externally (similar to the External Task Pattern of Camunda 7)<\/span>blog.viadee.de<\/a>.<\/span><\/p>

The Flowable<\/strong> engine is a lean Java process engine core<\/strong> that also runs in a classic multi-tier architecture with a relational database. It can be operated embedded in a Java application or as a separate service in the server\/cluster<\/strong> and integrates perfectly into Spring-based environments github.com<\/a> . With regard to the <\/span>Architecture<\/strong> This means that Flowable can be deployed as flexibly as Camunda 7 (e.g. in a bank’s on-premise server landscape), while Camunda 8 requires a significantly more complex set-up with distributed components. For conservative IT environments in banks, which often still rely on proven architectural principles, the steeper learning curve of Camunda 8 could play a role. <\/span><\/p>

Scalability and performance<\/h2>

The different architectures result in major differences in scalability<\/strong>. Camunda 7<\/em> traditionally scales vertically and horizontally to a limited extent – i.e. you can run the engine on more powerful hardware or in a cluster with a shared database. However, the latter reaches its limits at some point, as the relational database is the limiting factor<\/strong> for the number of simultaneously running processes blog.viadee.de<\/a> . For many typical applications (including most internal bank processes) Camunda 7 is performant enough, but with extremely high load peaks or mass data, performance can drop if the DB becomes a bottleneck.<\/span><\/p>

Camunda 8<\/em> was explicitly designed for high throughput rates and linear scaling<\/strong>. The Zeebe engine uses an event streaming and partitioning model that allows additional broker nodes to be added and processing to be distributed across multiple instances – without a central transaction database. In practice, Camunda 8 can therefore process significantly more process instances per second<\/strong> than Camunda 7 blog.viadee.de<\/a> . This scalability can be a decisive factor for financial companies with digitization projects that have to handle very large volumes (e.g. in payment transactions or real-time processing). However, it should be noted that Camunda 8 is based on <\/span>possible consistency<\/strong> is set: Changes are not immediately visible in all components, which must be taken into account in strongly interlinked synchronous processes.<\/span><\/p>

Flowable<\/strong>‘s performance is comparable to Camunda 7, as it is also based on the established transaction-based model with relational DB. For most business workflows<\/strong> – such as credit decision processes or account openings – Flowable is sufficiently scalable. In load tests with thousands of simultaneous instances, performance depends primarily on the database and the tuning of the environment, as is the case with Camunda 7. Flowable does not offer a special, newly developed “high-throughput” mode<\/strong> like Zeebe, but the engine is designed to be “lightweight”<\/strong> and can run efficiently on modern hardware or in container orchestrations. In short: Camunda 8<\/strong> has the edge when it comes to massive scaling<\/em>, while Camunda 7<\/strong> and Flowable<\/strong> are performant and proven for “normal” process loads. In regulated industries, where stability is often more important than maximum throughput, the advantage of Camunda 8 is put into perspective – unless the deployment scenario really requires the handling of very large volumes of events in a short period of time. <\/p>

API and integration options<\/h2>

The decisive factor for developers and architects is how the BPM engine can be integrated into the existing system landscape. Camunda 7<\/em> traditionally scores points here with direct Java APIs and a REST API<\/strong>. In embedded use, Java delegates can be executed directly in the same JVM process, which allows close coupling and even joint transactions with the application. Alternatively, Camunda 7 offers a full REST API that external applications can use to start processes, query or complete tasks. This flexibility made Camunda 7 attractive for many banks, as it was possible, for example, to integrate Java modules with Camunda in the core banking system and at the same time access the engine in other areas (such as an online banking platform) via REST. <\/p>

In terms of integration, Camunda 8<\/em> relies on a dedicated gateway with gRPC API<\/strong>. Instead of talking directly to the engine (which is not possible due to the decoupling), all communication runs via the Zeebe gateway<\/strong> and its gRPC interface blog.viadee.de<\/a> . This channel can be used to start processes, pick up tasks and complete them. As gRPC is less common in the Java ecosystem, Camunda provides official <\/span>Client libraries<\/strong> for Java, JavaScript, etc. that facilitate communication <\/span>blog.viadee.de<\/a>. In addition, the interfaces in Camunda 8 are distributed across several services – e.g. there is a GraphQL API for the tasklist and a REST API for the Operate tool (process monitoring) <\/span>blog.viadee.de<\/a>. For integrations, this means a little more effort and new technologies (e.g. gRPC, GraphQL) compared to the familiar REST\/Java world. In a modern microservice architecture, however, these patterns are easy to connect. A side effect: Since Camunda 8 always works remotely, there are <\/span>No Java delegates or direct execution listeners<\/strong> more in the engine process – such logic must be outsourced to external workers <\/span>forum.camunda.io<\/a>.<\/span><\/p>

Flowable<\/strong> offers a very developer-friendly model in terms of integration. Like Camunda 7, Flowable provides Java APIs<\/strong> and can be seamlessly integrated into Spring applications github.com<\/a> . At the same time, there is also a comprehensive <\/span>REST API<\/strong>so that Flowable can either be addressed via HTTP or used as an embedded library – depending on requirements. This duality is ideal for many banks: for example, a core banking system can use Flowable as an integrated workflow orchestrator, while other satellite systems communicate with the workflow service via REST. Message queue or event integrations can also be realized, similar to Camunda 7 (e.g. External Task Pattern can be implemented analogously in Flowable). Overall, Flowable requires <\/span>No new protocols or frameworks<\/strong> in integration; developers can rely on familiar technologies. This is a plus point for existing Java stacks in financial companies, as the learning curve is lower. Camunda 8, on the other hand, comes with more modern interface technologies, which can be advantageous in future-oriented architectures (keyword cloud-native banking) – provided the know-how for gRPC & Co. is available. <\/span><\/p>

Licensing and enterprise functions<\/h2>

License models and available enterprise features<\/strong> also play a major role in the choice of BPM engine – especially in large financial institutions that need support and long-term planning security. This is where Camunda 7, 8 and Flowable differ considerably in some cases. <\/p>

Camunda 7<\/strong> was offered in two editions: the Community Edition (CE)<\/strong> is open source (Apache license) and can be used free of charge, while the Enterprise Edition<\/strong> includes a paid subscription with support and additional features (e.g. extended cockpit functions, LDAP integration, Camunda Optimize for reporting, etc.). Many companies – including banks – initially evaluated Camunda 7 in the free version and then upgraded to the Enterprise version for productive use. Important to know: Camunda has announced that it will only actively support Camunda 7 until around 2027 (community updates only until October 2025) pretius.com<\/a> . After that, full support ends (extended support with bug fixes only until 2027). <\/span>New customers are clearly steered in the direction of Camunda 8<\/strong>as Camunda 7 is still being maintained but is no longer undergoing any further development.<\/span><\/p>

Camunda 8<\/strong> also breaks with the tradition of open source when it comes to the license model. The new platform no longer<\/strong> has a free community edition<\/strong>, but always requires a commercial license for productive operation pretius.com<\/a> . Although the source code of the core engine Zeebe is publicly available, the use of the entire platform (incl. Operate, Tasklist, etc.) is only permitted in production with a valid contract. Camunda 8 is available both as <\/span>SaaS (Camunda Cloud)<\/strong> as well as offered as <\/span>self-managed<\/strong> variant for own data centers, each in staggered <\/span>enterprise packages<\/strong>. Free use is only possible for development\/testing to a limited extent <\/span>pretius.com<\/a>. For banks, this means If you want to rely on Camunda 8, you have to plan a budget for license & support. In return, however, you get access to all new components, security updates and Camunda support. The Enterprise functions in Camunda 8 include Operate (process monitoring similar to Cockpit), Tasklist (task UI), Optimize (BI\/reporting) and Identity (rights management) – many of these were only available as add-ons or in the Enterprise version in Camunda 7. In Camunda 8, they are an integral part of the offering (but not freely selectable as modules in the community, as these do not exist). <\/span><\/p>

Flowable<\/strong> follows a dual model similar to that of Camunda 7: There is an open source engine (Flowable Community)<\/strong> under Apache 2.0 license github.com<\/a>which can be used and customized free of charge. In addition, the company Flowable offers <\/span>Enterprise products<\/strong> (e.g. <\/span>Flowable Work<\/em> for case management with UI, <\/span>Flowable Engage<\/em> for chatbot integration etc.) that are <\/span>commercially licensed<\/strong> are <\/span>forum.flowable.org<\/a>. These enterprise tools are based on the open source core, but offer convenient web interfaces, integrations (e.g. Elasticsearch-based search) and additional support for operations. In principle, a financial company can therefore start with the free Flowable engine and build its own solutions around it – or use the <\/span>Enterprise package<\/strong> in order to obtain ready-to-use solutions (incl. modeling UI, admin UI, etc.) more quickly. The costs for Flowable-Enterprise are individually negotiable; they tend to be regarded as <\/span>more flexible and often cheaper<\/strong> compared to large BPM suites. Nevertheless, you should bear in mind that the open source version of Flowable does not have limited engine functions (everything, including CMMN, is included), but for professional use in a bank, the enterprise extensions for monitoring, scaling (e.g. multi-node tools) and support are often very valuable. This depends on the bank’s requirements and resources: If you have a strong in-house development team, the open source version may be sufficient; if you need fast results and manufacturer SLA, the enterprise version makes sense. <\/span><\/p>

To summarize:<\/strong> Camunda 8 is fully committed to a commercial subscription model<\/strong>, while Flowable is sticking to the open source route and has optional enterprise offerings. For a bank with strict compliance requirements, open source can be attractive (keyword: independence, no vendor lock-in), but at the same time you have to weigh up whether you can make up for the lack of official support internally. Camunda is very well established as a commercial provider in the BPM world, which also means that expertise<\/strong> could be easier to find on the market<\/strong>. Flowable is somewhat less well-known, but also has an active community and is supported by former Activiti developers – the code base is tried and tested<\/strong>. <\/p>

On-premise operation and relevance for regulated industries<\/h2>

As a highly regulated industry<\/strong>, aspects such as data sovereignty<\/em>, security<\/em> and compliance<\/em> are crucial for Swiss banks and insurance companies. Many institutions prefer (or require) on-premise operation<\/strong> of their core systems in order to have full control over data and processes – cloud solutions are often only permitted hesitantly or in isolated areas, especially when customer data or transaction-relevant data is involved. Against this backdrop, the operating mode<\/strong> of the BPM engine is a critical factor. <\/p>

Camunda 7<\/em> is predestined for on-premise from the ground up. You can run the engine in your own infrastructure – be it on dedicated servers, in virtual machines or containerized in your own data center. All components (database, web apps such as Cockpit\/Tasklist etc.) run under the full control of the bank. This fits in well with the usual IT requirements in banks<\/strong>, where software is ideally operated within the bank’s own security zones. Camunda 7 can be used in highly secure environments (with network segmentation, without Internet access) without any problems and meets the requirements for auditability and traceability set by FINMA, for example. <\/p>

Camunda 8<\/em> was primarily developed with a cloud strategy<\/strong> in mind. The standard offering is a SaaS service<\/strong>, hosted in the provider’s cloud (Camunda Cloud). This model is often problematic for banks, as process data would be stored and processed outside of their own infrastructure. Although Camunda Cloud guarantees operation in European data centers and offers encryption and ISO certifications, many financial companies have policies that prohibit the outsourcing of such workflows to a public cloud. The good news:<\/strong> Camunda 8 is also available as a self-managed version<\/strong> that can be operated on your own servers (or in a private cloud) blog.viadee.de<\/a>. <\/span> <\/p>

In practice, however, this means increased effort: a bank would have to provide a Kubernetes cluster environment, install, configure and operate the various Camunda 8 components. Not every IT operation is already set up to manage a distributed microservice platform internally. In addition, Camunda 8 Self-Managed currently still has a few limitations (as of today, some SaaS features are only available on-prem to a limited extent). For <\/span>Regulated industries<\/strong> However, the self-managed route is usually the only viable option if you want to use Camunda 8 – and it is generally feasible (some large banks and insurers are already evaluating or using Camunda 8 on-premises, often in container platforms such as OpenShift). Important: The bank is still dependent on the manufacturer, especially when it comes to updates and support, as the platform cannot be operated without a license. <\/span><\/p>

Flowable<\/strong> is an on-premise \/ self-hosted solution<\/strong> by origin. Designed as an open source engine, Flowable runs in any environment – whether classically on an application server, integrated into an existing application or in Docker\/Kubernetes within the bank. There is no obligation to use any cloud service<\/strong>. This gives financial companies maximum sovereignty: all process data remains in-house and adjustments can be made to the code if necessary. Flowable, Inc. itself does not (as far as is known) offer its own public cloud BPM SaaS – the business model is rather to sell licenses for the enterprise tools or to support projects. Flowable therefore fits very well into strictly regulated IT environments. For example, Z\u00fcrcher Kantonalbank (ZKB), the largest cantonal bank in Switzerland, has chosen Flowable as its process automation solution<\/strong> to significantly accelerate internal processes flowable.com<\/a> . In this case, Flowable could be implemented on-premise, which meets the high data protection requirements. Especially when a bank <\/span>CMMN case management<\/strong> (e.g. in loan processing or in the compliance environment), Flowable is a very attractive option due to its complete support and on-premise capability.<\/span><\/p>

To summarize, banks and insurers need to evaluate for themselves: Camunda 7<\/strong> can be operated on-prem without any problems, but will be replaced in the future. Camunda 8<\/strong> offers modern cloud technology and enormous scaling, but requires a modern containerized operation on-prem and does not come without commercial contracts. Flowable<\/strong> can be used completely on-premises (open source), which allows maximum control – but here, too, you should consider the enterprise-level tools for productive use. In Switzerland, where regulatory requirements are strict, Flowable could therefore be the more pragmatic option in some cases, provided the functions are sufficient and there is no problem with the smaller manufacturer. Camunda 8, on the other hand, may be of interest to institutions that deliberately pursue a cloud-native approach (such as new digital platforms detached from the core banking system) or that need to map extremely high loads, where the architectural advantage comes into play. <\/p>

Comparison table: Camunda 7 vs. Camunda 8 vs. Flowable<\/h2>

For a better overview, the following table summarizes the most important criteria and differences between Camunda 7<\/strong>, Camunda 8<\/strong> and Flowable<\/strong>:<\/p>
Criterion<\/strong><\/th>Camunda 7 (Platform 7)<\/strong><\/th>Camunda 8 (Platform 8)<\/strong><\/th>Flowable<\/strong> (6 \/ V7 Engine)<\/th><\/tr><\/thead>
BPMN 2.0 support<\/strong><\/td>Complete (stable for years)<\/td>Complete (new Zeebe engine)<\/td>Complete (BPMN 2.0)<\/td><\/tr>
CMMN support<\/strong><\/td>

Yes, but only maintenance mode (no further development)<\/p>

No (not available in Platform 8)<\/p>

Yes, fully and actively developed<\/p>

DMN support<\/strong><\/td>Yes (Camunda Decision Engine 7)<\/td>

Yes (new integrated decision engine)<\/p>

Yes (embedded in engine)<\/td><\/tr>
Architecture<\/strong><\/td>Classic Java engine, monolithic or embedded, requires relational DB<\/td>

Microservices architecture (Zeebe Broker\/Gateway + Services), event sourcing, no relational DB<\/p>

Classic Java engine, runs embedded or as a service; uses relational DB<\/td><\/tr>
Scalability<\/strong><\/td>Vertical \/ limited horizontal scalability (DB as bottleneck)<\/td>

Highly scalable (horizontal scaling through distributed brokers, no central DB)<\/p>

Similar to Camunda 7: limited horizontal (DB cluster), sufficient for most use cases<\/td><\/tr>
Performance<\/strong><\/td>Proven, good performance up to medium load; DB limitations for very high loads<\/td>Very high performance even with a massive number of instances (possibly consistent processing)<\/td>Good performance for normal load; light footprint, efficient engine<\/td><\/tr>
Integration options<\/strong><\/td>Java API (embedded), JUEL scripts, REST API, external tasks; direct transactions with app possible<\/td>

gRPC API via Zeebe Gateway (clients for Java, JS etc.)<\/p>

Java API (embedded possible), REST API; seamless Spring integration<\/p>

Enterprise features<\/strong><\/td>Cockpit (limited in Community), complete Operations UI & Admin only in Enterprise; Optimize (Reporting), Consultants Support etc.<\/td>Includes all new tools (Operate, Tasklist, Optimize, Identity) out-of-the-box in Enterprise; continuous updates from the manufacturer<\/td>

Flowable Work\/Engage (licensed UIs for cases, chat, etc.)<\/p>

Licensing<\/strong><\/td>

Open Source (Apache 2) for Community Edition; Enterprise Subscription for full functionality; Camunda 7 CE EOL October 2025<\/p>

Enterprise license model only<\/strong> (no free prod use)<\/p>

Open Source (Apache 2) for Engine<\/p>

Operation \/ Deployment<\/strong><\/td>On-premise (own servers\/VMs, containers) or platform-as-a-service by the bank itself; simple installation (one Java process + DB)<\/td>

Default as Camunda SaaS cloud; alternatively self-managed on-prem in own Kubernetes environment<\/p>

On-premise (server, VM, container) fully supported; no official public SaaS by manufacturer (Design Modeler available as a cloud service)<\/td><\/tr>
Suitability for regulated environments<\/strong><\/td>High – complete data sovereignty on-prem, proven stability, audit logging available<\/td>Limited – only self-managed option on-prem suitable (higher effort, license requirement); SaaS not permitted for many banks<\/td>

High – complete control on-prem, open platform (source code can be viewed); compliance adjustments possible; already used by Swiss bank<\/p>

flowable.com<\/a><\/div><\/td><\/tr><\/tbody><\/table>

(Legend: BPMN<\/strong> = Business Process Model and Notation, CMMN<\/strong> = Case Management Model and Notation, DMN<\/strong> = Decision Model and Notation)<\/em><\/p>

Conclusion: Decision criteria for financial companies<\/h2>

The choice between Camunda 7, Camunda 8 and Flowable depends heavily on a company’s individual requirements and strategies<\/strong>. In the financial sector – where reliability, compliance and data control<\/strong> are priorities – the following considerations should be factored into the decision: <\/p>