We started doing it in-house because we wanted to acquire knowledge about that. After a few weeks or months, as we were getting closer to our production date, we got the Camunda Enterprise version. One of the things that came with that license was support from Camunda. So, we contacted them just to update how we did our configuration. They found that we had a lot of instance processes, and because of our level of history, it had a lot of extra data. They provided us with scripts to help clean our database from unrequired data. So, in the beginning, we didn't take any help from a consultant or Camunda, but as we were near our delivery dates, we took some help. Even when we were in production, we had some issues. We contacted Camunda for some things that were not working correctly. It was just to get advice on how we installed things. It was okay, but it required some adjustment.

In terms of the number of people involved in its deployment, because it was something that was considered complex, I did it myself just to have the basics, and after that, when there was something to adjust, the team did it with me. So, it was me, and there was a team that came after.

In terms of maintenance, the way they have made it, it is pretty low maintenance. If you want to upgrade the version of Camunda, you just have to go into the dependencies to adjust the version. Inside the version, there's always a migration script that is embedded in the version. So, it isn't self-maintenance, but you just have to change the version, and everything is done magically.

When it came to deployment, there were readily available options, along with clear instructions tailored for an open environment. We have it deployed on cloud as well as on-premise. The deployment timeframe varies, measured in hours or days, contingent upon specific customer requirements. Frequently, we initiate development, reproduction, and production environments. However, delays may arise as these environments can differ slightly, necessitating additional setup time.

Everything was done in-house. I built a very knowledgeable technical team. We had DevOps, and we had frontend and backend engineers. We had a complete team dedicated to making the startup grow. There were two to three people doing the work for a few weeks, and we have been able to make everything work.

It is easy to maintain, with the exception of the database. For the Camunda instance, for example, it is very easy to maintain the licenses. It is easy to attach a license to the container, and we are good to go, but we also have to take care of the database. We have grown so fast, and in order to not have a huge Postgres database, we have to delete some of the instances, such as instances from a day earlier. We are deleting the processing history because the database couldn't handle all the data that was passing through it. Maintenance-wise, that's what I remember the team complaining about.

We did it in-house, but we did use some consulting from Camunda during some of our initial days. One of their solution architects was really good in terms of technical knowledge. He knows the product really well and he guided us through some of the parameters and tuning of our clusters while we were deploying.

In addition to me, we had one more person doing the deployment. One of our senior people took care of the deployment on our side. I was overseeing things but he did most of the work.

I did the tool's deployment myself. 

It requires maintenance such as patching and other regular tasks.

It took around a week to deploy Camunda by one or two people.

We brought some people in to assist with our implementation. They were supposed to be experts, but they weren't that great. They wanted us to make much wider use of it, and we only wanted to use it quite in a small way. So, we paid for a bit of consultancy, but then we didn't keep them on.

They were typical London consultants. At £1,800 (approximately $2,400) per day, they were ridiculously expensive.

It is only a small team that maintains it. Right now, we only have one person for that.

The deployment process utilizes DevOps practices. We make use of tools like Docker, which are suitable for various platforms and easy to use.

The deployment usually takes around five minutes. This includes steps such as packaging, configuring the environment, installing the application, and allowing the server to start. The entire procedure is completed within five minutes.

Moreover, it can be managed by a single engineer or developer who has experience with CI/CD, DevOps platforms, Docker, and related technologies. 

Although not a junior developer, one knowledgeable person can handle the deployment process. In our case, we had one individual who handled the deployment for us, and for subsequent applications, each of us was responsible for maintaining our own application.

We did it internally.

We have an in-house team for deployment and maintenance.

We have an in-house team of two resources that maintain the product.

Camunda Platform's deployment was done in a day.

Of course, we do not use an integrator, reseller, or consultant for the deployment because we are in that role. We know how to build it and we know how to run this kind of project. In the beginning, we did make a lot of mistakes, but at the end of the day, it works. Now when we have a new customer, we know what to do.  

I did not use an integrator, I did it on my own.

We implemented Camunda BPM by ourselves, in-house. 

We implemented the setup of Camunda BPM on our own. We did everything in-house. Within a week, it was done. We implemented pretty fast.

We implemented this solution through an in-house team. The installation was done internally, by the systems area in our company. 

We are an integrator and we are consultants in business process management, and we are developing a tool on top of it. Therefore, we help our clients to implement. However, when we originally installed Camunda, we handled the process ourselves. The way we do things now, we try to make it easier for clients.

We performed the implementation ourselves.

We handled the implementation in-house.