We just raised a $30M Series A: Read our story

Appian Competitors and Alternatives

Get our free report covering Pega, ServiceNow, Camunda, and other competitors of Appian. Updated: October 2021.
542,267 professionals have used our research since 2012.

Read reviews of Appian competitors and alternatives

Abdurrahman Gori
Technical Manager at a comms service provider with 501-1,000 employees
Real User
Top 5
Component reusability saves us development time, but the learning curve is too steep

Pros and Cons

  • "The best feature is the automation."
  • "The only drawback is the time that it takes to have a complete set of workflows implemented on the Camunda platform."

What is our primary use case?

We use Camunda for the automation of the workflow and business process designer. We use the module cockpit and the workflow engine to orchestrate the process. We are a consulting company and we're not doing this for internal purposes. We mostly do this for projects, and these projects are for our clients.

The environment where we work is very dynamic and is changing a lot. So based on the circumstances, we mostly work on the delivery parts, as in project deliveries. At the beginning of the year, we have a clear scope, clear targets, but down the road, we face a lot of challenges where we face many dependencies. We need to constantly go around the dependencies and change things back and forth.

We have a lot of experience in the development, on the ERP, and so forth. We have seen that investing in a tool like Camunda is valuable, especially because it's an open-source product. When you do the customization, you'll be enriching and increasing the automation possibility of the product. So, the value is always increasing.

What is most valuable?

The best feature is the automation.

Camunda supports microservices and you can do multiple things. The most important thing is that you can reuse components that you have within the product. For example, let's say that I developed a workflow for a quality review; that is a workflow that can be reused in any new process. I can just ship it, plug-and-play, copy it, and reuse all of the features and components that are there. It means that I won't be spending too much time in terms of development to put it in place. To me, that is the most valuable thing about the product.

What needs improvement?

The only drawback is the time that it takes to have a complete set of workflows implemented on the Camunda platform. This is from drawing the modeling and the workflow up to the production release.

The support definitely has to be improved.

Second, it needs to be more intuitive. As it is now, to develop an automated process in Camunda, you would need to involve a front end developer, backend developer, and sometimes, someone who has experience with modeling. Where in Appian and Pega, you would be able to simply reduce these overheads by creating the process, the flow, and converting it within certain boundaries into the automated process.

The visualization part can definitely be improved. You can see the process moving live, but if you have a complex design where you would like to show the process in a different shape, that takes a lot of customization and a lot of coding effort to put this in place. The visualization needs not a little or a medium amount of work, but rather, it requires a lot of improvement. At the end of the day, we have the process, we have the workflow, we have the event, we have everything. However, what the people see at the end of the day is what they believe. So sometimes we know that we do have a lot of data and a lot of information, but we fail to represent this information in a way that meets or addresses the business requirements. Better visualization capabilities would help in this regard.

For how long have I used the solution?

I have been working with Camunda BPM for almost two years.

What do I think about the stability of the solution?

I would say that it is stable, at least up to a certain extent. Whenever there is an update to the product available, we go ahead and update it to the latest.

What do I think about the scalability of the solution?

This is a scalable platform. We have about 600 users and about 20 superusers. The superusers are developers, admins, and process engineers. They are a mix of process, business support, mobile app developers, and so forth.

How are customer service and technical support?

Support is an area that is in need of improvement.

First, they don't have a strong knowledge center. If there is a challenge or there is an issue and you would like to look around, it's not straightforward. Their knowledge center does not address most of the challenges that a person who goes through the cycle from scratch. In building the process and building the products and building the workflow, a person will go through a painful process if they don't have enough experience.

When I say enough experience, I mean a minimum of 16 to 18 months. If someone doesn't have this experience on Camunda, it will be difficult and they will suffer to get things up to speed. The learning curve is too high, so they can do more if they enrich their knowledge center.

The second problem is that the support services from Camunda are not straightforward. When we communicate with them, they have to evaluate you. Sometimes they charge you per workflow, but there is no standard model. It is difficult for us because we have an agreement with the client that at the beginning of that project, we put in our estimation as to the required resources in terms of the infrastructure resources, and in terms of logistic resources, and support. With Camunda, because of the undefined or non-standard costing, that becomes a challenge.

So sometimes we go to a client and we see that the support costs will be much higher than the benefit of the digitalization. That's an example where we decide to do only the modeling for that client using Camunda and the classic workflow development will take place. This is the case, especially for small and medium businesses. For enterprise clients, definitely, we always go with full-fledged support.

Which solution did I use previously and why did I switch?

