This article details the minimum requirements your system must meet to run Appian.
You can also find additional system requirement information for specific capabilities:
This table lists the supported platforms for servers that host Appian. Only 64-bit operating systems running on x86-64 CPU architecture (sometimes referred to as x64) are supported. Linux hosts must have a minimum kernel version of 2.6.23.
| Linux (Reference Platforms) | Windows |
|---|---|
| Red Hat Enterprise Linux 6.0+ | Windows Server 2022 |
| CentOS 6.0+ | Windows Server 2019 |
| Ubuntu 18.04+ | Windows Server 2016 |
| Amazon Linux 2 | Windows 10 |
Only server versions of Windows are supported for production environments. Desktop version of Windows are only supported for local development environments.
While Windows environments are fully supported, Appian recommends running on Linux if possible as we typically observe better performance and stability in Linux environments. Additionally, running more than one instance of the Appian engines and the Internal Messaging Service (Kafka and Zookeeper) is not a supported configuration in Windows environments. This means that high-availability and load balancing the Appian engines are not possible in Windows environments.
Due to the way file names and file paths are calculated for documents stored in Appian, all servers hosting the same Appian installation must use the same type of operating system. Do not mix Windows and Linux.
Customers who wish to run VMware must use one of the platforms listed above as the guest operating system.
Caution: Per Confluent, VMware's vMotion and disk snapshotting capability has been known to cause a full cluster outage when used with Kafka. For any VMware servers that host Kafka, you must disable vMotion and disk snapshotting. See the Confluent documentation for the most up to date information on running Kafka in production.
The Appian installation includes OpenJDK 8. The bundled JDK should only be used with Appian, not with other programs that run on the same server.
Note: While Oracle JDK 8 is supported, Oracle ended public updates for Commercial use of Java SE 8 at the end of January 2019. Oracle Customers can obtain updates for Java SE 8 through the My Oracle Support portal. For more information review the Oracle Java SE Support Roadmap.
If you're using Oracle JDK 8, it must be on update 291 or later.
Caution: Only the JDK bundled with Appian or the one that Oracle specifically mentions in their system requirements can be used with Appian. Other third-party JDKs are not supported.
Transport Layer Security (TLS) is required for all external sources connecting to an Appian Cloud environment, such as user requests and external systems interacting with Appian web APIs. See TLS Policies for Inbound Web Access for more information about the TLS policies Appian Cloud supports for inbound web access.
For self-managed installations, you are responsible for setting up your own TLS configuration.
Appian supports the following policies when connecting from Appian to an external system using TLS, such as a database or an integration:
| Deploy Type and Version | Default TLS |
|---|---|
| Appian Cloud/Appian on Kubernetes 23.1 and above | 1.3 |
| Appian Cloud/Appian on Kubernetes 22.4 and below | 1.2 |
| Appian Self-Managed Windows, Linux | Set by java version being used. If you leverage the bundled java version, the same version numbers above apply. |
If you must connect to systems using TLS 1.0 or 1.1, follow the steps in the Post-Install Configuration page.
The table below describes the physical system requirements for Appian.
Development sites (sites where applications are built) and production sites (sites where the applications run) have different load profiles, scaling characteristics, and performance demands and so are broken out separately.
| Usage Pattern | RAM (GB) | Storage (GB) | CPU Cores |
|---|---|---|---|
| Infrequent Use, Few Applications | 15 | 30 | 2 |
| Frequent Use or Many Applications | 30 | 100 | 4 |
| Usage Pattern | Concurrent Users | RAM (GB) | Storage (GB) | CPU Cores |
|---|---|---|---|---|
| Single Application | < 100 | 30 | 100 | 4 |
| Departmental adoption | 100 - 1,000 | 60 | 500 | 8 |
| Enterprise adoption | > 1,000 | 240 | 1,000 | 32 |
Production instances of Appian should run on dedicated hardware or virtual machines in order to prevent resource contention, port conflicts, and interference from other applications.
Note: The sizing guidelines in the table above are a rough approximation for hardware requirements. They should be treated only as a starting point. Actual sizing also depends on the following:
Based on these factors, your actual requirements may vary.
Sizing is best run with sample data while your application is under development, and with real data after your application is complete.
For customers who wish to run Appian from cloud infrastructure as a service, Appian will run on any that support the operating systems and minimum hardware requirements as listed in this article.
The following major providers of cloud infrastructure as a service are known to be compatible with Appian:
For more details on the Kubernetes compatibility requirements for the Appian operator, see Prerequisite Install Steps.
The following relational database management systems (RDBMS) are supported as the Appian data source and as business data sources. The RDBMS can be hosted on Amazon RDS as long as it is one of the types and versions listed below and the network latency falls within the recommended guidelines.
| RDBMS | End-of-Support Date |
|---|---|
| MySQL 8.0 with InnoDB engine | 01-Apr-2026 |
| MariaDB Server 10.6 | 23-Aug-2026 |
| MariaDB Server 10.5 | 16-Jul-2025 |
| Oracle 19c | 30-Apr-2027 |
| Oracle 12c R2 | 31-Dec-2024 |
| Oracle 12c R1 | 31-Dec-2024 |
| Microsoft SQL Server 2022 | 11-Jan-2033 |
| Microsoft SQL Server 2019 | 08-Jan-2030 |
| Microsoft SQL Server 2017 | 12-Oct-2027 |
| Microsoft SQL Server 2016 | 14-Jul-2026 |
| PostgreSQL 15 | 11-Nov-2027 |
| PostgreSQL 14 | 12-Nov-2026 |
| PostgreSQL 13 | 13-Nov-2025 |
| PostgreSQL 12 | 14-Nov-2024 |
| Aurora MySQL 3 | 30-Apr-2027 |
| Aurora MySQL 2 | 31-Oct-2024 |
| Aurora PostgreSQL 14 (starting at 14.3.0) | 28-Feb-2027 |
| Aurora PostgreSQL 13 (starting at 13.3.0) | 28-Feb-2026 |
| Aurora PostgreSQL 4, Aurora PostgreSQL 12 (starting at 12.8.0) | 28-Feb-2025 |
| IBM DB2 UDB v11.5 for Linux, UNIX, and Windows | 30-Sep-2025 |
| IBM DB2 UDB v11.1 for Linux, UNIX, and Windows | 31-Dec-2024 |
| RDBMS | Driver |
|---|---|
| MySQL | Connector/J 5.1.x |
| MariaDB | MariaDB Connector/J 2.7 Series |
| Oracle | Oracle 21.5 JDBC Driver Certified with JDK8 |
| Microsoft SQL Server | Microsoft JDBC SQL Server Driver 12.x |
| PostgreSQL | PostgreSQL JDBC 42.7.x Driver |
| Aurora MySQL | AWS JDBC Driver for MySQL 1.1.x |
| Aurora PostgreSQL | PostgreSQL JDBC 42.7.x Driver |
| IBM DB2 UDB | IBM DB2 JDBC Driver version 4.31.10 |
In addition to these supported databases, other JDBC-compliant databases can be queried using a connected system plug-in.
Appian recommends a round-trip time for TCP communications with the database of less than 10 milliseconds with an upper bound of 25 milliseconds for acceptable performance. Network latency outside of these bounds will result in degraded system performance.
Note: If you are connecting to an Amazon Aurora data source through the Admin Console, for Type, select the type of database that best matches your Aurora version. For example, if you are using Aurora PostgreSQL, simply choose PostgreSQL. However, if you are using Aurora MySQL, then you should select the specific option for Aurora MySQL. The non-Aurora MySQL data source option is not advised as it utilizes a different JDBC driver than AWS recommends.
For Appian Sites, mobile users should use the Appian Mobile app. For Appian Portals, mobile users should use a mobile browser. See Mobile devices for more information.
Web browsers must allow cookies. If a user's browser is not configured to allow cookies, then Appian displays an alert stating that cookies must be enabled in order to log in. Appian uses browser cookies to maintain user sessions, to enable protections against threats such as cross-site request forgeries (CSRF), and, if configured, remember certain user choices between sessions. The cookies contain anonymized tokens and unique identifiers. No personally identifiable information (PII) is ever stored by Appian in a browser cookie.
Web browsers for Appian Cloud users should be configured to allow TLS version 1.2.
Appian supports the most recent stable version of the following desktop browsers:
| Browser | Comments |
|---|---|
| Microsoft Edge | Supported on Windows and MacOS operating systems. |
| Mozilla Firefox | Mozilla Firefox updates automatically. |
| Google Chrome | Google Chrome updates automatically. |
| Apple Safari | Safari is only supported on Mac operating systems. |
Note: Appian does not support browsers that are no longer supported by their vendor. Use the latest supported browser version and always apply all available security updates.
The table below lists browser compatibility by feature. Certain features in Appian, such as the Process Modeler, have their own browser configuration requirements. See Web Browser Configuration for more information.
| Feature | Edge | Mozilla Firefox | Google Chrome | Apple Safari |
|---|---|---|---|---|
| Tempo | Yes | Yes | Yes | Yes |
| Sites | Yes | Yes | Yes | Yes |
| Portals | Yes | Yes | Yes | Yes |
| Embedded Interfaces | Yes | Yes | Yes | Yes |
| Appian Designer | Yes | Yes | Yes | Yes |
| Admin Console | Yes | Yes | Yes | Yes |
| Process Modeler | Yes | Yes | Yes | Yes |
| Web Content Component | Yes | Yes | Yes | No |
| RPA Console | Yes | Yes | Yes | Yes |
| Process Mining | Yes | Yes | Yes | No |
| Portal Pages (deprecated) | Yes (in IE mode)1 | Yes (runtime only) | No | No |
1Appian Forms Designer and legacy Portal Pages (deprecated) are the only product areas supported in IE Mode. All other product areas must be used with a modern browser and are not guaranteed to work when using IE Mode.
All supported versions of the Appian Mobile app are listed in Mobile Support.
The latest version of the Appian Mobile app is always backward-compatible with previous supported Appian versions, so we encourage you to upgrade to take advantage of new features and enhancements.
It is important that you use an OS version supported by Google and Apple to ensure that you have the latest security updates to protect your enterprise data. For more information, refer to the security bulletins published and maintained by Google and Apple.
The Appian Mobile iOS app is generally supported on the latest version of iOS and one prior major version. As of today, we support iOS 17 and iOS 16.
The Appian Mobile Android app is generally supported on the latest version of Android OS and three prior major versions. As of today, we support Android 14, Android 13, Android 12, and Android 11.
Note: We do our best to maintain support for older Android OS versions. So you should still be able to use the Appian Mobile app on older OS versions. However, we do not commit to addressing issues specific to an unsupported version.
Portals can't be accessed from the Appian Mobile app. Instead, use a mobile browser on the latest versions of iOS or Android to access portals. You can also configure a portal as a progressive web app (PWA), which allows you to configure a customized experience when users install the portal on their device.
Network File System (NFS) protocol is supported.
Server Message Block (SMB) protocol is unsupported.
System Requirements
