We performed a comparison between Apache Airflow and Appian based on real PeerSpot user reviews.
Find out in this report how the two Business Process Management (BPM) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It's stable."
"I like the UI rework, it's much easier."
"Designing processes and workflows is easier, and it assists in coordinating all of the different processes."
"Apache Airflow's best feature is its flexibility."
"One of its most valuable features is the graphical user interface, providing a visual representation of the pipeline status, successes, failures, and informative developer messages."
"We're running it on a virtual server, which we can easily upgrade if needed."
"Its user-friendly interface makes it straightforward to operate, offering a plethora of features for data preparation, buffering, and format conversion."
"I found the following features very useful: DAG - Workload management and orchestration of tasks using."
"The product has a very good mobile app."
"It has good integrations. We were looking for out-of-the-box integration with both on-prem and publicly accessible data sources. We needed integration with the cloud, OData, our REST API feed, and then on-prem passthrough to go to a SQL database or on-prem APIs through Azure local deployment, etc."
"We appreciate the drag and drop functionality and the easy to access plug and play features."
"Low code development: Code can be developed pretty quickly which leads to less turnaround time for automation of business processes."
"Since implementing we have had a faster time to solution, with fewer resources needed."
"The most valuable feature is business automation."
"The most valuable features of Appian are the VPN engine, it is fast, lightweight, and easy to set up business rules. Business teams can do it by themselves. That is a very good feature."
"Appian is easy to install and set up, and it does not come out with your audit. It has accessible process orchestration and process management. With Appian, the time to market is much faster."
"The solution could be improved by simplifying the integration process."
"Apache Airflow could be improved by integrating some versioning principles."
"Enhancements become necessary when scaling it up from a few thousand workflows to a more extensive scale of five thousand or ten thousand workflows."
"Programmatically, it's very good, and it doesn't have any competitors, but you cannot develop anything in Airflow UI. You need to develop everything within the program. In the market, other tools have come up recently as competitors to Airflow, and they also give graphical programming options, whereas Airflow doesn't provide that feature currently. All the DAGs you want to build need to be coded in Python."
"Adding more automated components in Apache Airflow for basic things like exporting the data would be helpful."
"The documentation must be improved."
"Apache Airflow should have better integration with cloud platforms."
"The automation capabilities could be improved; a visual workflow designer and a graphical tool to reduce coding would be very helpful. But for now, it's sufficient for our simple workflows."
"It would be useful if they could create an academy or forum in the future to help active users answer questions they have about the solution."
"We have clients that want to use Office 365, Microsoft Analytics, and Power Apps. Appian just isn't the same as using something specifically designed to cater to the Microsoft Suite."
"While Appian is generally flexible, it's rigid in some ways. It takes longer to do something that isn't available out of the box."
"What could be improved is more on the front end perspective, like the user interface and the mobile application aspect."
"I would like to see more features for enterprises. They would also benefit from adding documentation and training on their site."
"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."
"I wouldn't say their response time is long, but it could be quicker."
"Sometimes, clients expect us to implement ERP using Appian, which is very complicated. In such cases, I don't believe that Appian is a good tool for that."
Apache Airflow is ranked 2nd in Business Process Management (BPM) with 31 reviews while Appian is ranked 4th in Business Process Management (BPM) with 58 reviews. Apache Airflow is rated 8.0, while Appian is rated 8.4. The top reviewer of Apache Airflow writes "Enable seamless integration with various connectivity and integrated services, including BigQuery and Python operators ". On the other hand, the top reviewer of Appian writes "Low resource consumption, easy setup, and stable". Apache Airflow is most compared with Camunda, Informatica Cloud API and App Integration, IBM BPM, IBM Business Automation Workflow and OpenText 360 for SharePoint, whereas Appian is most compared with Microsoft Power Apps, Camunda, ServiceNow, OutSystems and Pega BPM. See our Apache Airflow vs. Appian report.
See our list of best Business Process Management (BPM) vendors.
We monitor all Business Process Management (BPM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.