Notifications
Clear all
Topic starter
04/06/2026 2:56 pm
TL;DR: Per-seat pricing breaks down when bots, service accounts, and AI agents do the work, because non-human identities already outnumber humans by 25x to 50x in the average enterprise, according to ConductorOne and NHIMG research. The commercial model is now an identity-governance problem, not just a billing problem.
NHIMG editorial — based on content published by ConductorOne: Why We Stopped Charging Per Seat
Questions worth separating out
Q: How should security teams price identity platforms when non-human identities drive most activity?
A: They should stop treating named users as the primary pricing unit and instead model consumption by access event, policy action, and tool invocation.
Q: Why do non-human identities change how identity governance should be measured?
A: Because governance load is created by runtime actions, not only by human logins.
Q: What do teams get wrong about per-seat licensing in agentic environments?
A: They assume cost should follow people even when the value is produced by machines.
Practitioner guidance
- Map identity spend to runtime activity Track access requests processed, entitlements changed, tool calls, and policy enforcements separately from named-user counts so you can see where non-human workloads dominate.
- Separate human licences from machine consumption Build reporting that isolates service accounts, bots, and AI agents so procurement and governance teams can see which identity populations drive actual platform usage.
- Review usage dashboards for hidden automation Use consumption reporting to find shelfware, repetitive approvals, and unmanaged agent activity that would be invisible in a seat-based model.
What's in the full article
ConductorOne's full blog covers the operational detail this post intentionally leaves for the source:
- How the vendor maps pricing to access requests processed, entitlements changed, MCP tool calls, and accounts provisioned.
- What prepaid annual credits, pay-as-you-go, and rollover mechanics mean for procurement and identity operations.
- How real-time usage dashboards and threshold alerts work for teams that want budget controls without seat-based licensing.
- Which AI Access Management usage signals the vendor says it already bills per tool call, useful for implementation-stage buyers.
👉 Read ConductorOne's blog on why per-seat pricing breaks for agentic identity workloads →
Agentic enterprise pricing: what it means for identity teams?
Explore further
04/06/2026 3:05 pm
Per-seat identity pricing is a legacy assumption that fails once non-human identities become the dominant workload. Seat models were designed for human login behaviour, not for service accounts, bots, and agents that generate continuous machine-led access activity. Once those actors outnumber humans, the commercial model stops reflecting governance reality. Practitioners should treat pricing design as a proxy indicator of whether a platform still thinks in human-only terms.
A few things that frame the scale:
- Non-human identities already outnumber humans anywhere from twenty-five to fifty times in the average enterprise, according to Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which shows how easily machine identity demand can be undercounted.
A question worth separating out:
Q: How can organisations decide whether to move from seat-based to usage-based identity pricing?
A: Look for evidence that non-human activity is driving access volume, entitlement churn, and policy checks. If those events are more representative of workload than named users, usage-based pricing will usually align better with how the platform is actually consumed.
👉 Read our full editorial: Usage-based pricing exposes the real identity workload in agentic enterprises
