Appian is a low-code development and business process management platform. It features drag-and-drop design for app building, automated work processes, unified data management, and cloud-based deployment.
$0
Drupal
Score 7.0 out of 10
N/A
Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
OutSystems
Score 6.4 out of 10
N/A
The OutSystems Platform is a Platform-as-a-Service solution for rapid delivery of responsive web and mobile applications. It includes functionalities required to develop, deploy, manage and change web and mobile applications. It is targeted at the delivery of enterprise applications that require integration with backend systems, complex business rules and logic, usable interfaces and flexibility to change. It can be deployed in the cloud, on-premises or in hybrid environments.
$4,000
per month
Pricing
Appian
Drupal
OutSystems
Editions & Modules
Appian Community Edition
$0
Application - Input-Only
$2
per month per user
Application - Infrequent
$9
per month per user
Application - Standard
$75
per month per user
Platform
Custom Quote Priced per user with unlimited apps.
minimum 100 users, no maximum
Unlimited
Custom Quote Priced per development with unlimited apps.
unlimited
Platform
Custom Quote Priced per user with unlimited apps.
Minimum 100, no maximum
Unlimited
Custom Quote Priced per development with unlimited apps.
Appian presented us that the software will allow EDPR to develop better solutions than OutSystems because our developments need to be very closed to the business needs, and we are in a really changing work environment, then we need to be able to adapt our development as fast as …
Appian stands out when it comes to low code development and easy to use and develop platform. It helps developers and business to meet the users requirements within no time with equal efficiency.
The biggest benefit is that it helps avert vendor lock-in (you can take the code and leave if you need to/want to)! Also, OutSystems supports multi-tenancy and directly incorporates containers and DevOps concepts/tools. OutSystems is on top of analyst charts for two …
Verified User
C-Level Executive
Chose OutSystems
Most complete solution. Beyond the super fast ability to create high-quality web and native mobile apps, the built-in analytics have proven to almost eliminate the need for added overhead of analytics tags.
I've been following OutSystems for 3 years and the pace of innovation …
Appian works great for automating manual processes and integrating multiple systems through its toolset. It gives great flexibility for establishing rules for approvals, routings, escalations, and the like. Because of the low code toolset, it's very easy to deploy and make changes as needed as processes evolve and as the organization learns to utilize the system better. Minimal maintenance is required to support the applications build on the platform. Some of the automated testing integration with tools like Jenkins is limited so that may be an issue for some.
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
Well suited for internal exposure of business processes (invoicing, API layer to other systems, customer maintenance etc), whether a UI is required or not. Not so well suited for full fledged web design. An OutSystems application must serve one particular business need, if gets too much functionalities and responsibilities it tends to get chaotic and complex.
Allows at a glance workflow documentation which assists in the need we have for information readiation.
Drag and drop interface for workflow development greatly speeds our apps time to market.
Using the advanced features of Appian, we are able to create working sites in a fraction of the time it would take to do so using "traditional" development.
Search issues when type ahead and database search are used in the same field.
Buttons implementation where user is require[d] to click on the button description - if clicks on the button outside that text - button will not work.
Problems with using certain off-the-shelf performance tools like WebLoad or Neoload. That is because of different dynamic variables being used internally in Appian - which these tools are unable to correlate. We are still investigating using other tools like Jmeter to overcome dynamic correlation problem for performance testing.
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
Price – The licensing model of OutSystems is very expensive and not suitable for small scale developments. This is offset by the time to develop and stability for larger scale developments
Flexibility on PaaS version – The PaaS hosted version of OutSystems limits your flexibility to access the front end and backend database systems which can significantly restrict your options on high data volume developments or where anything requiring slightly out of the ordinary access is required
Same price for PaaS and self-hosted system. Licensing model dictates that you pay the same price even when you host the system on your own hardware which effectively means you pay more to manage the infrastructure yourself
We recently renewed our license with Appian. We are convinced that its flexibility, relative ease of use, the support they provide, there mobile advancements and their general willingness and desire to see us succeed all contributed to our reason to renew our agreement with Appian
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
We are very happy with OutSystems and our developers deliver good work. OutSystems lets us build new software on a regulare (2 weekly) basis, which is highly flexible and adjustable. Even without very much experience, our developers manage to build usefull software, which is working a lot better than our previous (legacy) software.
Appian is a low code environment, because of this, a very good visual interface is required. Appian is providing a feature-rich dashboard [that] we can use for building the dashboards and other interfaces. Appian also provides patches and releases to enhance these features. A developer can start off development just by going through a basic course from the Appian learning community.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
OutSystems has a feature in which we can develop a functionality in a application and can use that functionality in another application without developing it again. That is main plus point for the development team so they can work with different functionalities rather focusing on the same thing again and again. if we want to make any change on the user side then we can make it live with just the deployment using the service center.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
Appian is one of the leading low code business automation platforms that support RPA, decision rules, case management, workflow automation, and machine learning all in a single bundle. But it is also harder to implement and replace the traditional business process.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
The tech support is very reachable. Usually by [email] from but also by phone if needed. We had some difficulties at the start with understanding "what our machine was doing" under high performance load. After some good sessions understanding our needs they delivered good solutions for our problems we had in the beginning.
As analyst I participated in a developer boot camp. At times it was hard to keep up but most of the time it made sense. Trainer took the time to explain and slowed pace down to answer questions etc.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
The online training material is well designed and explanations are step by step, helping trainees to understand and follow each exercise and new concept.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
In a large company, patiently and consistently work the behind the scenes politics with business and IT partners across the firm. This is transformational - you will need a solid set of key business partners to lock arms together to move forward.
Appian has enormously transformed and keeps on updating the product every quarter to meet the latest needs of the world with new innovations & technologies being integrated within the platform. What gives more pleasure than a product that keeps on continuous[ly] improv[ing]?
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
I tried to use WordPress with some success. Also looked at Joomla. But when I saw OutSystems I knew I had been wasting my time there. It takes you longer to get going with OutSystems - but even I as a novice realized immediately that Outsystems is simply in another league. Outsystems is powerful. (Can you compare WordPress and Joomla to Outsystems - I don't think so).
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
I believe it has negatively impacted our release dates. There may have been a misunderstanding as to the learning curve, even though it is "low code."
The look and feel of the applications created using Appian have uniformity and it's easier to have "reuse" between applications.
There is less developer control when it comes to features. I think this mainly has to do with the amount of plugins available. I would think there should be many more available plugins. But again, our use case is probably different than most others.
The ease of use of the OutSystems development process has been the biggest ROI for us. We have developed our Framework product and maintained/enhanced it with only 4 workers.
OutSystems has enhanced their product very significantly over the last 4 years. They have gone from a simple to use tool to a very simple to use sophisticated tool that covers the standard mainframe-based computing apps and the apps used on handheld mobile devices all using the same basic set of development tools.
