Skip to content

Flowset Year in Review

Flowset started in 2024 as a product intended to create a long-lasting alternative to Camunda 7. That’s why the project was originally called OpenBPM. It was intended to be an open-source engine and high-productivity development tools on top of it that continued the best practices of developer-friendly BPM. 

As development progressed, it became clear that the effort needed to deliver the whole Camunda 7 ecosystem is much harder than we initially expected. Luckily, we were not alone in our appreciation of Camunda 7. That’s when we learned about Operaton, a project led by a team of people with deep expertise and genuine passion for the technology, just as we were willing to become. Instead of creating yet another fork, we decided that the best path forward was to contribute to Operaton. At that point, OpenBPM no longer needed its own engine. Together with that, the name no longer reflected the direction of the product, so a rename became inevitable. That’s how Flowset was born. A set of tools around the engine to make development of BPM applications easier. 
The previous name, OpenBPM, no longer reflected this direction. It also caused confusion by suggesting the entire toolchain would be open source. In practice, some of our most valuable components — such as the Studio plug-in for IntelliJ IDEA and Workspace for analysts — will be delivered under a freemium, but commercial model. We believe transparency in naming is essential to align with our long-term vision and the expectations of the engineering community. 

Throughout the year, we saw real and growing interest in Camunda 7 productivity tools for engineering teams, in particular Flowset Control. Dozens of conversations with Camunda teams helped us better understand real-world pain points and shaped Flowset’s value proposition.  

In 2025, we shipped multiple releases and reached an important milestone with the Flowset 1.0 release. This marked our transition from experimentation to a stable product that already delivers tangible value. 

Today, we clearly see that Flowset provides value in replacing and extending Camunda web apps. At the same time, our broader mission goes further: to make the entire BPM development lifecycle as seamless as possible. 

We chose Operaton as our strategic partner, but we don’t see Flowset as tied to a single engine. Supporting other popular BPM technologies is an important part of our long-term vision. 

Group 2-2-1-1

What’s Next?

We are starting 2026 with a robust foundation for the future. Together with Operaton, Flowset makes it easy to migrate from Camunda 7. For small to medium solutions, migration can take just a few minutes. With the base migration scenario covered, we can now focus on expanding Flowset further. 

In the first half of the coming year, we plan to invest heavily in education — producing documentation, guides, and video content to help teams better understand BPM operations and migration paths. In the second quarter, we plan to release an Enterprise version of Flowset, addressing the needs of larger organizations and production environments. 

We’re excited to continue this journey in the year ahead!