Try our new research platform with insights from 80,000+ expert users

Appian vs Make comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 5, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Appian
Ranking in Process Automation
6th
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
62
Ranking in other categories
Business Process Management (BPM) (7th), Rapid Application Development Software (5th), Low-Code Development Platforms (4th), Process Mining (6th)
Make
Ranking in Process Automation
30th
Average Rating
7.0
Reviews Sentiment
6.6
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Process Automation category, the mindshare of Appian is 6.9%, down from 10.9% compared to the previous year. The mindshare of Make is 0.8%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Process Automation
 

Featured Reviews

Srimanta Pandit - PeerSpot reviewer
Flexible, improves operational efficiency, and reduces the time taken to complete processes
The solution’s turnaround time for development is better compared to other tools. The solution enables fast development. The traceability of the processor is good. There is much more governance and regulations on the processers. The tool reduces the time of the processes by 30% to 40%. The solution’s low-code aspect has greatly impacted the development and deployment speed. One of the major reasons we are using the product is that we can reuse the modules. The developers can reuse all the modules. It enables us to make subsequent developments in less time. The prebuilt modules can be deployed within two to three weeks. The tool is very flexible. Compared to other platforms, the Appian product team was agile in quickly customizing things for us.
Yaniv Ivgi - PeerSpot reviewer
An affordable cloud solution for automation and data manipulation
Make has a single IP. We cannot use a single IP because of the security. There are a lot of crashes when you work manually. Also, they need to provide more models. When you have an error, Make should inform them with guidance before you make the mistake. There is a lot of data you can confuse.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Appian is a stable product and works very well."
"What stands out are the speed of the product, the quick, easy development, and visual diagramming."
"It's a stable product."
"It is really simple to create a new app, and I like the data-centric aspect of the BPM tool."
"Appian has many valuable features, the first being the ease of development—rapid development. Second, the process of learning the product and tool is faster when compared to its peers in the market. It's closer to low-code, and while it's still not very easy, it's more low-code than other products in the industry. Appian has a good user interface, a seamless model user interface, which comes without additional coding. It can also integrate with multiple systems."
"Appian also has very flexible local integration."
"Write to Data Store Entity - Saving data in SQL databases is done easily using entities. Entities (CDTs in Appian terminology) define relationships and target schema tables via XSD files."
"Since implementing we have had a faster time to solution, with fewer resources needed."
"The most valuable features of Make are the additional options when compared to other similar solutions. For example, with Google my business, you can only do certain things with Zapier, whereas with Make, you can do a little bit more."
 

Cons

"Appian could include other applications that we could reuse for other customers, CRM for example."
"Lacks integration with other products."
"If that had more DevOps capabilities, it would be an excellent product."
"It is difficult to set up the on-premise version."
"A point of improvement would be the SAIL forms. The built-in tool used to generate forms does not have debugging support (to view local variables as they change on live preview, and step-by-step valuation) which is a big drawback for form development. Moreover, the script language used to build SAIL forms does not support inheritance or lambda expressions (functions as arguments of other functions), which makes the code base more verbose."
"My only request is that they decrease the license costs."
"One of the areas that Appian is working on is to improve its UI capabilities and give more flexibility to the UI."
"What could be improved is more on the front end perspective, like the user interface and the mobile application aspect."
"Make could improve the ease of use, it can be more complicated than other solutions. There are a lot of elements that are more technical than in other solutions."
 

Pricing and Cost Advice

"The cost depends on the number of users, although I recommend taking an unlimited license."
"Licensing of Appian is less expensive when compared to other BPMs in the market."
"It's an enterprise tool and can be used by enterprise only. So it's a very expensive tool."
"Product pricing compared to some of the earlier vendors, like IBM, CA, and Oracle, is quite well-priced. Although, we do feel that as we increase the number of users and the workload increases, we will have to spend more."
"You can't really test the software properly without actually buying the license first."
"Appian is very flexible in their pricing. In general, Appian's pricing is much, much lower when compared to competition like Pega or other products. Appian also has a flexible licensing model across geographies. Pega usually goes with a single licensing cost—which is a US-based cost—for all global customers, and it's costly. Whereas Appian has a different regional licensing cost model and it can be cheaper, depending on geography. So Appian's licensing is very flexible, and cheaper when compared to other competition."
"More flexibility in the licensing model is still needed because initially there were customers who are looking at only one or two use cases of business areas, but now the business areas are changing and there is a larger scope. One license model may not fit everyone. They need to be a little more flexible on the licensing model."
"The licensing will be on a monthly basis. We are estimating that cost to be around $2000 to maybe $3,000 per month. We don't foresee any costs above that."
"The price of Make is approximately $20 per month for the platform."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
845,485 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
30%
Financial Services Firm
16%
Computer Software Company
10%
Government
5%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Which do you prefer - Appian or Camunda Platform?
Appian is fast when building simple to medium solutions. This solution offers simple drag-and-drop functionality with easy plug-and-play options. The initial setup was seamless and very easy to imp...
Is Appian a suitable solution for beginners who have no additional preparation?
Appian is actually pretty big on educating its users, including with courses that reward you with certifications. There is a whole section on their company’s website where you can check out the edu...
Is it easy to set up Appian or did you have to resort to professional help?
We had some issues when we were setting up Appian. It was quite surprising, since this is a low-code tool which, in its essence, means it is meant for business users and inexperienced beginners. So...
What needs improvement with Make?
Make has a single IP. We cannot use a single IP because of the security. There are a lot of crashes when you work manually. Also, they need to provide more models. When you have an error, Make shou...
What is your primary use case for Make?
We use Make to manipulate data, cut the numbers, take this line of code, and translate it to another line of code. SaaS products use XML, and other products use JSON. You need to translate to commu...
 

Comparisons

 

Also Known As

Appian BPM, Appian AnyWhere, Appian Enterprise BPMS
Integromat
 

Overview

 

Sample Customers

Hansard Global plc, Punch Taverns, Pirelli, Crawford & Company, EDP Renewables, Queensland Government Department of State Development, Infrastructure and Planning (, Bank of Tennessee
Buan Consulting, Armadia
Find out what your peers are saying about Appian vs. Make and other solutions. Updated: March 2025.
845,485 professionals have used our research since 2012.