I have limited experience with Appian and Pega BPM, but my most in-depth experience is with Camunda BPM. We did a pilot project with Appian for one or two months and we did one with Pega for about one month.

During our evaluation, we have seen that there are pros and cons to all of them.

We also used K2 as one of the platforms, as well as Microsoft BPM. The Microsoft product was a combination between Dynamics and SharePoint and so forth, it was really rigid. Similarly, K2 has a lot of limitations.

This is important because once we get the business requirements, we adapt to the system. We don't force the business to change, especially in this region. We are in the Middle East, Gulf area, and working with the government sector means that they have their own standards that we need to comply with. They have their own procedures where the tools, the IT, and the process have to be adjusted to meet their requirements. For example, consider a supply chain and the procurement process. This is different from one organization to another.

This is the main thing that holds us back from investing in a system like Pega. Pega, to a certain extent, is good. It has most of the capabilities. It also gives you the room to customize to the extent that you feel fit. However, the cost is too high. When we talk about the licensing costs and the customization costs, it's extremely expensive and out of reach.

How was the initial setup?

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.

What about the implementation team?

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

What's my experience with pricing, setup cost, and licensing?

The cost of this solution is better than some competing products.

What other advice do I have?

My advice for anybody who is considering Camunda BPM is that they implementing a PoC first.

I would rate this solution a six out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
MallikKesavaraju
Scaled Agile Consultant at Anthem Blue Cross Blue Shield
Consultant
Top 5
Good case management and BPM workflow with easy cloud implementation

Pros and Cons

  • "The solution's case management is its most valuable aspect."
  • "They are currently spending some time on improving the product with respect to machine learning, especially related to robotic automation. They probably could be a little more adept on that area would help."

What is our primary use case?

The solution is basically a quoting application. When insurance brokers or internal users have to call or do insurance quotes for commercial insurance, we use Pega. The insurance we cover is for outdoor coverage and for a casualty to property, as well as casualty insurance.

What is most valuable?

The solution's case management is its most valuable aspect. 

It's basically an open architecture based software, which means the main aim of the software is to provide a low-code application development environment. It has several authoring tools on the UI flow and makes sure that you can put in a lot of gadgets and create the screen very quickly using those gadgets.

Right now, it has a pretty good feature set. It has case management and BPM workflow as well as robotic automation. It has decisioning. It has chat and virtual assistant support, and we just implement it on the cloud, therefore it's a pretty robust feature set.

What needs improvement?

They use something called a unique model-based architecture. During development, where the database and the UI, everything comes from one single piece of architecture. Due to that sometimes the enterprise architecture teams do not like it due to the fact that it forces them to use just one piece of architecture. If these could be more modularized, then it can be easily deployable in different kinds of scenarios in organizations, it would be much better.

However, they are kind of tightly coupled and it's difficult to separate everything out. Still, I would say it is an improvement to consider for the future. Id they could decouple the various components so that it gives flexibility to enterprise architects to deploy what is most needed as part of their enterprise architecture strategy, rather than getting kind of, looking at the only way the product handles, it would be a stronger product.

They are currently spending some time on improving the product with respect to machine learning, especially related to robotic automation. They probably could be a little more adept on that area would help.

It's very difficult to change many things unless somebody puts in the time to figure everything out. However, Pega could learn from all the customer service calls they get and categorize them in order to do an automatic form-based or customer service based response. If they could set it up to everything automatically, then that would save a lot of time and headaches for companies and help them troubleshoot and work through issues faster.

For how long have I used the solution?

We've been using the solution for almost ten years. We haven't used in the last 12 months too much, however.

What do I think about the stability of the solution?

We have found a few issues on the solution and we work closely with technical support to help fix them. While it is largely stable, we do find we need to keep up with problems and work closely with Pega directly to address and fix them when they arise.

What do I think about the scalability of the solution?

In terms of scalability, provided you throw hardware at it and you do a proper production implementation approach and alignment strategy, it's scalable. 

You can go up to 2000 to 3000 users pretty easily. It's just that you need to throw a lot of hardware at it and make sure that you manage and create the web servers required. You need to create various pieces such as database servers and things like that, to make sure that you get the performance you need for those 2000, 3000 users.

The solution is being used continuously. I'm not sure about the increase in the usage, but at least it's serving the purpose as needed for the brokers.

How are customer service and technical support?

It's a complex piece of software. For that reason, we did find some issues and I was kind of instrumental in working with Pega on their global support model. We had weekly calls to review. They have a process to track issues that are unique. Sometimes it's handled by their support network, and sometimes the issue is taken up to be dealt with by working on the next version. For us, triage calls are made every week.

How was the initial setup?

