System Requirements

On This Page

Overview

This page details the minimum requirements your system must meet to run Appian.

You can also find additional system requirement information for specific capabilities:

Java

The Appian installation includes OpenJDK 17. The bundled JDK should only be used with Appian, not with other programs that run on the same server.

Caution: Only the JDK bundled with Appian can be used with Appian. Other third-party JDKs are not supported.

Transport Layer Security

Inbound to Appian Cloud

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.

Inbound to self-managed Appian installation

For self-managed installations, you are responsible for setting up your own TLS configuration.

Outbound from Appian

Appian supports TLS 1.3 when connecting from Appian to an external system, such as a database or an integration.

If you must connect to systems using TLS 1.2 or lower, follow the steps in the Post-Install Configuration page.

Hardware requirements

Tip: For self-managed environments, see Self-Managed Resource Requests and Limits.

This section provides guidelines for physical system requirements for Appian Cloud. Use the information in this section to begin estimating the resources you want to purchase from Appian for your Appian Cloud environment.

The values in the sizing tables are a rough approximation for hardware requirements. They should be treated only as a starting point for determining your actual system needs.

General sizing considerations

Actual sizing also depends on the following:

Number of active and archived processes.
Amount of uploaded files and data.
Engine checkpoint frequency.
High availability setup.
Amount of data synced in record types.
Specific features like relationship-based sync filters or event consumers for Kafka integration.

Use the Sizing Script with sample data during development and real data before production deployment to get more accurate requirements.

Development vs. production sizing

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 in the tables in this section.

Development sites

Usage Pattern	RAM (GB)	Storage (GB)	CPU Cores
Infrequent Use, Few Applications	15	30	2
Frequent Use or Many Applications	30	100	4

Production sites

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

High-volume data sync requirements

To sync 20 million or more rows in a record type, your environment must meet the following hardware and licensing requirements:

Capability Tier: You must have an Advanced tier (up to 20 million rows) or Premium tier (20+ million rows).
Minimum Site Memory: 128 GB.
Multi-Node Sites: For high-availability (HA) or multi-node configurations, ensure each application server node meets the 128 GB minimum.
Performance testing: Query performance across all tiers depends on your record type data volume, query complexity, and available resources. While row limits vary by tier—including no limit for the Premium tier—you must test your performance to ensure your site meets your requirements.

Cloud infrastructure as a service

See Prerequisite Install Steps.

Databases

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 any cloud service providers, such as AWS or Azure, 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.4 with InnoDB engine	01-Apr-2032
MariaDB Server 10.11	16-Feb-2028
MariaDB Server 10.6	31-Jul-2026
Oracle 23ai	31-Dec-2031
Oracle 19c	31-Dec-2029
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 18	14-Nov-2030
PostgreSQL 17	08-Nov-2029
PostgreSQL 16	09-Nov-2028
PostgreSQL 15	11-Nov-2027
PostgreSQL 14	12-Nov-2026
Aurora MySQL 3	30-Apr-2027
Aurora PostgreSQL 17 (starting at 17.4.0)	28-Feb-2030
Aurora PostgreSQL 16 (starting at 16.1.0)	28-Feb-2029
Aurora PostgreSQL 15 (starting at 15.2.0)	29-Feb-2028
Aurora PostgreSQL 14 (starting at 14.3.0)	28-Feb-2027
IBM DB2 UDB v12.1 for Linux, UNIX, and Windows	TBD
IBM DB2 UDB v11.5 for Linux, UNIX, and Windows	30-Sep-2025
IBM DB2 UDB v11.1 for Linux, UNIX, and Windows	30-Apr-2025

Database drivers

RDBMS	Driver
MySQL	Connector/J 8.4
MariaDB	MariaDB Connector/J 3.5 Series
Oracle	Oracle 23ai JDBC Driver Certified with JDK17
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.

File systems

Network File System (NFS) protocol is supported.

Server Message Block (SMB) protocol is unsupported.

Web browsers

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.

Supported browsers

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.

Appian feature support by browser

The table below lists browser compatibility by feature. Certain features in Appian, such as the Process Modeler, have their own browser configuration requirements.

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)¹	Yes (runtime only)	No	No

¹Legacy portal pages (deprecated) is the only product area 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.

Mobile devices

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.

Hardware recommendations

We recommend that users access Appian Mobile using mobile devices with a minimum 4 gigabytes (GB) of RAM. Depending on your Appian Mobile use case, you may want to use mobile devices with higher RAM, such as 8 GB, to support the needs of your applications.

For example, we recommend using mobile devices with more RAM if using Appian Mobile for a use case that includes any of the following:

Offline experiences.
Many file upload components on an interface.
Many images on an interface.

Mobile operating system support policy

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.

iOS

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 26 and iOS 18.

Android

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 16, Android 15, Android 14, and Android 13.

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.

Accessing portals on mobile devices

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.

Appian for Windows

Appian for Windows is a desktop application that allows users to complete offline-enabled tasks and actions on Windows devices. See Appian for Windows for more information.

The following lists the Appian for Windows system requirements:

Requirement	Supported
Operating system	Windows 11
Processor	x86 (ARM isn't supported)
RAM	8 GB minimum
Free disk space	20 GB minimum. Actual usage varies based on the number and size of offline interfaces cached on the device.

The Appian for Windows app requires Appian 26.6 or newer. The app version on the device must be the same version or newer than the Appian environment it connects to.

Feedback

Was this page helpful?