I can't give you a good reason to skip over Bizagi. I have been using Bizagi for over 4 years and have gone from total low-code skeptic to low-code evangelist and a strong supporter of Bizagi. It's available for no cost to learn, develop, and test/pilot process automation (up to 20 users in test), and has very reasonable licensing options for production once you are ready to go live. It also is powerful and flexible. We're even using it to drive our docket and scheduling system for hearings (not something one things of doing with a "process automation" tool). Can't recommend Bizagi strongly enough.
I have been using Camunda and BizAgi, amongst some others, during an evaluation.
Both are easy to use. My business peers tended towards Camunda because we would get a native language speaking support (in German). (However, for very other reasons we did choose something very different).
Camunda Platform allows for visual demonstration and presentation of business process flows. The flexible Java-based option was a big win for us and allows for the integration of microservices very quickly. Camunda Platform is very stable, with a free open-source version that is very good. The automation is great.
Camunda Platform can be challenging regarding the initial setup, though, and it seems to take a long time for completed workflows to be implemented. The learning curve for this Camunda Platform can be pretty steep. A mobile app would be a welcome enhancement. Process interfaces between diagrams could be improved and better template options would be welcomed.
Apache Airflow integrates well with other pipelines and solutions. We like the direct support we get from Python using Apache Airflow. This makes work and automation much easier. Apache Airflow handles complex workflows and coordination of tasks easily. We can use it to manage large-scale data processing workloads using DAG, which is a core component of Apache Airflow.
Using Apache Airflow is okay, but managing it has its challenges. We would expect better scaling, especially since it is on the cloud. Apache Airflow is also not a great solution for those who are not tech-savvy. (It is not for business-end users.)
Conclusion:
Both of these solutions require some level of technical expertise to implement and manage, which is something to keep in mind.
We felt Apache Airflow offered better integration with the solutions we are currently using. We have a solid relationship currently with Python and are using many solutions that make Apache Airflow the best choice for us.
Pega BPM allows for a great deal of flexibility in terms of how an organization or company can set up this solution. There are two possible ways that this product can be deployed. Each of these has a different level of setup difficulty. The first option involves a completely cloud-based approach, linking the program up to the cloud and connecting it to your organization’s online databases. At that point, most of the work is being done by the program and the cloud itself. Option two is more difficult to implement. This option involves installing the software on your company’s local servers. This requires a great amount of work to properly integrate the software with the local hardware. You will want to hire experts in this type of technology to run the integration and manage the software.
Camunda Platform is relatively easy to set up if you are not attempting to tweak the software to gain extra functions out of it. It can be downloaded and deployed within a half an hour. However, if your organization wants to get more out of the program than its most basic functions, the process becomes more complicated. Additional time and resources will be required if your company wants to add things onto the software.
Pega BPM has a variety of payment models. They offer options that scale their prices based on the number of users or the number of cases that the organization has. These are just two examples of the flexibility of pricing that Pega BPM can give businesses.
Camunda Platform is even more flexible on price than Pega BPM. They have an open- source version of the program which is absolutely free. This version possesses all of the core features of the paid version. The ability to maintain functionality and not have to pay expensive licensing costs is a game-changer.
Conclusion
Both of these products are potentially easy to set up. Pega BPM offers great flexibility in terms of pricing. Ultimately, Camunda platform’s open source version is more affordable without sacrificing functionality.
I can't give you a good reason to skip over Bizagi. I have been using Bizagi for over 4 years and have gone from total low-code skeptic to low-code evangelist and a strong supporter of Bizagi. It's available for no cost to learn, develop, and test/pilot process automation (up to 20 users in test), and has very reasonable licensing options for production once you are ready to go live. It also is powerful and flexible. We're even using it to drive our docket and scheduling system for hearings (not something one things of doing with a "process automation" tool). Can't recommend Bizagi strongly enough.
I have been using Camunda and BizAgi, amongst some others, during an evaluation.
Both are easy to use. My business peers tended towards Camunda because we would get a native language speaking support (in German). (However, for very other reasons we did choose something very different).
Hi, i have not use Camunda platform yet
@ValeryTezo , maybe you can help?