The initial setup is never straightforward. It's always complex. Organizations deploying the solution will need a Pega admin and experts. It's not like anybody can just walk in and install it onto a PC. It needs a lot more performance concentrations and much more integration considerations. Therefore, it's a little complex.

In terms of deployment times, on-premise, it takes a little more time, and I would say it would take maybe about a month. However, now, cloud implementations are pretty quick and go much faster.

In terms of maintenance, we do need someone from the company to help us manage the solution.

What about the implementation team?

We did solicit outside assistance for the implementation. We actually used both the Pega professional services in the beginning for a short time and then a subsequent implementation was done by an integrator.

What's my experience with pricing, setup cost, and licensing?

There are multiple models. They have enterprise licenses for each server, for the product version. If you're doing it on-premise they also have per user basis on their cloud. 

It depends on what your specific need is. Those vary from customer to customer, depending on the number of users and the volume of business and things like that. There's no, set price, or a specific quote and everybody just follows it. It's more they work out the enterprise licensing agreements or per user basis with respect to each client.

Which other solutions did I evaluate?

I joined the company when those decisions were already made. I wasn't part of that decision. However, in a lot of places where I've consulted as a digital transformation consultant, we did definitely compare Pega with competition such as Appian and other BPM, and even Salesforce and other workflow systems as well.

What other advice do I have?

We're just customers. We don't have a business relationship with Pega.

Pega BPM is definitely one of the topmost BPM packages out there. It hits all the right notes for a containerized implementation. The only thing you need to be careful is that you definitely need experts to help you along the way, in both the design and the requirements capture. They have an excellent requirements capture tool as well. However, if somebody needs to be trained on that, you need the help of experts, both on the software architecture as well as business architecture as well as the Pega admin. Eventually, these kinds of positions will either require a company to staff up or they will need to work with a system integrator. 

Most of the companies work with system integrators due to the fact that Pega professional services are definitely very expensive. Organizations will work with a company life Cognizant or Accenture or others to really help them out along the way.

I'd rate the solution nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
AnilKumar4
Senior Developer at jarvis
Real User
Top 10
Offers good integration and has good stability

Pros and Cons

  • "Features they are integrating to the other services."
  • "They need an easy way of getting details and then adding to it and then being able to do it in a more simplified way"

What is our primary use case?

We use the mobile application, the Lightning application. We use it with consulting and integrating the different products like vCloud or integration with Google. There are some that we do production also. Everything is on mobile now. So we use mobile apps and then we develop those applications. It's a Cloud browser and device support that we are doing the programming. So basically now we are developing that in the Lightning Application, where we can. That is based on the event architecture and by the company's controller, we write those according to that. We develop the programming that will go to the software, we need to have the APEX programming materials for the IBM system, or with Lightning RAWC, who with integration we need to go with other configuration tools. So there are a lot of things that need to be captured in developing the project.

What is most valuable?

They also have features they are integrating to the other services or managing the technical management or you can go with the integration point of view and you can able to, in the build tool, do the configuring of those things in terms of other approvals or like customization. And you can include the time bond overflows for the emails. So all these parts come from the Salesforce only. So Appian does not have it, it comes with that only and now we are able to do it.

What needs improvement?

If you compare it with Appian, there are business rules that you are dealing with. With less code, we are making a higher standard. So maybe, in the future, Salesforce can make it a more integral part of the application. And they are also strategic partners with multiple companies, so maybe that is the reason they are sustainable and they the four versions every year. These things likely depend upon robotics programming and they use the latest technologies for a more stable portal. So we need to be more cautious about the coding and so data file would be more stable. But as a partner, there will be some time-taking process to make it up in the implementation. When you compare with Appian, they have to improve more on configuration and more systematic care, configuring by itself and if they are making other things in the area that they update. 

The process should be automatically approved. They should also configure the maps that we initial use. I think the alerts can be used differently, or customize the targeted content mills can also be automated. Those things can also be included in Salesforce. I was looking at this map that needs to be included. Like a world map. An easy way of getting those details and then adding to it and then being able to do it in a more simplified way, visually.

For how long have I used the solution?

I have used Salesforce App Cloud for two years.

What do I think about the stability of the solution?

Stability is more than adequate. It takes a number of developers to handle that currently. Most of the people don't know that a lot of features are developed with rules. Unless you are a developer you won't be able to design it currently. So it's easy to do a mini-platform now with Salesforce. That may be the strategy, but if it is having combined information within one platform, it is stable.

How was the initial setup?

At first, the setup can be difficult. But once we get it deployed and get our tools implemented it is more automated. We have now set up a solution that allows us to easily deploy quickly. So once you understand the coding program, then it was easier for them to deploy. It usually takes about a month to deploy.

