A1 ratingsAppianAppian Platform

Appian Platform

Appian · platform · Any industry
C
CGrade
50Score
±1495% range
≈#401Rank of 1134
0%From fleets
FR-CAT-01111Catalog no.

The six pillars

Each bar is the score; the bracket is its 95% range.

Can you see what it costs?

Nothing a buyer can read · prices on request only
25±38
Desk research 0 · counts for 25% · A cost API you can call scores highest; an admin console or cloud billing export next; a card statement or emailed invoice is all some products leave you. Published prices add to it.

Can you see how much it's used?

MyAppian Adoption page and AI usage audit log (no public API)
86±27
Desk research 100 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

By project
64±27
Desk research 70 · counts for 15% · Exact (one key or project per agent) beats by-project, by-workspace or by-user.

Can an agent on it report out?

HTTP step in a workflow · Web APIs and integrations; not verified
57±27
Desk research 60 · counts for 15% · A remote MCP connector scores highest, then a local MCP server, an SDK, an API or a workflow step; copy-and-paste lowest. Any open standard counts, not just FleetRegistry.

Can you control spend and access?

Spend cap: None · Per-agent keys: Scoped · Audit log: By API · SSO: SSO only
56±38
Desk research 61 · counts for 20% · Hard spend caps (30%), scoped per-agent keys (25%), an audit log you can read by API (20%), revoking by API (15%), SSO with SCIM (10%).

Does it work on small plans?

Small plans don't get the data
14±27
Desk research 0 · counts for 10% · Whether the plan a person or small business buys gets the cost and usage data at all.

Where the evidence comes from

Independent fleets0%Desk research62%Neutral starting point38%

Once three independent fleets report on a pillar, desk research counts for at most a third of it. FleetRegistry's own fleets never count.

Controls on record

Spend capNone
Per-agent keysScoped
Audit logBy API
RevokeNot known
SSOSSO only
PricesOn request

Contact-sales pricing with monthly AI Action allotments. When they run out, the AI service keeps running and overage is billed (no hard stop). API keys are tied to service accounts with group permissions and managed in the Admin Console, SIEM log streaming needs a Professional/Signature Success Plan, and SAML SSO is documented but SCIM is not.

History

11-11 C 5011-12 C 5011-13 C 5011-14 C 5011-15 C 5011-16 C 5011-17 C 5011-18 C 50
First rated 2026-10-02 at 46 (C). Now 50. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-02.

Every fact, with its rung and source

Each fact stands on its own source and its own rung of the evidence ladder (Rule N2.1). Verified Observed Declared Inferred. The weakest fact in a pillar sets its weight.

FactValueRungCheckedSources
How a buyer sees cost
Cost
None found Declared
medium confidence
2026-11-15
2 earlier
[1][2][3] Correct
Prices published
Cost
No Inferred 2026-11-15
3 earlier
[1][2][3][4] Correct
Usage API
Usage
MyAppian Adoption page and AI usage audit log (no public API) Declared
medium confidence
2026-11-15
2 earlier
[1][2][3] Correct
Cost per agent
Per agent
By project Declared
medium confidence
2026-11-15
2 earlier
[1][2][3] Correct
How an agent reports out
Reports out
HTTP step in a workflow Declared
medium confidence
2026-11-15
2 earlier
[1][2][3] Correct
Per-agent keys
Controls
Scoped Inferred 2026-11-15
3 earlier
[1][2][3][4] Correct
Audit log
Controls
By API Inferred 2026-11-15
3 earlier
[1][2][3][4] Correct
Spend cap
Controls
None Inferred 2026-11-15
1 earlier
[1][2][3][4] Correct
SSO
Controls
SSO only Inferred 2026-11-15
3 earlier
[1][2][3][4] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-11-15
2 earlier
[1][2][3] Correct

Prices · Tiered Standard/Advanced/Premium licensing with monthly AI Actions allotments; list prices not published

Notes · Enterprise contract pricing per user, per month, per app. AI Action usage is on the MyAppian Adoption page, and overage is billed at applicable rates beyond the allotment without cutting off service; there is no public billing API.

Scored with the rubric for Platforms and APIs (Rule N7.1). Each pillar blends a neutral 50, desk facts weighted by rung, and independent fleets. A1 is 85+ with fleet proof, A 70, B 55, C 40, D 25, E below. Part N of the Rules

Run agents on Appian Platform?

Give each one a permanent number, a named person who answers for it, and a record of what it can touch and what it costs. Free.