We have three instances of Camunda running, and inside Camunda, there are multiple business processes for different solutions. For example, we have different types of permits. Each one has its own business process, and everything is deployed on Kubernetes. We have about 10 or 15 endpoints that are used through connectors.

Its setup was a little hard. The documentation was not that great at that time, and they had a lot of versions. What made it hard was that their recommendation was changing. For some time, they were providing a Docker image, and then they changed to what they call a green stack where we were using spring boot to achieve that. I'm not sure what it is now, but I know that it changed again. So, it was hard to follow the best practices related to Camunda at the beginning. It came down to documentation.

Overall, it took weeks. To have something running was fast and took days, but we had a lot of tweaking to do. To be advanced in our solution development, we did stress tests and had a few problems with that. We were trying to adjust the configuration, and the documentation was not always easy to read. Sometimes, the configuration was easy because we had to adjust the configuration just with the XML file. Sometimes, we had to go a little further in Java. There were different levels of tweaking. Overall, it was fast to have the initial version of Camunda running, but it took us a lot of time to have something production ready.

The initial setup was very easy and flexible.

The solution is deployed on-premises.

The product's initial setup phase was neither an easy nor a difficult process, though my company did receive support from Camunda, considering that I work in a big company with firewall products in place. There were some hurdles during the setup phase, making it a not-so-smooth process, but my company was able to deploy the product successfully in the environment.

The solution is deployed on an on-premises and on the cloud model.

I was here during its initial setup. It took quite some time because it also had to adhere to our architecture. We had to do some modifications to achieve this. It was quite intensive at the beginning. At the time, Camunda also provided Helm charts and other things, but in the end, we had to adjust too many things. So, we basically prepared our own automation in order to deploy the platform. It took us some time to make that automation ready. We wanted to have an easy way to apply the platform, and that took us some time. It was like an arrow that was dragged back, but in the end, it made us faster for new changes.

In terms of the deployment model, we provide it only as an internal service to Swiss Re itself. Currently, it's a hybrid setup. Parts of the solution are in the public cloud and parts of it are in the private cloud. It's deployed at multiple locations where the orchestration part is in the public cloud and the majority of the workers are in a private cloud. We have this sort of distribution of the platform.

In terms of the implementation strategy, we started the evaluation in 2019. We had multiple products. We did the proper requirements engineering and decided to go with Camunda. Before going to production, we organized Hacktoberfest where we invited our existing customers who were on the legacy platform. We let them try it out to see how it is for them. We got quite positive feedback from them, and based on that, we started the process of onboarding it.

Within Swiss Re, there's a standard process called the digital governance framework. We have to go through this extensive process where licenses are reviewed with regard to security, architecture, exposure to the network, etc. All these things are reviewed in this process. Within that process, we also have to do penetration testing to see if the system is viable for our use case and if it's secure. It was 2020 when we got everything approved. From there, we started with the migration. Along with the migration and complete evaluation, we onboarded new people to the team who had different skill sets required in order to run the platform in the future. So, we built up a new team in Budapest and also upscaled our existing team.

In the first phase, we mainly targeted people with a certain knowledge of IT and engineering. For them, it was easy to implement the workflows and so on. In the next or current phase, we are trying to introduce the platform to business users. In order to do that, we have to further improve the UI so that it's also easy for a business user to create a business process in the future. We are not there yet. It's an iterative process where we sit together with business process owners and try to find out their demands and adapt according to the demands. We are trying to avoid big-bang approaches and proceed in an iterative way, and with Camunda, we have the capability to iteratively improve ourselves.

For developers with a development or software engineering background, it's quite easy to implement Camunda. For those who do not have that knowledge, my team provides a service. We go to the teams and help them with the implementation of the workers and the workflows. So, we support it on an end-to-end basis. We get the requirements, document them, test them, and develop them. We cover all these things as an end-to-end service, but the goal for us is to move more and more toward a self-service platform. Until then, we will operate in a hybrid mode. So, currently, there are people who can do it themselves and deploy workflows, and there are people who require help from our side. Until we close the gap with self-service, we will support the people or designers. For business users, it's very important that it becomes very easy to use. Having an easy UI where they can drag and drop in their workflow and test it in a non-intrusive way is quite important going forward. It would be a success factor in the end. If we want to succeed in the business areas, we have to provide an easy platform that can be utilized by any person with limited knowledge of software engineering.

The installation was very simple. With Camunda, it's very easy in comparison with other products.

We set up a dev environment and a laboratory environment, and it took about five days, max. We hoped to expose Camunda to our end-users, not only IT users but also business-type users.

I would rate my experience with the initial setup a nine out of ten, with ten being easy. Installing Camunda on your machine is incredibly easy. It's even easier than installing MS Office. I also installed IBM BPM on a virtual machine, and that took me one or two weeks to configure fully. Camunda is much simpler in comparison – the process is similar to installing MS Office.

Most customers I have are in the banking sector, so they prefer on-premises deployment. 

It takes around three days to deploy the solution because it includes things like permissions etc. Camunda is significantly quicker to deploy in comparison to IBM BPM, which takes around ten days. 

