JumpCloud extends per-seat IAM to agents

This pushes JumpCloud from selling identity per employee to selling identity per actor. In practice, an AI agent that can call tools, open apps, or touch data starts to look like a digital contractor that needs its own record, owner, login method, group memberships, and shutoff switch. That is valuable because agent counts can grow faster than headcount once companies automate support, IT, and internal operations workflows.1 2 3 4

• JumpCloud is packaging agents as distinct non human identities, not as add ons to employee accounts. Each agent gets OAuth based authentication, an owner, group based app access, activity history, and independent suspension or deletion, which makes the product billable and governable as a separate seat.2 3
• Google Cloud gives JumpCloud a concrete deployment wedge. Google now supports agent identities for agents acting with their own authority, and JumpCloud adds a control layer above that, covering discovery, registration, policy, and short lived token governance across MCP and A2A flows.1 4 5 6
• The bigger strategic point is category expansion, not just one feature launch. Microsoft Entra, CyberArk, and Google are all moving toward agent identity, which suggests buyers will increasingly expect AI agents to be managed like service accounts or employees, inside existing IAM budgets rather than a separate experimental tool budget.7 8 6

The next step is a pricing and workflow shift where enterprises count humans, devices, apps, and agents in one access graph. If agent adoption keeps moving from copilots to autonomous task runners, JumpCloud can grow with the number of automated workers inside a customer, even when employee headcount stays flat.1 2 3 6