This site is also available in: Deutsch (German)
Content of this article:
- Introduction & Background: History of Camunda and Flowable (Where do we come from?)
- Status quo: current market position and presentation of CIB seven & CIB flow (new solutions)
- Camunda 8 in focus: reasons for the change, advantages, new features vs. disadvantages & architecture (microservices)
- Migration & outlook: Migration effort, challenges, effort estimation and how we can support (and next steps)
In this blog post, we’ll take a look at the development of BPM platforms – from Camunda 7 to CIB seven and CIB flow to the current Camunda 8. First, I’ll give you a brief overview of the process: We’ll start with some background on the history of Camunda and Flowable. Then we’ll look at the current market situation and explain what CIB seven and CIB flow are all about. The main part is about Camunda 8 – why it was introduced, what innovations and advantages it brings, but also what disadvantages and challenges are associated with it (keyword microservices). Finally, we talk about the migration effort from Camunda 7 to 8 or to CIB seven, the challenges involved and give a rough estimate of the effort involved. Finally, we show how we can support you in these steps and what the next steps are.
History of Camunda & Flowable
- Camunda BPM (Camunda 7): Originated in 2013 as a fork of the Activiti BPM project. The Berlin-based company Camunda developed its own process engine from this.
- Flowable: Created in 2016 as another fork of Activiti, initiated by the original Activiti development team. Flowable succeeded Activiti as an open source engine.
- BPMN 2.0 standard: Both engines (Camunda & Flowable) rely on the BPMN 2.0 standard for graphical modeling of processes. They also support DMN decision tables and CMMN (Case Management).
- Open Source & Community: Camunda and Flowable were built as open source solutions with active communities. Camunda established a business model with enterprise support, while Flowable was developed independently.
- Evolution: The common roots (Activiti) explain the functional similarity of both systems. Camunda 7 and Flowable shaped the BPM market in the 2010s as lightweight workflow engines that could be integrated into Java.
Let’s start with a look into the past. Camunda has its origins in the Activiti project – an open source BPM engine project from 2010. Camunda separated from Activiti in 2013 and developed its own fork under the name Camunda BPM (also known as Camunda 7). At the same time, Flowable (2016) was created a few years later, also from an Activiti fork. Both therefore share a common basis and implement the BPMN 2.0 standard for process modeling. In practice, this means that both Camunda and Flowable enable the graphical modeling and execution of business processes (as well as decision logic via DMN). As open source projects, both have attracted a community – Camunda combined this with a commercial support model and grew strongly, while Flowable lives on as a flexible open source successor to Activiti. This shared heritage helps us understand why many of the core concepts in Camunda 7 and Flowable are similar. So much for the history – which brings us to the starting point of our BPM evolution.
Market position today
- Camunda as market leader: Camunda is now one of the leading BPM platforms worldwide, with a large user base in companies across a wide range of industries. In 2024, Camunda exceeded the $100 million annual revenue mark – an indicator of its broad acceptance.
- Flowable as an alternative: Flowable is also establishing itself as an important open source alternative in the BPM market, especially where flexibility and independence from commercial licenses are required.
- Other BPM players: In addition to Camunda and Flowable, there are proprietary BPM suites (IBM BAW, Appian, Pega, etc.), which are often heavier and more expensive.
- Camunda 7 vs 8 transition: Camunda 7 is currently being replaced by the new Camunda 8 platform. Existing customers are faced with the decision of whether and when to migrate.
- Open source in transition: Camunda 7 was completely open source, but Camunda 8 is mainly marketed commercially. This influences the market dynamics and opens up space for open source projects such as CIB seven.
Let’s take a look at the current market situation. In recent years, Camunda has established itself as one of the top providers in the field of BPM and process automation. The company has grown strongly – an indicator: they have passed the $100 million annual recurring revenue threshold, which shows how many companies rely on Camunda. Flowable remains a relevant alternative in the open source segment and scores points with organizations that want a free, independently developed BPM engine. There are also major proprietary players such as IBM, Appian and Pega. In comparison, Camunda scores particularly well with technical teams thanks to its open standards and the ability to embed it flexibly in their own applications. Camunda is currently undergoing a technology change – from Camunda 7 to Camunda 8. The new release cycle is predominantly designed for a commercial subscription model, which creates space for open source offerings such as CIB seven.
What is CIB seven & CIB flow?
- CIB seven: Open source continuation of the Camunda 7 BPM engine by the company CIB. Fork of the Camunda 7 Community Edition, further developed and maintained since the end of 2024.
- Purpose of CIB seven: Available alternative for Camunda 7 users to protect investments and ensure digital sovereignty. Fully open source, on-premise operation possible.
- CIB flow: Low-code BPM platform from CIB that integrates CIB seven as a process engine. Web-based interface for modeling and execution, including form designer, connectors to third-party systems and AI modules.
- Function of CIB flow: Orchestration of complex business processes via BPMN 2.0 without in-depth programming knowledge. Integrated document processing (PDF, digital signatures) and AI components (text recognition).
- Background: Products of the CIB Group. Together, CIB seven (engine) and CIB flow (front end) offer a complete solution on-premise or as SaaS.
CIB seven is a fork of Camunda 7, published by the CIB Group at the end of 2024, to provide long-term support for the Community Edition of Camunda 7. For Camunda 7 users, it offers a seamless transition without license costs and with ongoing open source support. CIB flow is the associated low-code platform: a web modeler, form editor and a UI for Tasklist and Cockpit that uses CIB seven as an engine. Together, they enable a user-friendly BPM solution with comprehensive expansion options and centralized support.
Synergies of integration
- Seamless integration: CIB seven acts as the heart of CIB flow. Modeled processes in CIB flow are executed directly, without media breaks.
- Investment protection: Existing Camunda 7 BPMN models and workflows can be adopted – minimal adaptation effort.
- Convenience + stability: Stable, high-performance engine (CIB seven) meets user-friendly low-code front end (CIB flow). Developers and technical experts work more closely together.
- Expandability: Integrated connectors and AI modules enable simple integration of external services.
- Standardized support: Central contact CIB – updates and support are coordinated.
The integration of CIB seven and CIB flow offers a sophisticated, high-performance engine combined with an intuitive low-code design front end. Existing processes are retained, while new functions such as AI modules, document automation and a wide range of connectors are available. The whole thing is backed up by a standardized support approach.
CIB seven – Product details & roadmap
- Basis & version 1.x: CIB seven 1.0 in November 2024, followed by 1.1. Based on Camunda 7.22 CE, fully compatible.
- Compatibility: Migration requires minimal changes (Maven dependencies, package names). Existing processes and Java delegates run unchanged.
- Roadmap 2025: Version 2.0 on May 7, 2025 with its own web interface (Tasklist, Admin UI, Cockpit); Version 2.1 in October 2025 based on Camunda 7.24.
- Long-term support: maintenance and security updates beyond 2025. Support for Camunda 7 CE users from October 2025.
- Further development: Community marketplace for expansions (2025/26) and community program from summer 2025.
CIB seven 1.x is technically equivalent to Camunda 7.22 and can be migrated in minutes. Version 2.0 with an open source web interface will follow on May 7, 2025. Version 2.1 will be released in fall 2025 to incorporate the final Camunda 7.24 code. CIB guarantees long-term support and update management and is building a community with a marketplace.
Why Camunda 8?
- Scaling requirements: Distributed, log-based architecture (Zeebe engine) eliminates DB bottlenecks.
- Cloud & microservices trend: Kubernetes- and Docker-optimized, SaaS offering, orchestration of distributed microservices.
- Performance & resilience: event streaming instead of central SQL DB; replication and fault tolerance.
- Advanced use cases: From BPM to process orchestration: RPA, event streams, AI integration, serverless functions.
- Product strategy: SaaS and subscription model for regular revenue and faster feature development.
Camunda 8 was introduced to enable horizontal scaling and cloud-native processes and to provide a modern orchestration platform. The new Zeebe engine allows higher loads, parallel processing and better fault tolerance. At the same time, Camunda is pursuing a strategic realignment towards SaaS and subscription models.
Advantages & new features in Camunda 8
- Scalability & performance: Horizontal scaling via broker cluster, no DB bottleneck.
- Reliability & availability: Distributed data replication, geo-redundancy, no single point of failure.
- Cloud-native operation: Helm charts for Kubernetes, SaaS offer for a quick start.
- New tooling experience: Web Modeler, Operate (Cockpit), Tasklist, Optimize for analysis and reporting.
- Connectors & integration: a variety of ready-made connectors, event-driven patterns for microservices.
Camunda 8 offers a comprehensive, cloud-native platform with modern tools for modeling, monitoring and analysis. The distributed architecture ensures performance and resilience, while ready-made connectors facilitate integration into other systems.
Disadvantages & missing features
- Higher complexity (operation): More services, Kubernetes/monitoring effort, no embedded engine mode.
- Licensing & costs: Proprietary components (Operate, Tasklist, Optimize), practical use only with commercial contract.
- Incompatibilities & migration effort: External engine via gRPC, no Java embedded context, FEEL replaces JUEL, extensive adaptations necessary.
- Learning curve & maturity: New concepts, early feature implementations, missing batch operations and migration tools.
- Overhead for small projects: Complex infrastructure often oversized for simple workflows.
Camunda 8 entails greater operational complexity and ongoing costs and requires extensive migrations and training. For many simple use cases, the overhead may not be justified.
Critical consideration: microservices architecture
- Advantages: Independent scaling, fault tolerance, modular development.
- Complexity & DevOps effort: Deployment, orchestration, monitoring and error diagnosis more demanding.
- Not ideal for every use case: monoliths are often more robust and simpler.
- Latency & overhead: Network calls instead of method calls increase latency.
- Consideration necessary: Microservices are worthwhile when there are real requirements for scaling and availability.
Microservices offer modularity and scalability, but require sophisticated DevOps and increase latency. A monolithic solution is often sufficient.
Migration effort Camunda 7 → 8 vs. to CIB seven
- Camunda 7 → CIB seven: Little effort, library exchange, customize package names, few days/weeks.
- Camunda 7 → Camunda 8: High effort, external workers, API changes, script adaptations, several person-months.
- BPMN/DMN porting: models mostly reusable, check for unsupported constructs.
- Parallel drift & cut-over: parallel operation of both systems, cut-off date change, monitoring of both platforms.
- Infrastructure & test: Set up new environment (cluster/cloud), extensive tests, adapt CI/CD pipelines.
Migration to CIB seven is possible in days, while Camunda 8 is a new project that requires a lot of effort. Specialist models can usually be adopted, while parallel operation should be anchored and extensively tested in organizational terms.
Technical & organizational challenges
- Infrastructure change: container technologies, Kubernetes/OpenShift, DevOps tools required.
- Know-how & training: Zeebe-API, External Tasks, FEEL, Elasticsearch, gRPC, monitoring of distributed systems.
- Conversion process: project phases, inventory, migration roadmap, risk management.
- Stakeholder communication: Involve specialist departments, manage expectations, communicate benefits clearly.
- Change management: change management plan, demo sessions, rollout concepts, lessons learned.
A successful rollout requires infrastructure development, training measures and stringent project and change management with clear phases, risk planning and stakeholder communication.
Cost estimate
- Camunda 7 → Camunda 8: Small projects 2-3 months; larger projects 6-12+ months with team.
- Camunda 7 → CIB seven: Days to a few weeks, significantly less effort.
- Task categories: Refactoring, infrastructure, tests, training.
- Buffer & unknowns: Reserve for technical hurdles, recommend iterative approach.
- Cost-benefit: Check whether the added value of Camunda 8 now justifies the investment or whether CIB seven pragmatically suffices.
The scale of the Camunda 8 migration corresponds to a new project with several months of effort, whereas CIB seven can usually be implemented in a short time. A cost/benefit analysis helps with the decision and can enable a staggered approach.
Where can we help?
- Analysis & consulting: Check BPM landscape, recommendation for CIB seven vs. Camunda 8.
- Migration planning: project phases, milestones, risk/rollback strategies.
- Technical implementation: refactoring, worker implementation, BPMN adaptations, CIB flow integration.
- Training & coaching: Workshops for developers, admins and users, on-the-job coaching.
- Operation & support: performance tuning, updates, troubleshooting, support contracts.
Our team provides support in all phases: from analysis, planning and implementation to training and long-term support. This allows you to concentrate on your core processes.
Sources
- History of Camunda & Flowable: medium.com
- Camunda 2024 financial figures: camunda.com
- CIB seven launch & product pages: capterra.com, cib.de, cibseven.de
- Zeebe-Engine & Camunda 8 Architecture: rst.software
- Camunda 8 Tooling & Connectors: pretius.com
- Camunda 8 Embedded Engine & API changes: unsupported.docs.camunda.io
