Okta
Sorbet currently classifies Okta as the leader in its Identity & permissions bucket. The detailed selection note is not yet available.
Strengthening
Based on 1 material signal in the last 30 days: 1 positive, 0 negative.
Evidence summary, not a buy / sell rating
Latest approved decision: hold · 2026-08-29
The role and pillars explain what job this holding has inside the System-of-Record basket—not whether it suits an individual investor.
Okta owns the most consequential durable record in any enterprise: the identity graph — every user, group, application assignment, policy binding, and authentication event, all versioned and queryable through a stable API. That graph is the permission state the thesis identifies as the literal control plane for agents, because no agent can take a real action — invoke an API, write a record, escalate a ticket — without first being evaluated against an identity policy. Okta embodies P3 (ownership is a typed, permissioned field; the "who" is never implied), P4 (named, explicit verbs — grant, revoke, authenticate, authorize — are the entire product surface), and P5 (every authentication and policy-change event is logged with immutable, queryable history, which is precisely the audit trail an agent runtime needs to verify what it was permitted to do and when). As the bucket Leader, Okta carries the weight of the identity category's 40% Leader allocation: it has the broadest installed base of enterprise identity records, the most mature MCP-compatible API surface, and the network effects of being the directory both humans and, increasingly, non-human service accounts already authenticate against — making it the hardest substrate to displace as agentic workloads scale.
The bucket's primary paper position: the company Sorbet currently treats as the clearest expression of this workflow category.
The thesis properties this holding is selected to test. These labels are portfolio classifications, not standalone proof.
Typed ownership
Structural verbs
Queryable history
The thesis for Okta breaks on structural grounds, not price movement. The clearest falsifier is hyperscaler absorption: if Microsoft Entra ID or Google Cloud Identity begins bundling identity and permissions management into enterprise cloud contracts at zero incremental cost — and Okta's net revenue retention deteriorates in tandem with accelerating customer churn toward those bundles — that signals a structural erosion of Okta's ownership of P3 (typed ownership with permissions) and P4 (structural verbs: grant, revoke, escalate). A second falsifier is the emergence of a credible open-source or composable identity layer — something like a self-hostable Okta equivalent with a stable MCP-compatible API — that captures the long tail of developer-led deployments and visibly drags Okta's gross margins below the mid-70s, indicating pricing power has been structurally compromised rather than cyclically pressured. The third and most thesis-central falsifier is Okta's failure to ship and monetise an agent-specific SKU: if by mid-2027 there is no disclosed revenue line or disclosed ARR contribution from machine identity, non-human principals, or agent-scoped permission grants, that is evidence that Okta is not converting its P5 advantage — queryable permission history via stable API — into consumption economics, and the agent control-plane narrative does not hold for this name specifically. An observer should watch quarterly disclosures for net revenue retention trend, the gross margin trajectory on professional identity, and any product announcement (or conspicuous absence) around non-human principal management.
Daily closes are shown for context. Reference levels are deterministic outputs of Sorbet's published ATR method, not analyst targets or advice.
2025-07-28 → 2026-08-31
$173.04
Short-term levels use 14d ATR and the 200d average. The 3y projection compounds the current revenue-growth rate with no multiple expansion. Missing inputs stay blank.
Revenue growth + FCF yield, not the conventional FCF-margin formulation. Visible for judgment, but not wired into selection.
Price is more than 50% above the 200d average; the model treats new adds cautiously.
| Quarter | Revenue YoY | Gross margin | FCF margin | Operating margin |
|---|---|---|---|---|
| 2026-01-31 | 19.10% | 77.92% | 33.11% | 6.04% |
| 2025-10-31 | 6.74% | 77.09% | 28.44% | 3.10% |
| 2025-07-31 | 15.32% | 76.92% | 22.25% | 5.63% |
| 2025-04-30 | 2.74% | 77.47% | 34.59% | 5.67% |
| 2025-01-31 | -2.03% | 76.83% | 41.64% | 1.17% |
| 2024-10-31 | 9.67% | 76.39% | 23.16% | 0.00% |
Okta's trajectory hinges on whether it can convert its identity graph — already the authoritative record of who can do what across tens of thousands of enterprise tenants — into the permission-enforcement layer that every agent runtime will be required to consult before taking a real action. The company has signalled this direction through its expanding machine-identity and service-account capabilities, but the critical execution test is shipping a durable, queryable API surface that lets agent orchestrators read, grant, and revoke permissions as typed, auditable state transitions rather than as opaque policy blobs. What remains unproven is monetisation at the agent-identity tier: human seat counts are a mature metric, but non-human identity volume — service principals, agent personas, ephemeral tool credentials — demands a new pricing motion that Okta has not yet demonstrated at scale. If it lands that motion while holding gross-retention rates in its enterprise base, the identity bucket's thesis pillar — that permission state is the agent control plane — runs directly through Okta's core product, making it structurally difficult to displace even as hyperscalers push bundled identity offerings.
Okta’s EnterpriseClaw Role Links AI Identity Demand To Rich Valuation
Okta's role as the identity provider for Automation Anywhere's EnterpriseClaw platform directly supports the thesis that identity/permission systems are the agent control plane (P3 Ownership). Centralized authentication and policy enforcement for AI agents means Okta owns the 'who is responsible' typed field for agent workflows, not just conversational context.
Source: Yahoo
positive signal but thin coverage (only P3) — hold for confirmation.
Earnings in 1 day(s). Defer trim/add proposals through the print.