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
Supabase
Score 8.9 out of 10
N/A
Supabase is an Open Source Firebase Alternative from the company of the same name in Singapore. Every Supabase project is a dedicated PostgreSQL database. Supabase also provides an open source Object store with unlimited scalability, for any file type. Supports open source authentication, with every Supabase project coming with a complete User Management system that works without any additional tools.
$25
per month per project
Pricing
Appian
Supabase
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.
Unlimited
Pro
$25
per month per project
Pay-as-you-go
$25
per month per project (plus usage costs)
Offerings
Pricing Offerings
Appian
Supabase
Free Trial
Yes
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Appian
Supabase
Features
Appian
Supabase
Low-Code Development
Comparison of Low-Code Development features of Product A and Product B
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.
Supabase can be used for strong custom backends for games and full-stack web applications. Self-hosting is not as great of an option just yet, and Supabase is still being developed actively so there are still legitimate problems that can be encountered, but this project seems to be going in a positive direction and has been useful for us.
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.
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
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.
It still takes some ability to be able to use all the features, but you may not need to use all the features. Even though a lot of Supabase is straightforward, you will still want experienced backend developers working with this tech. I wouldn't recommend having frontend specialists deal with this much.
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 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.
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]?
The extent of the options offered by Supabase far exceeded other similar products we've tried in the past. Also, their documentation has been excellent for us. Self-hosting is not what it's cracked up to be, but that's usually the case with these kinds of tools, anyway. I don't know anyone else I've talked to about Supabase who self-hosts, either. For something super micro small, Pocketbase is genuinely self-hostable, but it's been best for prototypes and proofs-of-concept, perhaps not with something expecting a lot of users. That's where Supabase's scalability and flexibility become more valuable.
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.