I'm a developer, not an administrator. So, I usually work with the administration team for the actual deployment. Typically, we need a few key files: one for the setup and one for the Camunda server itself. I'm familiar with the server file since I have Camunda installed for development on my own computer.

The initial setup was straightforward. I would rate it ten out of ten.

It is kind of straightforward. We have everything configured as infrastructure as a code. So, we got the best practices from Camunda, and we wrote our deployment instructions for Camunda's deployment as code by using Terraform. We did that on our side, but it would be very good if we can get it from them, but I understand that each client probably wanted to have their own method of deployment.

Camunda's deployment was easy, but fine-tuning the Postgres that we had as the backend database wasn't easy. 

After the deployment, it took us two to three months to wrap our minds around how to use it correctly. After that, it was a matter of creating templates that our team would be able to leverage and start using more and more. It isn't a very difficult product to understand. It has its quirks, and that's the part that you have to learn and has a steep learning curve, but when we did our due diligence, Camunda seemed to be more mature and straightforward than its competitors. I value it very highly.

They provided help charts, so it was pretty straightforward. But when you want to tune it or run it on an enterprise level, you will want to try out a few of the parameters they have provided, and play around with them, to ensure that the software components that your cloud provider has can be used smoothly for deploying Camunda. Initially, you might have to make some effort to set things up on your own cluster, but they have good documentation and help charts for deployment on your Kubernetes.

We have different environments, including development, testing, staging, and production. We could even implement a CI process for our workflow instances and BPMN files, as they can be deployed using a CI/CD pipeline. Microservices can be deployed at their own pace in a CI/CD pipeline. That was the strategy for deployment.

Camunda's deployment is easy. You need to click some buttons. 

I was responsible for the deployment; we had one person dealing with the structure and another for the implementation. The initial setup was straightforward and fast. Everyone in the company uses it, we have around 200 employees. 

The initial setup is not too complicated.

We started with the analysis. The implementation depends on what you are asking for. We had a few discussions with the developers about what I expect and they developed and implemented it in about two months with about 10 days of work.

I have to say that the developers I cooperated with had previous experience with Camunda.

The product's initial setup phase is difficult for beginners.

The solution is deployed on the cloud.

Camunda is easy to set up. The initial setup was fine until we had an issue with execution times not being guaranteed. That took quite a number of weeks to resolve. 

We developed this platform on-premises and we deploy through AWS.

Setting up the software development process is not difficult for me because I am knowledgeable in this area.

Since the process is mostly Java-based, there is no need for me to do any training. However, the aspect of training poses a challenge due to its high cost.

The initial setup was straightforward. That was what I was able to accomplish. 

It took me approximately two to three hours to complete the task. I had to refer to tutorials and make some adjustments on my computer, which consumed some time. As a developer, I found the task relatively easy to handle.

I deployed it. But it was not a major inconvenience for me. It was deployed a year ago.

The initial setup is quite easy - I set it up in 30-35 hours.

I rate the ease of setup seven to eight out of ten.

The initial setup is difficult to adapt. It takes two to three days to complete.

It is not overly complex to set up and implement if you are already a Java developer. For Java developers, it is quite straightforward and manageable. 

However, if you are, for example, a PHP developer or someone working with a different technology stack without Java skills, it may be a bit challenging to get started with Camunda. In such cases, I would recommend seeking assistance or guidance.

Camunda is a highly documented platform. I really appreciate that aspect. When I started working with Camunda, I made sure to read all the documentation for the APIs and other related information. It's a well-documented tool.

Its initial setup is straightforward.

The setup process is easy. It was the primary reason to opt for Camunda.

We did not encounter any issues during the installation or while building the workflows. We implement the tool for our customers.

It was simple. It took us about three or four weeks to deploy the first portion or first draft of BPM.

In terms of maintenance, it is okay. It doesn't require anything specific.

I know that the IT team needed some help, fortunately, we have a good connection with them, so we worked together to set things up. In the beginning, it was kind of hard.

As we experienced some difficulties in the beginning, deployment took almost a month.

The Camunda installation is very simple. For example, if your project requires standalone applications, Camunda can provide the necessary external components to complete the installation. The setup can be a little more complex when compared with other applications such as JBoss, but overall it only needs a few extra configuration steps.

The installation is quite straightforward.

You log into the Camunda website and download the folder to install it directly.

The installation process took 20 to 25 minutes.

We configured the integration and the UI.

The initial setup is straightforward, especially with Spring Boot Camunda Starter. The configuration is in application.yml files.

The initial installation was not difficult for us because we had already some experience with the solution.

It was very simple. We are using the web solution, and it was very easy and quick. We could start using it in one week.

The initial setup was not straightforward. The complex part was to load or update the backlogged events. So if I have a process, which is already past the flow to a certain stage, after the implementation, if I did not start from scratch, you would need to make the data or the workflow that you have current with the process. Making it current with the live process monitoring is a nightmare. It takes a lot of development effort, a lot of data validation, and a lot of workarounds to bring this up to speed.