What other advice do I have?

I would rate the Salesforce Cloud App at an eight out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
VK
Associate at a tech vendor with 1,001-5,000 employees
Real User
Top 20
Constructs the system based on all the requirements of your business

Pros and Cons

  • "Newgen will structure the system based on all the requirements of the business. We can design the forms as complex forms or make our own versions to fix what's wrong."
  • "In terms of stability, like every product it has its issues."

What is our primary use case?

This solution is deployed on-premises as well as on the customers' cloud environment. Its primary use depends on the business requirement. Newgen will structure the system based on all the requirements of the business. For example, we work in the finance domain and it helps with the banking process.

What is most valuable?

There are a lot of features in BPM products. We have evaluated those features from OmniFlow iBPS and appreciate their intelligent business process management where we can design the forms as complex forms or make our own versions to fix what's wrong. We have incorporated the bootstrap technologies into our product.

OmniFlow was previously based on Java fees for designing the forms and now it's independent of Java for their product.

It is plug and play now. Previously, we had to do a lot of customization if we needed to implement a solution for the business and it would take around three to four months or a year for a banking process. It took at least six to seven months to implement and roll out into production. Now, the scenario has completely changed - it's just plug and play. We have a lot of accelerators so we can do two to three months to roll out into production.

What needs improvement?

OmniFlow used to design the same old forms. Now, we design intelligent forms so we can drag and drop the forms and control its form responsiveness. Previously, we didn't have any responsible kind of form design and now it has responsive forms. It will be supported to mobile for all the devices if it is a responsible form. So with the mobile support text and online route deviations, everything will be online.

For how long have I used the solution?

I have been using Newgen OmniFlow for six years.

What do I think about the stability of the solution?

In terms of stability, like every product, it has its issues. Stability increased now. So we don't have many issues.

What do I think about the scalability of the solution?

There are no issues with the scalability of Newgen OmniFlow.

How are customer service and technical support?

We have 24/7 support as per our policies and I must say we have the support we need to provide to the businesses. They provide the best support.

Which other solutions did I evaluate?

We evaluated OpenText and Appian.

What other advice do I have?

On a scale of 1 - 10, I give Newgen OmniFlow an eight. I have six years experience in Newgen and we have implemented our own Newgen now with 2,000 to 3,000 implementations since then. We have a huge customer satisfaction rate because we try to accommodate all the requirements of their business. We cannot say, "No, it's not feasible," because everything is feasible from the Newgen BPM.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Implementor
TW
Chief Technology Officer at a financial services firm with 1-10 employees
Real User
Top 10
Valuable business process management tool with low-code requirements

Pros and Cons

  • "The features that I have found most valuable with Mendix are its business process management and its minimal low code, both from an interface perspective and from a process perspective."
  • "Mendix is slightly less scalable than I'd like."

What is our primary use case?

We have a loan origination platform. What we're looking to do is have a dynamic process whereby, based on a variety of inputs, we can tailor the journey. At the moment, we're debating how that kind of journey works and if we put some kind of workflow in place, then firstly, this becomes a living documentation and, secondly, it's quite easy to be flexible as to how to adapt each journey rather than correcting one great big process. We wanted to break it up into smaller journeys. If each stage is isolated it becomes easier for each change that you want to make. That was the logic.

What is most valuable?

The features that I have found most valuable with Mendix are its business process management and its minimal low code, both from an interface perspective and from a process perspective. With Camunda, we were looking at it from our business process standpoint. Appian and Mendix were one size fits all.

What needs improvement?

In terms of what could be improved, of course I'd like it to be highly secure and highly scalable. Security is paramount to us. Scalability-wise, we don't necessarily have a huge volume.

From a scalability perspective, at this particular stage, it's not necessarily a top priority.

For how long have I used the solution?

We started this journey with Mendix just a couple of months ago.

What do I think about the stability of the solution?

It is a flexible and stable solution.

What do I think about the scalability of the solution?

Mendix is slightly less scalable than I'd like.

We have 30 internal users. The issue for us is, from a low-code interface perspective, how do we deal with external users?

How was the initial setup?

The installation is fairly simple.

What other advice do I have?

On a scale of one to ten, I would give Mendix about an eight. I'd probably put Appian about the same and Camunda I would say is maybe a six. 

I would recommend Mendix, but obviously, for the right use case. That's the point.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Get our free report covering Pega, ServiceNow, Camunda, and other competitors of Appian. Updated: October 2021.
542,267 professionals have used our research since 2012.