Source
Hosting options & portability — found from sitemap — Appian
Checked for Appian on 13 Oct 2026
- Page
- https://docs.appian.com/suite/help/26.9/Requesting_and_Installing_a_license.html
- Checked
- 13 Oct 2026, 16:56 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:93bde54e5ff682076b4a2e8657984dce612ac0b04e471089be8b2e6c1ba58379
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Self managed kubernetes Report an error
“This page walks through how to install Appian on Kubernetes for self-managed customers. The instructions show how to install on a server-based cluster.”
-
Supported versions Report an error
“This release of Appian on Kubernetes has been explicitly tested against Kubernetes v1.33-v1.37.”
-
Supported platforms cloud Report an error
“Appian is validated on and supports major platforms including:”
-
High availability supported Report an error
“Refer to our high availability configuration docs for more information if you would like to setup a multi-replica (HA) deployment of Appian using the Appian operator.”
-
Hpa supported Report an error
“Horizontal pod autoscaling You may want to set up Horizontal Pod Autoscaling on the Apache Web Server (httpd).”
-
Relational database required Report an error
“Appian on Kubernetes requires its own relational database to store system metadata, known as the Appian data source. However, Appian on Kubernetes does not install that relational database, so you can select a database consistent with your organization's policies and practices.”
-
Database location flexible Report an error
“This relational database can either run within the Kubernetes cluster or outside of it.”
-
Rpa database mariadb Report an error
“To use Appian RPA, you must also create and configure multiple databases on the MariaDB server, ensuring the URL, username, and password are correctly set in the configuration files.”
-
License temporary validity Report an error
“Temporary license: Valid for 6 days.”
-
License longterm site bound Report an error
“Long-term license: Valid for an extended period of time, and only valid for the site URL for which they were requested.”
-
License generation lead time Report an error
“Note: It can take up to 4-5 business days to generate the long-term license files.”
-
License key change november 2026 Report an error
“Caution: Starting in November 2026, newly issued Appian licenses will be signed with a new private key and require version v0.205.0 of the Appian operator or newer.”
-
License files Report an error
“you received a zip with two files: k3.lic and k4.lic, and a third file called appian.lic”
-
Ssd recommended Report an error
“Appian recommends keeping the data directories for these two components (services/data/kafka-logs and services/data/zookeeper) on solid state volumes rather than mounting them onto network drives.”
-
Persistence via statefulsets Report an error
“As most Appian components are StatefulSets that rely on persistent storage, the .spec.[STATEFUL_COMPONENT].volumeClaimTemplateSpec fields have suggested values that define this storage.”
-
Ingress controller expected Report an error
“We expect to use an ingress controller, so we are setting .spec.ingress.enabled to true in the spec.”
-
Migration tool available Report an error
“Migrating from a server-based installation to Appian on Kubernetes? Run the migration tool's import command instead of creating the Appian custom resource directly.”
-
Startup time Report an error
“It will take about 20-30 minutes for the Appian site to fully start.”
-
Bootstrap admin user Report an error
“Newly created sites are bootstrapped with a system administrator user. This user cannot access the Admin Console.”
-
Process hq configuration Report an error
“To enable Process HQ for process analysis, you can add the conf.iam.pm.unifiedMiningPmRedirectUri custom property to your Appian CR configuration file.”
-
Operator delivery Report an error
“Appian is installed on Kubernetes using a custom resource definition (CRD) and an operator.”
3 facts read from this page are not shown because they could not be confirmed on the page as captured.
Scores citing this record
- The Data Protection Officer Hosting options & portability
- The Head of IT Hosting options & portability
- The Integration Engineer Execution, error handling & monitoring
- The Integration Engineer Hosting options & portability
- The Operations Analyst Hosting options & portability
- The Process Owner Process design, forms & approvals
- The Process Owner Hosting options & portability
- The Skeptic Hosting options & portability