I have not seen that there is too much support in being able to bring in existing services. For example, if someone has an existing process, an existing instance with existing data, which is not linked, there is no explanation of what the best approach is and how to load and how to bring this into the new process and make it current, covering the backlog.

This is especially true if the backlog is something that would be crucial for some of the processes that are down-line. For example, in the case where you have a successor process where it depends on the predecessor too much in terms of the decision, and also in terms of that project. Normally, we deal with delivery on projects, so we look at the delivery and the forecast and the delays. So to see the project delays, sometimes we need to go back in time to see whether the delay was in the first stage or on the second stage or on the third stage. Based on this analysis, we always create our baseline by the end of the year and reiterate on our scopes at the beginning of the year.

At Camunda they had a subscription service. It was based on how many flow nodes, I think 4 billion flow nodes, and they would give you a one-time fee. You just had to pay it, and you got internal support.

Of course, you can use them without their support. You can just download it and use it, but any self-respecting entity will get support. Where they make money is not licensing. They get it in support because, sooner or later, you want help.

They have various subscription models. One of them is pay a one-time cost, and they'll support you.

The solution's initial setup is quite straightforward. I rate Camunda Platform a six or seven out of ten for the ease of its initial setup.

The setup was straightforward. We need to have Java, and that is it. My team does the work on the deployments so I don't know exactly how long it takes anymore. But it is a simple concept that the more complicated the client's needs and use cases are, the longer it will take.  

We do deployments with just two people: one senior and one junior tech. But it depends on the complexity of the workflow. Sometimes we might bring an extra tech if the workflow is complex.  

The initial setup was straightforward.

It was deployed a year ago, so I can't remember exactly, but I think that I only took a few minutes to deploy.

The initial setup is straightforward.

The initial setup is a bit complex.

The initial setup was straightforward. We didn't have any issues.

The only issues we could have would be with our code.

The initial setup was complex. We really needed to study and understand how it worked. It was difficult because we didn't have enough information in the manuals.

We did what was said in the manual and then wanted to do more. We watched several videos, and we started to connect the dots. With our own solutions or conclusions, we were able to implement Camunda BPM.

We took responsibility for the setup and it was straightforward with community help

The initial setup of this platform was very simple.

I think the setup process is simple. It's not very complex because we have installed it several times for the development area and for the production and we have not had any problems. I think deployment took no more than about two or three days—it was not difficult. 

The initial setup was very easy, I did it myself. 

The initial setup, for business users, is complex. If you compare it with cloud systems and Mendix, it is complicated. It has a very strong and very rigid back-end BPM engine and it's more trustworthy if XML files have been generated from Camunda. The quality of the XML file being generated from Camunda, the XML files of BPMN, is more trustworthy than other systems. That's why we selected it. This is the main reason that we selected it.

With the Camunda installer, the deployment of just the solution is pretty fast.

However, the automation process with the current functionality, meaning with the missing functionality of data monitor and data binding and with the lack of proper UI representation, it took us a year to develop those components to have a low-code solution on top of it.

Now, with our low-code solution on top, it will take us one to two days to have a visible process automated.

I would say it's medium complexity to setup. You do need development skills but the experience has been clear for us.

It depends on how you set it up. If you want to set it up for demo purposes or development and start working with the product, the set up is fast. The first one I installed took me five minutes and it was running.

The initial setup is pretty easy. It depends on the people who are installing it. It generally takes a few days.

Our initial setup was quite complex and took around six months due to some bureaucratic issues. However, I think that it could be faster for organizations without such issues.

The initial setup is not that complicated, but it isn't easy either. Deployment took a few days. The deployment time depends more on the complexity of what you want to do with Camunda than the size of your organization. 

The initial setup is very straightforward. 

The solution's initial setup has a medium level of difficulty. It's not as easy and it's not hard. Maybe someone who is starting out and doesn't have any experience with any other framework may get into some headaches. However, I've worked with it now and for my level of expertise, it's got a medium level of difficulty to set it up.

The initial setup was very easy, but we haven't deployed the program yet, as we are still only testing it. We have tested how to deploy new processes, how to use the clips to deploy processes, and how to integrate your modeler into clips. If you are referring to these issues, I think the provided documentation is quite sufficient.

The initial setup is straightforward, but if you need to tweak any part of the it, it can get complex.

The initial setup was straight out of the box, and very easy.

The initial setup is easy. I wouldn't say that it is complex at all. They deployment takes only a day. If you don't want to use something specific then you can install it in two hours.

To do the initial setup, to get it up and running, is not complex and it can be done in less than two days. When you want to move it to production you have to set up the security, the front end, and the business layer. If you are using it internally then it is ok, but it is more complex if it is going to be used by the public.

The initial setup was complex and it took us five days to deploy it.

Installing the server side is easy. Just click on Download button at the site, unzip and run. The modeling tools can be downloaded and run on premises or directly from the cloud.

The installation is not difficult.

I would rate the ease of install level an eight out of ten.

It took a while, but I believe it was more related to us; it was not specific to Camunda.