Appian licensing is the set of commercial terms under which Appian Corporation sells the Appian Platform, a low-code platform for building process automation, case management and data applications, together with its AI, robotic process automation (RPA) and process-intelligence capabilities. The public documents show a subscription model priced “per user, per month, per app”, three platform tiers named Standard, Advanced and Premium, a monthly allotment of AI Actions, bot limits for RPA, and Success Plans that decide support and Cloud options.[1] The agreement behind a purchase is not published: the data processing terms identify it as the Cloud Subscription Agreement and/or the Master On Premise Agreement between the parties.[3] The contracting company named in the website terms is Appian Corporation, a Delaware corporation with its principal place of business in Tysons, Virginia.[11]
This article is the entry point to the Appian coverage in the wiki. Deeper articles cover the platform tiers and user licensing, AI Actions, Appian Cloud, Success Plans and self-managed deployments, RPA, Process HQ, portals and Data Fabric limits, and the free trial and Community Edition terms. A separate case article covers the trade secret litigation between Appian and Pegasystems.
Editions
Appian’s pricing page compares three tiers of the Appian Platform. All three include low-code process and application development, integrations, the Appian Cloud database, mobile apps and AI Copilot for Developers. They differ in the scale of the data layer, the number of RPA bots and portals, and the availability of Process HQ, Case Management Studio, offline experiences, Autoscale, advanced plug-ins and most AI features.[1]
| Capability | Standard | Advanced | Premium |
|---|---|---|---|
| Data Fabric scale | Single data source, 4M rows per record type | Multiple data sources, 20M rows per record type | Multiple data sources, no row limit per record type |
| RPA bots | 5 | 25 | Unlimited |
| Portals | One portal per app | Unlimited | Unlimited |
| Process HQ and Case Management Studio | Not listed | Included | Included |
| AI Agents, Composer, DocCenter | Not listed | Included | Included |
| AI Action limit per month | 200K | 500K | 1M |
The figures in the table come from the pricing page, which carries no date, so no effective date can be stated for them.[1] Footnotes qualify them: a feature may be unavailable or limited in self-managed deployments, Autoscale for Process requires additional licensing, plug-ins are not supported elements of the software, and the Snowflake and Apache Kafka integrations are limited to Advanced and Premium.[1] The detail is in Appian Platform tiers and user licensing.
Outside the three paid tiers Appian offers two evaluation routes. The Appian Cloud Trial is governed by trial terms that allow evaluation only,[7] and the free Community Edition grants up to 15 Users under a separate licence agreement.[8] Both are covered in Appian Trial and Community Edition terms.
Metrics
Appian names its units in the pricing footnotes and documentation rather than in a definitions booklet. The metrics recorded in the catalog are:
- User (per user, per month, per app): the pricing basis of every tier. Footnote 3 says the per-application figures for bots and portals are the entitlement per application for user licences and, for platform user licences, the total across all applications.[1] The Platform user license is the second licence form the footnote names.
- AI Action: the unit of measurement for AI consumption, allotted monthly by tier.[2]
- Bot (RPA), Portal and Rows per record type: capacity limits that rise with the tier.[1]
- Environment (Appian Cloud): the environments named in the legal agreement.[4]
- CPU count (self-managed licence file): the system configuration that a self-managed licence file is requested against.[6]
Appian’s documentation distinguishes two user types, System Administrator and Basic User, and says Basic User accounts require additional roles.[10] Those are technical access classes. The public documents do not state which accounts are billed under which licence.
Counting and floors
The public pages do not publish a user definition for paid subscriptions, a minimum quantity or a price. Practitioners therefore need three documents together: the order form, the customer agreement and the pricing page that was current at signature. What the public pages do establish is the shape of the entitlement. A user licence carries a tier and a count, the per-application capacity figures are tied to the licence form, and the AI Action allotment is stated per month by tier.[1]
Two points are worth checking against the order form. First, the pricing page says the figures for RPA and portals represent an entitlement per application for user licences, which means the same tier can yield different totals depending on how many applications are licensed.[1] Second, the Admin Console can deactivate users who have not signed in for a set number of days, but the documentation describes deactivation only as an access control: the user account remains in the system and cannot sign in.[10] Whether a deactivated account counts for billing is a contract question.
Deployment: Appian Cloud and self-managed
Appian Cloud is the main deployment. The environments that are provisioned are those recorded in the legal agreement, and the subscription administrator named there is also the initial licensing point of contact who can approve or deny licence requests.[4] Features such as high availability, log streaming and environment snapshots depend on the Success Plan.[9] Details are in Appian Cloud, Success Plans and self-managed licensing.
Self-managed Appian changed shape recently. Appian 25.3 is the last release that supports non-containerized deployment; from 25.4 Appian can only run self-managed in containers managed by Kubernetes, and an environment on 25.3 or earlier cannot upgrade to 25.4 or later without migrating to Appian on Kubernetes or Appian Cloud.[5] Licence files for the older installer-based releases are bound to a server, its operating system, its CPU count and its FQDN.[6]
Programs
The documents name several commercial wrappers. Success Plans (Foundation, Professional and Signature) bundle support and platform options.[9] The AI Action monthly allotment is a consumption programme with overage billing.[2] The Community Edition and the Cloud Trial are free evaluation routes with their own terms.[7][8] No enterprise-agreement or unlimited-deployment programme is described in the public documents.
Compliance and audit
The documents reviewed for this article contain no audit clause: that sits in the customer agreement, which is not public. What the public documents do give a licence manager is a set of operational data sources: the Admin Console user accounts, the MyAppian Adoption page that shows AI Action consumption, an AI usage log, and the licence files on self-managed servers.[2][6] Appian’s trial and Community Edition terms also prohibit use by competitors and masking of identity,[7][8] which is relevant background to the litigation described in Appian v. Pegasystems.
Out of scope
This article does not cover Appian solutions sold as packaged applications, such as the Award Management or Contract Lifecycle Management offerings that appear in the documentation, whose licensing is not described in the sources used here. It also does not cover hyperscaler marketplace pricing, partner resale terms, professional services, or the price of any tier. Prices, minimums, the definition of a billable user and the audit clause are not in the public documents and are not stated here.