Okta Stock

This presentation contains forward-looking statements. We reserve the right to change the information in this presentation. More information can be found in our securities filings.

Good morning, everybody. Welcome to Investor Summit at Oktane '26. So we've got Todd McKinnon, our Co-Founder and CEO; we've got Ric Smith, our President of Products and Technology; and Jon Addison, our CRO. So we're going to do a tight 60 minutes. But before we take questions, I'm going to turn it over to Todd for some quick opening commentary.

[Audio Gap]

Lots of new vendors. There's going to be different dynamics in the industry, but Okta is very committed to really winning in this era and building a long-term value-creating company. So thanks for all the support, and thanks for coming to Oktane, and we're excited to answer some questions to try to illustrate where we're up to it in a little bit more detail.

David, you're going to make the decision on who gets to ask? Awesome. Be nice to David.

Keith Bachman from Bank of Montreal, and I appreciate the time. Todd, I just wanted to ask you a question about the market dynamics. And what I mean by that is your keynote today highlighted Blueprint, which is a way to try to bring vendors together. And then underneath that, you talk about messages such as governance and orchestration are key themes. Yet there's a lot of vendors trying to get into that space, not only security vendors. IBM has watsonx.governance, watsonx Orchestrate. ServiceNow has Control Tower, which the value proposition sounds remarkably like some of the things that you're trying to do.

And so I just wondered if you could talk a little bit about Okta's positioning here and right to win when there's a lot of folks trying to go after the same real estate and not even necessarily security vendors, but a lot of folks trying to have that governance and orchestration layer, which is necessary for adoption. So just talk a little bit about the competitive dynamics and your right to win.

I think there's a lot of work to do, like the example -- so fundamental to our strategy and our belief is that agentic is not one discrete thing. It's really a transformation of every layer in the stack. So it's new agents, it's new platforms to build agents, but it's also agents in every part of the stack. You've heard us say this several times now. But the implications of that are that when you talk about control tower or management and visibility, there's actually a lot of work to do there. Like, for example, a control tower and visibility in terms of the effectiveness and the ROI, the business ROI of agents you could put a control tower on that. It's very actually different from a visibility and control, security governance control tower.

So I guess it's a long-winded way of saying that there's a lot of opportunity for all of us to be successful, which is why strategically, the point of the Blueprint is to -- we're trying to make the pie bigger for everyone by catalyzing the market. I mean there is unprecedented interest. I mean, it really in a very concrete way, it's a conversation everyone wants to have, and everyone knows it's going to be a problem. But I think the market in terms of actually allocating budget to build the secure agentic enterprise is being hamstrung by the confusion. Customers are -- they don't want to make the wrong decision. And we've been successful with Okta for AI agents. It's off to a great start. It's grown incredibly fast.

But that's because we've positioned it as this really no regrets foundation. Like basically, like we go to customers and we say, -- however this unfolds over the next 5 or 10 years, you're going to have to have a secure way to connect things together. Token, that's not going away. In fact, it's been around for a while. You've had to connect software together, and it's only going to get supercharged in terms of that requirement. So you need to manage tokens, you need to have this registry, and that's worked. But to really take the market to the potential we think it can be, and let's be clear, we think the identity foundations of the Blueprint, it could be a bigger market than all of IAM.

And IAM is one of the biggest markets in cyber already. I believe IAM will be the biggest market in cyber in 5 years. That's pretty clear to me that's going to happen. And agentic could be bigger than it all. Agentic, the security and governance and visibility for agentic being the control layer for that could be bigger than all of identity is today.

Now how do we make that happen? We have to bring this clarity, and we have to make sure customers can get help and the industry can help customers understand how to rationalize this all and put things in buckets. And of course, there's going to be debates and skirmishes at the margin. It's not like I'm sure that other companies have an opinion on they should do this identity part, and that's fine. But by and large, we're going to clarify what the gateway should do, what's the difference between an AI gateway and an MCP gateway and how those work together and how the -- what risk means across those kind of things can be clarified and catalyze the market. And that's the point of the Blueprint.

And the Blueprint members, it's only been 6 months or so, we've been working on this in serious dedicated budget effort. And it's going well. I mean the proof is in the pudding. The alliance members have to keep working together, certify their products as the technology evolves, but I'm very optimistic about it. And the strategic objective here is, let's be clear, is bring clarity and make the pie bigger for everyone. And I think we have a good shot of doing that. And like I said, I'm super motivated and fired up to meet this need and move the industry forward because, yes, it's -- the downside scenario is fragmented approaches, not good governance, not good risk management and not getting where we need to be as an industry.

Brian Essex from JPMorgan. We caught up really briefly and you asked me one of the things that I thought was impressive in my reply was the third-party IdP access.

Yes, third-party IdP.

Yes. So, sacrilege in the past. Would love to hear the backdrop for that? And how many deals -- when you've been selling Okta agentic identity platform. How many of those conversations maybe had a bottleneck because a competitor of yours was in the IAM business with that customer? And how much do you think this would accelerate market adoption of your agentic platform?

Yes, I can start, and Ric, you can chime in here. You've been super close to this. By the way, Okta has a secret weapon here and my friend, Ric Smith. He's been here 1 year, and it's making a huge difference accelerating our R&D. So the access management for employees, the market share is pretty stable. Microsoft has about 40%. Okta has about 30%. And then there's some smaller players and a lot of kind of like niche players, I would say, below that. The whole market is growing, so that's good.

But Okta for AI agents is a GA product. And so we're the only one with the GA product, which is a great position to be in. We're innovating quickly. So that's a lot of customers out there that have a Microsoft IdP. And they're coming to us, particularly the big ones, big global deployments, multinational -- I'm thinking of a multinational auto manufacturing company, thinking of 2 or 3 other very large accounts that see this as a big problem in their Entra IdP shops. And we have seen -- so -- and they want to use Okta for AI agents, which is exciting.

Now I would say the vast majority still of our conversations about Okta for AI agents are people with the Okta IdP for sure. But particularly in the largest of the large enterprise, which is an overall area of strength for Okta in general in the last year or 2, the fact that we're supporting IdPs outside of Okta is very compelling.

So that's exciting. The other exciting thing is that we're seeing that I can think of 2 or 3 specific cases, one is with a software company, 35-year-old software company. A couple of other ones come to mind where they're actually -- you can't replace Entra because it's the login for Office 365. But the Okta for AI agents product is actually pulling in the whole platform. They know AI is a big deal. They've been not happy with Microsoft because it's not really great at connecting with non-Microsoft technologies. And this has been the thing to get them over the edge of going in the whole platform, governance, privilege, Okta for AI agents and Workforce IdP. And that one actually has -- those 2, I'm thinking of actually have a big SIEM customer identity expansion as well. So it's catalyzing the platform, which is the -- that's like big time upside scenario for Okta. We win the agentic identity market. It pulls through the rest of the platform in a way that changes the market share dynamics overall. It's super exciting.

No. I mean I think you stated it very accurately. Like most of our conversations that we have actually start on the AI front. And then that leads to a larger platform sale. Most of that is the result of the customer having a clear understanding that it's time to actually evolve their identity platform in order to be able to handle what's happening in the agentic world.

In terms of us being able to connect to another IdP, it is early days in terms of that kind of opportunity. We're seeing more and more demand for that. And it's not just unique to what's happening with Okta for AI. We're seeing it across all the products, and we have a motion to actually start opening up governance, PAM as well as the Auth0 platform so that we can attach to an independent IdP other than Okta so that we can use that as a land-and-expand opportunity for the platform.

One other thing I'd say on that is this is really where specialization in go-to-market is helping. We made a move to specialize how we go to market in the field with our customers with deep domain expertise in kind of 3 product areas. So we have a takeoff team for AI, deep subject matter experts on Okta for AI agents and our AI solutions. They're often opening the door and those doors lead in different directions. And like Ric said, it really is creating the opportunity for broad platform modernization across all identity use cases and 4 identity types.

And that leads us to the CIO and the CISO, where we have the Okta specialist team, but also leads us to external-facing applications and Auth0. And so we see many examples now where the AI conversation is opening the door to a much broader opportunity for Okta, and it's going across both the Okta and Auth0 platforms in all of their forms. So the go-to-market structure that we've had in place now for 18 months is really helping elevate that.

And join me in congratulating my friend here for 5 years at Okta. Congratulations. When I first met Jon, I was interviewing for the GM of EMEA role. And I just want to thank you for making my promotion decisions look smart.

#1 rule in life make the boss look smart.

It never fails.

Eric Heath from KeyBanc. Now I think one of the things you said, Todd, and I totally appreciate, there's a lot of noise. It's hard for the CSOs to cut through the noise and understand all the different technologies and who's differentiated and everybody's got their own story and they're all telling the same story essentially.

Long-winded way, I guess, saying like you do have some platform vendors that have gotten into identity, and they tell a similar story and that they're trying to secure identity for agents as well. So how are you seeing them show up, if at all, the larger platform vendors? And secondarily, is the bundling effect, what they can do with flex pricing and platformization having any impact or do you foresee it having any impact to selling Okta for AI agents?

I think it's going to play out. I think that the market share established over the next 3 years for the agent, call it, the system of record for agent identities, it's going to play out over the next 3 years. And the market share is -- there's going to be massive growth and the market share is going to be set probably in 3 years.

So there is going to be competition. I mean people are waking up to this after many, many years that identity is going to be the biggest part of cyber. And that the agentic control plane might be a bigger market than all of that together. Because really, you're talking about the control plane or at least some foundational pieces of the Blueprint for all of technology because everything is becoming agentic. When we talk about the agentic -- the Blueprint for the secure agentic enterprise, we're talking about the Blueprint for all of security. That's why it takes a village. It's not going to be Okta out there all alone, securing everything. It's just not going to happen. There's too much technology, and there's too many pieces that have to come together to make it happen.

But I do think the market share is going to be set over the next 3 years and for agentic identity, and we are very focused on winning that. It's all systems go to win that. And I think we have a lead. It's very early, but our advantages are -- it echoes with what we've been talking about for many years. We're not trying to sell a model. We're not trying to sell a broad development platform. So yes, some people want to go all in and they'll be constrained and hamstrung by that. But the vast majority of people, especially in this fast evolving somewhat confusing environment of agentic and rebuilding their company and their infrastructure, they like the choice. They like the flexibility.

So I like our position. And there's not another company that has that focus on identity. And if we do our job right in laying the landscape in a way that people are clear on how the Blueprint parts have to work together and how in those different pillars of the Blueprint, how identity plays such a relevant role, I like our chances. But it's not -- I mean, it's not a defined -- I mean it's not -- the market share has not decided yet. It's too early. So we have to go out and win it, and we're making sure we build the company and the culture and the environment to win it. That's why we're -- everything at Okta is ramping up. The intensity, the expectations, the standards, we are not going to lose this. I'm totally dedicated to winning this, and I like our chances.

Gray Powell with U.S. Bank. So I just had a question on the buying center, particularly related to Okta for AI agents. And just for better or worse, security or identity historically is just viewed as like a tax on the business versus something that enables business. So do you see the buying center changing with AI? Like is it more closely aligned with something like a marketing budget or something that could generate revenue versus traditional security budget dollars?

Yes. We faced this challenge for some time just relating to identity. And broadly speaking now, identity management is a topic where we need to address the needs of people who are building technology to compete and sell goods and services. Also, clearly, it's of high relevance to CIOs and CISOs and the SOC. And so for some time, we've been like working really hard to make sure that we've got the right team in place to specifically address those needs. And we don't really see that playing out much more differently when we think about agentic security. So the agentic security topic, and it's kind of clear understanding as we're seeing it in our customer base that to solve it, they see agents as a primary identity type. That's a natural evolutionary step in the relationship capital that we've built over 17 years in our customer base.

Now it means that we've got to be like tight with our customers across a really broad set of stakeholders. It means in really big companies, we've got to be aligned internationally so that we understand their strategies. We're ahead of the curve when we're thinking about securing all of their external-facing apps, all their resources to humans, nonhumans and agents in the future. So there's a lot of work to be done, especially in enterprise and strategic customers. But I feel really good about our positioning, the relationships that we built over time. And we're seeing budgets typically come out of our traditional stakeholder groups. So CIO, CISO budget, we're seeing a lot of new program spend. And increasingly, we're seeing budget come out of R&D and engineering, especially for things like building external-facing agents.

Yes. I think you'll see an evolution over the next year from all the -- almost -- I'd say 80% of the conversations I have are with IT or security, Gray. It's like traditional buyers. And -- but I see a big trend changing. You're going to get more like the traditional customer identity business, where it's like marketing and Chief Digital Officer. You're seeing that start to happen more and more. I was meeting with one of the major airlines recently and at the table where there -- basically, it's their kind of Chief Digital Officer, which is like business-driven, they want growth. It's a loyalty program growth, more ROI and loyalty program. And then you saw -- then the Chief Security Officer was more traditional risk management locked down internal systems.

And you can tell that, that's -- the conversations are going to evolve that way. There's going to be more of that what typically would have been like the SIEM buyer, and I think we've done a good job leveraging our relationship with IT and security and the Workforce Identity Foundation and getting Okta for AI agents off the ground and rolling there. And I think you'll see a similar thing on the customer identity side.

But I think it makes sense, right? I think people are starting with their internal processes. Maybe the risk is lower there. They don't want to mess up. Maybe they don't want to mess up the customer-facing experience. If you want to mess up your loyalty program as an airline, but that's the trend I see.

Rich Poland from Wells Fargo. So Todd, I think today on stage, you're talking a lot about the agentic commerce and the productization there with Auth0. I just kind of wanted to put a finer point on that given recent events with Muse and Instinct. It feels like that could be meaningful.

Super interesting, yes. Yes. I think like -- I'm going to -- I feel like I'm broken record here, but I think there is a big opportunity for more standardization there. All these products like Instinct and Muse and OpenClaw and the other ones, it's pretty rudimentary. It's like type in your password and I'll use your password. And I think we need a better solution. It's like if you're building a customer-facing app for many years, a bot was bad. Like bots where you don't want to shut them down and you didn't want bots taking the tickets and scalping them and bots were blocked, and we have a whole capability to block bots. Now bots are good.

Unless you're worried about like Amazon is, you're worried about your Amazon credentials being out there and losing control and someone hacks into one of these Muse or one of these things and like buys $5 million worth of Amazon stuff, Amazon is going to be responsible. So I think we need better standards. I think the industry has to evolve. And I think as the Blueprint expands, it will start to cover more and more customer-facing. If we do our jobs right, it could start to cover more and more customer-facing scenarios. But yes, it's still early days, especially on the customer-facing side.

And I would add the -- like most of our customers, particularly in the SIEM business, they're starting to see a drift in traffic. So like traditional digital properties are in decline in terms of the traffic they see as a result of more and more consumers going through agents. And the standards in place like UCP are very early. So there's not broad adoption, not a lot of interoperability. But every one of our customers sees that pull, and that's why we're partnered with Google to go out there and try to like open up that lane for them.

And to the earlier question regarding like, are we seeing more traction, revenue opportunities or helping guide our customers and revenue opportunities. Beyond just agentic, they're actually coming to us and trying to find paths that they can look at the login process as part of the conversion process. So I mean, if you end up in the Auth0 platform keynote, you'll be seeing a presentation around Conversion Suite, which offers that opportunity and affordance to our customers.

Joshua Tilton, Wolfe Research. Todd, I want to go back to something you said when you started, you used the words, we're lucky for where we're positioned in the industry. Can you maybe, in the context of that, compare the demand and the adoption curve that you're seeing for your Okta for AI agents offering to what you saw during COVID and the demand and adoption curve when I could argue you were just as lucky for your position in the market at that time?

Yes. COVID was definitely a catalyst. It really -- I would say it was like the big final push of the multiyear secular shift to being the perimeter is not the network. You really have to have a strong identity foundation. I don't think -- it was -- like I said, I don't think it was -- in terms of shift in the industry, it was like kind of the culmination of that shift. And then the next last -- after COVID and 0 interest rates, last 3 or 4 years, we've all been trying to figure out what's the next big catalyst. And we found it, which is very exciting.

This one is -- it's hard to compare. It was such a weird time in COVID and everyone was trying to adjust and so forth. But this one feels way bigger to me. This one feels -- it's not the final push of a multiyear thing. This feels like something new. Not new in the sense that it's totally disconnected from what we've done before, but the energy and the potential feels much bigger.

Fatima Boolani from Citi. I have one for Todd and I'm going to sneak one in for Ric as well, if possible. Todd, just on the Blueprint Alliance, the spirit of the effort is very clear. The ethos is clear. But can you maybe expound on what the next phase of the Blueprint Alliance is going to be outside of building more consortium and more vendor inclusion? And ultimately, what I'm trying to ask is that should we expect the next phase of that alliance to include economic incentives whereby Jon can go to customers and have joint go-to-market incentive agreements with CrowdStrike or Zscaler, where ultimately, you are getting paid for building a coalition around this effort. And I have a follow-up for Ric.

No, it's a really smart question, kind of follow the money. I think the next -- so this is very important to us. And the next phase, I think, is it has to catch on with customers, meaning customers have to accept it and make it clear to everyone involved on the vendor side that they want this. And then if it doesn't get that kind of traction, it's not going to be super successful. So customer adoption and customer endorsement is super important. That's the only thing that I've been working at enterprise companies for a long time. And the one thing that really is powerful is customers requesting things. So that's really important.

And then I think the next more -- we have a really good version of the white paper that I'm very proud of. The next step is really the -- working with the alliance partners to check the reference architecture that the products are working together. And that will just -- it will just be a good virtuous cycle with customers endorsing it and they're seeing results that the products are working together and tangible evidence of the clarity versus the confusion. I think those are 2 very important steps.

In terms of like the economic incentives, I think those are interesting, but probably premature now until we get those 2 steps. The one thing I will say is that we're talking Blueprint, which is very high-level industry landscape type stuff. And then we talk about this agent SSO. And that's like a macro and now we're going to micro. And agent SSO is we've been working on this for 4 years. It's perfect for agents. They all need it. It's got a ton of traction, a ton of momentum.

And in terms of incentive, the reason why we're enabling Cross App Access support in every Okta product is because we have to catalyze the ecosystem. We have to give these ISVs a reason to support it. They all have 50 things to do. They're all working about on AI agents and doing this stuff, and they have to have an incentive. And the incentive is going to be customers ask for it. And if customers have one of the most popular AI agents in Claude like they do speak in this protocol and it's in every Okta product. We can't go to an ISV and say, hey, support Cross App Access is an open protocol. This first thing they ask is, okay, how many customers can use it? And the answer they used to be like, well, I'm not sure. But now the answer is very clear.

Every Okta customer -- and by the way, every paying customer because they support it, which is awesome. And every customer that uses Claude. So that number is big. So you should -- when we talk over the next 6 months or a year, the question used to ask me is, how many ISVs supporting Cross App Access? And that number better grow. And if you -- if many of that number is growing, you could get confidence in this micro standardization effort. And if you get confidence in this micro standardization effort, you should have more confidence in the macro effort, too.

You're spoiled for choice in terms of where you can invest the R&D envelope. Clearly, the velocity of the portfolio expansion has picked up. How should we think about where you're kind of putting your chips? And I'm coming from the standpoint of the earlier question on if we see a massive explosion on consumer AI interfaces and B2C use cases, there is a completely different technology investment strategy behind that. So how do you kind of think about allocation of your R&D capital behind those opportunities?

I mean we're pretty financially aligned in R&D. So when we groom the portfolio, we're looking at like what are the major drivers in terms of current revenue, what are the bigger bets down the line. And we have no fear of moving resources even if we have to cross the lines between the different platforms. So we're here to win, and that's the only way to win.

Yes. One thing I want to be clear on everyone. So we combined Auth0 and Okta R&D. So it all works for Ric now. So he can move pieces around, make sure the investment across the entire portfolio is aligned on the biggest impact things. I think it's been -- it's a great thing. It's really helped Okta for AI agents in the gateway and so forth.

Saket Kalia at Barclays. Jon, maybe for you, I'm going to change it up a little bit. I'd love to talk about some of the observations that you have from specializing the sales force, right? It seems like it's been a great success based on some of the metrics. But maybe outside of the agentic opportunity, which we're all clearly excited about, do you still feel like there's low-hanging fruit for better execution just in the core workforce and Auth0 businesses. Does that make sense?

Indeed. I mean I think the momentum, the durability of our core business is really strong. It's a really big part of the success we've had this half. A large part of that is the improvements and the accelerated benefits of sales productivity. For 18 months, we've had a very stable operating model in go-to-market. It's benefited from specialization, like I said, in several forms. We specialized around our public sector opportunity. We've specialized in commercial and down segment around like specific customer need around new logo acquisition and installed base and account management. And like I said, in platform specialization above that for enterprise and strategic.

It's super clear that when we think about specialization and obviously, many companies at our phase and our stage with this broad range of product capability and demand that solve specific problems for customers and our stakeholders that we manage. There are various choices around how you specialize. And we take our North Star from what is it that the customer needs? What is it the customer needs to be successful in the thought leadership, relationship capital, technical expertise and partner ecosystems so that they can invest in the Okta and Auth0 platforms and think about them really as generational strategic bets over the long term. And that's how we think about specialization.

And so if you look at all of the incredible innovation that we've built in and around the Auth0 and Okta platforms over years, like they're very broad platforms. They have a lot of use cases covered. They require a lot of specificity, a lot of understanding about the competitive landscape, the buying processes of stakeholders when they think about those platforms, the different identity use cases change. So it does require learning. And our tenure in sales is very high. Like I said, AI productivity is very strong, and our attrition is low. And so we're getting the benefit from that. And so when we think about the future, we feel about shifts in those areas carefully and prudently. And we really think right now, we're on the right path in the structure and the team, the capacity we've got and how it's yielding in pipeline and sales productivity.

Shrenik Kothari from Baird. So Todd, on the keynote, you pretty much highlighted why you made the agentic SSO available to everyone. And clearly, as you just highlighted, it's a frictionless on-ramp for customers to adopt more. I just wanted to connect the dots here a little bit since you already have several dozen customers who are already using the Okta for AI agents. And you mentioned in the keynote that first step is the connection point. And then if you need more complex use cases, requirements for governance and runtime enforcement. So just curious in terms of the monetization journey for the customers on Okta for AI agents, how is that sort of progressing? Yes.

So I was meeting with a large well-known insurance company, and they're an Okta customer. They use Okta for customer identity and workforce identity. And the conversation was all around Cross App Access, and they wanted to -- they're very excited about Claude supporting it. They're very excited about a bunch of their applications supporting it, and so they want to understand that. So they were super excited about just being able to do that in their environment. So they can -- they have agent SSO, which means that they can start using the Okta directory of agents. They can start doing Cross App Access. And they're very excited about that. And it was like 2 meetings and 1 week POC when they realized that they needed full life cycle, they needed support for connections that weren't Cross App Access, and it's a full upgrade to Okta for AI agents.

So that was kind of like -- I was really excited about that because that's our strategy. It's like kind of see the opportunity with Cross App Access. Deliver value with that, but also deliver value with -- and monetize the value with Okta for AI agents, which is why when you put it all together, too, you kind of see why third-party IdP support is important. You can -- that even if it's a company that doesn't use like this large auto manufacturer I was talking about, they don't use Okta for their IdP, but we could run the same play there, Cross App Access, upgrade the Okta for AI agent.

So yes, it's -- yes, we're -- like I said, we're in a good position. Still early. We have a lot of work to do, but the strategy and the tactics are -- we're seeing early evidence that they're playing out quite nicely.

Steve Koenig with Macquarie. I'm wondering, Todd, question probably for you or anyone else that wants to comment. Given kind of the early state of agentic identity and agentic governance, and you're one of the few vendors with the GA product out there. How is this impacting customers' efforts to adopt agentic AI more broadly? And where are you seeing like if you were to think about the use cases that are driving customers to consider Okta for AI agents, what sorts of agentic use cases are priority for them? And where are they, in some cases, holding back on adopting agentic technology because of this early state of the control technology?

I think it's a really good question. I think the -- I don't think we've -- any of our customers for Okta for AI agents, I don't think we've introduced them into the concept of agents. I think these are companies that have been kind of on the path you look at RAMP or Yahoo! or Dell, internally, our own example, it's -- these companies are -- see the potential and are on the journey, either they're heavily invested in platforms that are offering agentic capabilities or they're building their own. And so the need kind of smacks in the face, and we're there to service that need.

I think when -- if you just think about it like as an adoption curve, these would be called early adopters, I think. But -- and we're trying to make the pie bigger by codifying and clarifying how things fit together with the Blueprint and trying to really hasten the big part of this bell curve of adoption because, I mean, it's coming, right? I mean every company that's going to be successful is going to -- it's almost like loses meaning because saying they're going to be agentic is like it's the same thing as saying they're going to like adopt the future of technology. So it's going to happen. It's just a matter of how long and the reality is it's probably going to be longer than we all think. But it's probably going to be bigger than we think. Yes. So it's super motivating.

Mike Cikos with Needham. Two questions. First, on the AI monetization. Can we talk about where we are in terms of price discovery? And what is the market willing to pay in terms of valuing an agent?

Yes. I think -- so this is a really important thing we think about a lot. Right now, our pricing for -- Okta for AI agents is per user, which sounds weird, like it's for agents, why would it be per user? And that's -- if you got a chance to check out the keynote today, we're a pretty pragmatic company. We want to meet customers where they are. And customers -- and this is like kind of like the previous answer where these companies are adopting AI agent solutions, but they're really helping a user and making a user more productive. And the flows all kind of start for a user, whether it's the Dell example where it's the AI system is like in the interaction of a customer service or support person is like figuring out based on the AI model, the next best action. A lot of the use cases are tied to a user.

So it kind of makes sense for someone like Dell or RAMP or Yahoo! or many other customers where they say, hey, I want to pay for this per user, and it's like basically an uplift of the per user price. And we're seeing like if the whole -- using like round numbers, obviously, but I can think of deals -- sizable deals that have been -- if the overall platform or Okta is like 4, the AI agent part is 1 or 1.5. So it's a significant part of uplift for the whole suite. And that's exciting.

But I think this is going to evolve. This pricing model is going to evolve. And it's going to be -- it's not going to be per user. There's going to be something else. It's going to be per agent that's problematic now because it's -- there's not a standard way on how you count agents. By the way, it's something we can add to the Blueprint, a systematic way to count them. It sounds simple, but it's going to really benefit customers because right now, the problem with counting is that if you have an agent like our internal agent called Dex, is that one agent? Or is that 7,000 agents because that's how many people use it. And of course, if you're paying by the agent, you want that to be one. If you're charging by the agent, you want that to be 7,000.

So the industry will figure it out. I think a big impetus will be the longer running agentic workflows get, the more autonomous workflows get, the less coupled they will be to a user session, and that will really force us all to figure this out. But I -- we'll figure it out, and I have no -- the value we're adding and the value of the Blueprint is adding, like I said, I'm not worried about monetizing this. I think this opportunity could be bigger than all of identity in the fullness of time, and we'll get there.

Maybe for a quick follow-up. I'd just love to ask Jon, like go-to-market on this point, like it feels like each touch point by default has to be more bespoke to help each customer on their journey. And I'd just be interested like what are the additional resources you're putting behind this to help customers onboard?

There's 2 or 3 things I'd say on that. We prepared for this year really waiting for the moment, and it gave us an opportunity to reconsider our sales methodology and go-to-market. So the structures that we've got in place to create a framework for how we go into the market with thought leadership around AI, like we completely rebooted our sales methodology at the beginning of this year, specifically for that purpose.

Secondary to that is we want go-to-market folks to come to Okta and it'd be the best experience for them not only in terms of making them identity experts, but also like fusing how they go to market with AI tools. And so we spent a lot of time and effort and investment giving them amazing tools. But when they're showing up with customers, they have the right information that's specific to the use case, it's specific to the industry. It's highly relevant to really the innovation that's coming very quickly out of R&D to really give them the tools to excel, differentiate themselves and meet customers where they are.

The third piece on this is, you're right, each customer use case is bespoke. It's highly specific to where they are in their maturity curve with agents. And an incredible part of that is preparing ourselves with thought leaders around those customers who work with them for years on their own technology strategy. And for that, we have to rely on our partner ecosystem. So we've spent a lot of time and effort with our partners, educating them on this massive opportunity, but really preparing them to bring their specific thought leadership about the company in question to bear as they engage with us with our expertise around AI security. And that's really playing out.

We had an incredible partner summit yesterday. Some of the performance from our consulting partners, the advisory firms that companies are working with in enterprise and strategic. It's paying massive dividend. And when we look at the performance of our big deal cohort, really big part of our growth story in H1. I look at all those deals. I mean, our top 20 deals in Q2, they were like sold side-by-side with partners co-selling with us. Our biggest deal in Q2 was partner sourced. So a massive part of that is being there toe-to-toe with our partners, providing advice, technical expertise that is relevant to their bespoke agentic use cases.

It's Gregg Moskowitz from Mizuho. So I have a bit of a follow-up on agent SSO. It's been GA for a month and the demo you showed this morning was pretty slick. What I'm wondering though is how much of an on-ramp for Okta for AI agents do you think that this can be? And from a go-to-market standpoint, are there any strategies or mechanisms that you might be able to put in place to get a healthy percentage of customers to sort of matriculate from agent SSO to Okta for AI agents going forward?

Yes. I mean you can almost think of it as a very clear analytical dashboard that we can use for pipeline. And so we know all the customers that are onboarding on to it. That can be fed to Jon and his team can engage. And I mean, honestly, you don't really have to wait for that. It becomes pretty obvious in terms of all the features and functions that you need to manage the agent life cycle once you're onboarded to it. But it does give them the first litmus test of understanding of like what is the experience as a result of not having to do all these like consent-based prompts through Claude console or what have you.

It was interesting internal the debate about should we make the Cross App Access capability, add it to every product at Okta and make it widespread. And it was an interesting debate. So the debate like against doing that was, oh, we don't want to give it away, we could charge for it, we can monetize it. The argument for doing it was like, obviously, pushing the Cross App Access standard, giving an answer these ISVs when they ask how many people could do this? The answer is all of them, that's compelling.

But the other point is like, listen, we're pouring all this energy and innovation into Okta for AI agents. And you can't build enough value around the Blueprint and all the problems there to solve that you can't get them an upsell. It's like really come on, guys, you got to work harder. And the result was like clear that we do have compelling value in Okta for AI agents way above the Cross App Access and the stuff that -- and the directory entries and the capabilities there. And I think we're going to be pretty happy with that decision.

Yes. I mean it's going to take a lot of effort and focus and momentum to get Cross App Access adopted broadly in the market and the ecosystem and a major part of how we're going to be tracking customer success moving forward. I mean we obviously have a set of customer health metrics that we measure in every kind of standard like CSM motion and how we think about agent SSO is going to form part of the consistent evaluation of the value that we're adding across all forms of how they're being successful with their stack.

Yun Kim, Loop Capital. Just following up on Mike's question around go-to-market on Okta for AI agents. How heavily are the partners involved in the initial go-to-market? Because obviously, we hear a lot of good things about the pipeline from the earnings calls. How are those generated of that size? And also just walking the floor for a few minutes before I came in here, did pick up signs that maybe there's a greater services component related to Okta for AI agents, maybe almost 2 to 3x versus your single sign-on. Does that change the way that you do your go-to-market and you got to like tie into services to make sure that you're engaging the prospects properly?

It's going to take a huge amount of collaboration in the industry to be sort of get our customers to be successful with AI security. That's really obvious. I mean just in the last, I'd say, year, 18 months, like we've really expanded the amount of effort that we've put into forging these technology partnerships that are going to surround our customers. And all of the customers are going to be meaningful to our growth, as Todd said earlier, they have deeply heterogeneous operating environments. They're looking to us as an independent and neutral identity provider with 17 years of integrations behind them to come in and help make this solution work very quickly for them.

It's going to require a very broad effort in long-term deployment, not just around Okta for AI agents, but as Ric talked about, what we're seeing is the AI conversation is triggering a broadening effect as companies think about modernizing their identity infrastructures for all types of like human, nonhuman and agent identity types. And so we have to -- in our motion, we plan out like that breadth of capability, the pull for a number of like products that are in our new product category that put in place what we call an identity security fabric. And a lot of these products, they're requiring consolidation, replacement of often many point solutions and significant amount of services effort.

And so in order to do that, we face the reality that like for us to be successful, we need to surround our customers with a number of service delivery capabilities in our partner ecosystem that are specialized, that are experienced, they're enabled and we've invested in. And we've invested significantly in those capabilities. We're getting great feedback from our partner community in and around that. And so their ability to go and deploy our products, broaden out the identity security fabrics that are a key part of the Blueprint Alliance and our customers' long-term strategies for identity, that's a critical part of our engagement, our selection and our investment in the partner ecosystem.

Robbie Owens, Piper. Good to see you as well. I appreciate the complexity of what you guys are trying to do around agentic, contemplating access, governance and the like. How do you think about the data side of the equation? I know it's going to take a village, but there is a natural convergence when I think about what an agent has access to and then regulating what type of data it's going to have access to. How do you contemplate this longer term?

Yes. I think data security and data governance is a big opportunity. I think it's pretty nascent and immature right now. I think a lot of enterprises have -- don't have a good handle around it. And it is a pretty identity-centric problem. So our strategy is like, again, repeating myself a little bit, but we're trying to build the one-stop shop for identity. We're not trying to branch off into a bunch of other security categories. We're keeping our independence and neutrality, and we're trying to build the best -- take our $600 million of R&D and invest it in the best identity stack, the identity platform and the pitch to customers is like consolidate on us.

And then the second opportunity is this agentic being the system of record for the future of agentic, which is really the future of technology and playing our part in the Blueprint. So those are the 2 big things we're doing. I think the -- we think about strategy on the first one, it's like, okay, what is identity and what is not? And there's a lot of things that are either -- some that are clearly identity. And then there's things that are adjacent, and we're thinking through like what's the right way to build, buy and partner there. And I think this identity area is super interesting. The current solutions there aren't great. And yes, it's something we think about a lot, but I don't think there's a good answer yet.

Nasr Islam here for Brad Zelnick at Deutsche Bank. So Todd, touching on the 4 pillars outlined in the Blueprint. If you look at other security markets, we've often seen value migrate towards runtime enforcement and response, while discovery and posture management capabilities have become increasingly commoditized over time. As the agentic identity market develops, do you think the same dynamic could emerge here? And where do you believe the most durable source of differentiation will ultimately reside?

That's a good question. I think it's probably -- I think that would be a fair bet that it would -- the value will accrue at the same layers, but we're keeping our mind open. And we're trying not to be too smart for our own good, like we want to listen to customers and provide the value that they're asking for. You have to have a strategic view and you have to bring your own opinions, but we're pretty good at listening to what the market wants us to build and building it quickly.

And the last thing that comes to mind there is that -- the opportunity is big. And so spending time trying to think through like what layer of the architecture is going to be monetized the most might not be super productive. If we just focus on what customers need, how value is going to be delivered, working with the people in the ecosystem to build the right thing and then delivering great capabilities. I think that's the winning solution.

Rudy Kessinger, D.A. Davidson. A lot of your cybersecurity peers have seen a lot of success with the flex pricing model. Given the uncertainty around agents and how many we might have in 6 months or a year as a customer, I guess, is that a model that you guys have considered utilizing as well?

We have customers on flex agreements and enterprise bundles. Clearly, as the portfolio breadth has expanded, and we're dealing with very complex customers, lots of different subsidiaries, moving at different speeds with very broad use cases. There's clear commercial value to them of having agreements that give them economies of scale and flexibility. So that's a path that we're down. I think that's the path we're going to continue with, and it's exciting that customers are leaning in so broadly with us and are interested in those types of opportunities.

Every company that gets to $3 billion in revenue and has aspirations to accelerate growth like we do, they're going to do some version of bundling or platform. And ours is the identity is the bundle is the platform. So we're definitely doing bundling and we're going to do more of it in flex agreements. We're going to do all that stuff. You're all very studied in all this, but the bundle economics are more compelling and they work better, the more hit products you have. So one of the most exciting things about Okta for AI agent is it looks like it's going to be a hit product, which is going to reinforce the value of the broad platform, make the bundle more compelling, stickier, move the rest of the product. So it has a big potential to move the business on all those dimensions.

It's Taz Koujalgi from ROTH Capital. Just a clarification on the comment that you made earlier about pricing and uplift. Todd, you said if the Okta platform spend is 4, Okta agent spend is about 1.5, that would imply about 50% uplift. Did I hear you correctly? Because I think when you launched OIG, you had said that the uplift that you're getting from OIG is about 30%. It looks like the Okta agent uplift could be even more than OIG?

I think that's right. Yes. I mean we're -- it's not a set of thousands of deals yet. So it's a small sample size. I'm just thinking of the few specific sizable deals in my mind, and that's how the numbers are fleshing out. It's maybe similar or a little bit more to the OIG attach, which is pretty exciting.

This is Lawrence Vensko here for John DiFucci from Guggenheim Securities. We've talked a lot about the enterprise today and the opportunity there, but you've also invested a lot into the public sector. And you recently brought agent governance into the FedRAMP High environments. Considering your commentary around the pipeline in Okta for AI agents, is the public sector pipeline today mostly Okta agencies adding agents to their environments? Or is it new agency opportunities?

It's still, I'd say, pretty early days in terms of agent deployments in public sector. The public sector performance, generally speaking, has been very strong through the course of this year. And that's down to, like you said, like a lot of our investments in our regulated environments and most recently, FedRAMP High and IL5. And we're continuing to see great representation in our top deals from the public sector domestically and abroad. So yes, we're excited about it. We're excited that we've got the right regulatory controls in place, the right environments for public sector customers. And I think that as they start to explore their own agentic use cases, we're going to be in a great position because of that.

Yes, that's -- I think if you do take a broad survey, I think public sector is maybe trailing, particularly on adoption of agentic. But some of the biggest opportunities in the pipeline we're working on even at this conference are with massive government agencies that want to do Okta for AI agents. They're doing pilots and prototypes. And I just had a meeting yesterday with one of the leaders at these -- with this organization, and it's all about making sure all of the pieces of the platform have the right compliance so they can deploy it in their environment. So I think it's coming, especially, I think it's some of the larger organizations that see a lot of potential and can move effectively quickly in here to get some of the benefits. It's pretty exciting.

Time for one more.

That's shocking.

As always, I have one more question. I'll wrap it up there. Really appreciate you guys coming out to Las Vegas. We know your time is valuable. If you scan the QR code here, they will download like a 4-page summary of all the innovation announcements that we have this week at Oktane. So thanks again for coming out.

Yes. Thanks for your support. And I read a lot of your research on -- not only on Okta, but on everything else. And you guys do good work. And I learn a lot from your research. I really appreciate it.

Please welcome Okta's Chief Executive Officer and Co-Founder, Todd McKinnon.

Congratulations. You are part of the biggest Oktane ever. Thank you for being here. It was 1 year ago that we introduced this simple but powerful concept. And that was to secure AI, we needed a powerful new identity type, an identity type where every AI agent got their own identity. And I've been on a plane this last year almost every week. Talking to all of you about your challenges and what you're looking to get out of this technology. And the feedback has been amazing. So thank you for meeting with me. Thank you for informing us on this journey to help us build the right thing for the industry at this time.

I ran across this quote recently, and I thought it was an accurate reflection of our industry right now. Talent hits a target no one else can hit. But Genius hits a target, no one else can see. And AI agents, they promise to do both. I think as an industry, we're focused on the talent side of this right now. We're looking at our existing processes, making them more effective, making them more efficient, getting cost optimization. But the real prize, the real potential is Genius. How do we get to that product breakthrough that no one even knew was possible. How do we invent new things? How do we discover new cures for diseases. This is the potential of AI. So how are we going to make that happen? How do we get there?

I think watching this technology the last couple of years, we have an intuitive feel for this. It's about more connections. The models get better when you give them more data. Systems get better when you connect them to more other systems to allow them to take actions. That is how we get to Genius. That is how we get to Genius. And we also know, living in the world right now that this comes with risk.

So every process you optimize, you hear a headline about a cyber attack, someone taking advantage of this technology and breaking in. And we all understand that when we're looking for the cure for disease, we could unleash something like a bio weapon, and that's risk. So as an industry right now, we're being forced to choose. We either lock it all down and don't connect AI to anything and get the security. That's no good. We don't want to lock it down or we let it connect everything, free it up and go for the innovation. It's not a great choice.

So how do we get the best of both worlds here. And the solution is simple, not easy, but simple, and that is visibility and control. Bringing visibility and control is how we break this deadlock and get security and innovation. And at Okta, our vision as a company is to free everyone to safely use any technology. So I feel like the luckiest guy in the world leading this company at this time. We're at exactly the perfect moment. We have to bring visibility and control to this industry right now. That is how we're going to enable all of you to safely use any technology. We're the perfect company at the perfect time, and it's incredibly motivating to all of us to go make this happen and change the industry.

We've been at this for a while, 17 years. And if you were unclear how long that is, here's a picture of me right about the time I started Okta and our daughter getting ready to go play some basketball on a Saturday. This little girl, she's going to be like this forever. And this past weekend, in case you were wondering how long 17 years is, we dropped her off at university.

Yes, it's very excited for her. It's definitely a little bit melancholy. But her first day on campus, she called me to complain about having too many systems to log into. And I said, Julia, evidently, 20,000 customers isn't enough. We need 20,000 and one. We'll get to work on that. Every month, 58 billion authentications, 58 billion connections between people and machines and the technology and the resources you need to be effective and productive. So we're in a perfect position to help match security and innovation by solving the challenges of our industry.

So a key part of doing that is standardization. Technology is too complex. It's too isolated. It doesn't work well together. And to bring innovation and security together, we're going to need standardization on a massive scale. So today, we're going to talk about that in 3 sections. The first section is the Blueprint for the secure Agentic enterprise. Second, agent SSO, a powerful new standard that enables agents to connect seamlessly to resources. And finally, Okta for AI agents.

Let's start with the Blueprint. People ask me, Todd, what's your biggest competition? They expect me to mention another vendor or a platform or -- but the answer is something different actually. Our biggest competition is confusion. When I talk to all of you, you're confused. Every vendor is coming at you saying that their solution is the one solution that will help you secure everything, will help you create all the AI you need and lead your organization to glory.

Now you all know intuitively that reality is quite different. What's happening in our industry right now is every layer of the technology stack is being transformed by AI. It's not just one new group of vendors or tools or companies. It's every layer of the stack from infrastructure to applications, to data to agents you're building yourself, agents, start-ups are selling you. So no one company can secure agents alone. It's not realistic. We're talking about a complete transformation of the technology stack.

So we took this feedback, and we're going to do something about it. We went out and we've built -- we've locked arm in arm with some of the leading companies in our industry to create a Blueprint Alliance. And all these companies, industry leaders, AWS, CrowdStrike, Salesforce and many others, they're motivated by the same thing we are. Confusion is their competition as well, and we need to work together to clarify that.

And the Blueprint Alliance working together is centered on 4 key questions. The first question is, where are my agents? Second question is, what can they do? Thirdly, what are they actually doing? And fourth is how do I respond? So if we answer these 4 questions, it will clarify that confusion and put us all on this journey toward building a secure Agentic enterprise.

So the teams have been together, the top product and engineering people from these companies have been together hammering this out in quite a sophisticated level of detail. And just like a Blueprint for a building, it has the electrical sub plan, it has the structural plan, it has the plumbing plan. This -- our Blueprint is broken down into 4 sections. The first section answers the question, where are my agents? This is about visibility and control. This is about an agentic registry, so you can keep agents from multiple systems coordinated and give them all a unique identity.

The second question is about what can they do? What connections can they make? What do they have the permissions to do? Making sure those permissions match the appropriate entitlements that those agents need. This is also about governance of the life cycle of the agent to make sure that an agent today and tomorrow in a month and a year from now still needs the access that's granted. The third pillar is the runtime pillar. It's actually what are the agents actually doing? What is the intent of the call or the application for that agent? And how does it match up with the actual performance and the actual execution.

This is things like network monitoring and other types of monitoring and observability so that we can see that the agents are doing actually what we think they should be doing. And finally, all of this is incredibly valuable because it sets you up and defines how you respond. The kill switch everyone talks about is in this pillar. If something goes wrong, if it gets off track, if it's malicious or it's just an error, how do we actually disconnect it and make sure it stays in line with what we want to do.

So this is all built on a common framework of risk signals. So the Alliance has defined what the risk signals and what the protocol format for sharing the risk signals is. So different parts of the Blueprint and different components of the Blueprint can share risk signals with a common understanding of what they mean. And of course, it's consistently defined how telemetry and observability and monitoring because the whole point of this is bringing visibility and control.

So central telemetry and logging is absolutely important. So there's a ton of detail here, and the keynote would be way too long to go into all of it. So you get out your phone and scan this QR code, it will take you to a couple of important resources. It'll take you to the white paper that the Alliance has defined that lays this all out. And you can also order the room service menu from here.

So we're super lucky today to be joined by a leader from one of the founding members of the Blueprint Alliance. So please let's give a warm welcome to Chet Kapoor, Vice President from Amazon. Chet.

How is it going Todd.

It's great to see you, Chet. Sorry about your travel problems today.

It's called life.

Yes.

Right? We were supposed to be on stage together, and there we are.

So why is securing AI agents in your view, a cross-industry challenge?

So it's really interesting. I've always been very comfortable with speed and my mother would say probably too comfortable with speed. And recently, I have gotten into a little bit of a fan of F1 racing, and I keep thinking about things and how you think about a racecar and things like that. And I actually think that AI is like a racecar, right? And we keep thinking about brakes as a way of actually slowing down. But if you really think about brakes, it actually gives you the confidence to take the corner at full speed.

And so if you start going down that path, you realize that also AI is different from everything we've ever done in software because it's not deterministic. It's probabilistic. And the very thing that gives agents power also makes it really hard to secure because they don't follow the same path every time. And so the way I think about agents is there are a lot like human actors, right, with one big difference, right, that you have access to their brains. But it's very clear, the more access you give them, the more responsibility you give them, the more powerful they get.

And so I love the 4 questions you bring up, and I'm sure we'll talk about it more, like where are your agents? What can they do? What are they actually doing? And when something goes wrong, how do you respond? Because if you answer these questions for every agent, you realize that they're going to be agents all over the place, right? I mean AWS will do them. There'll be SaaS vendors that do them. Customers will build their own agents, and they all have to work together. And that's exactly why we need this Blueprint that we're working with you and many others in the Alliance for.

How do you see it solving this challenge of moving customers beyond prototyping and experimenting and into production? I imagine you guys run into that a lot with your scale and your capabilities.

So it's interesting. I think the biggest thing is I -- we talked about 5 or 10 CISOs a week. And the conversation always comes -- starts from, I want to move faster, but I need to manage risks. And the interesting thing about this where we are, it's not just a CISO discussion with things like [ CISOs ], it's actually become a Board and a CEO level discussion, right? And so I think what customers are really.

No, they can't avoid it. The news is hammering it every day.

Yes. And my take is -- and I think there -- a lot of CISOs are moving, right? They're starting to think about this and saying, I cannot be the one that says no, right? I've got to be the one that actually gives the guardrails and figures out a way to make it happen. So they want some way to move, but they want confidence that they can actually do it. So give -- they wanted to answer your -- the questions you brought up at a very high level for folks is you think about -- they want to see, they want to govern, they want to contain everything in the environment, right?

So make sure that every agent has an identity or verified identity and a named owner, right? Make sure they have task-scoped access, right? What can they do, right? What are they doing? They have real-time monitoring and tracing and then containment, right? Not only stop an agent and let it back in without affecting the rest of the system. So I think the biggest thing that I think that we have to land up doing as an industry is we cannot solve this problem by having more gates and manual reviews. Otherwise, you're dragging AI, this race car back to the human speed. And I think that's going to be a problem.

That would be like a safe Formula 1 race where they only went 25 miles an hour. Not too exciting, Chet. Not too exciting.

No, not too exciting at all.

As the -- what are you -- how are you feeling about the Blueprint Alliance helping the Blueprint evolve as the industry evolves? I know that's an important part. This isn't a static thing that's going to just be here in September of 2026. It's a living, breathing thing. And how are you going to make that happen?

So here's what I think. Ultimately, we are heading towards doing things at machine speeds, right? And the world we're coming from is telemetry, storage query and then dashboards for humans, right? And the world we're heading to is you have all this telemetry, you have context, you have reasoning and then actions by agents.

And so if you look at those 2, that's the bookends where we are and where we're heading. I think it's really important that we understand that it's about starting in learn mode, right? We call it the learn mode, which is you start with humans in the loop, right? They can approve things. And over a period of time, you get humans on the loop where they only are looking at exceptions. And then as time goes on, you get more confidence and there's -- you can go to autonomy.

And there's -- the thing that I really like about the Blueprint is that we actually give folks a trusted ramp to go off and make it happen. And additionally, what I also like about this, Todd, and I know this is Oktane and I'm talking to you. This is a lot bigger than just vendor, right? It avoids vendor lock-in. And this is a lot bigger than Okta. This is a lot bigger than AWS. It's about making sure the industry can adopt and actually go off and make agents work in their environment safely with the right guardrails.

Yes. Well said, Chet. So thank you so much for joining us. Next year, we'll get you out here in person. We'll make sure we have.

Next time, I'll come in the night before.

I can't wait. And thank you so much for being part of the Alliance and helping us build the secure Agentic future together.

It was great. Good luck with the rest of the keynote.

Thank you. Chet Kapoor, everyone. That last thing we talked about is very important. This is not an Okta product. We are locking arms with everyone in the industry to move the secure Agentic Enterprise forward, and it's going to take us all. And Okta as a company, we're -- our independence and our neutrality positions us perfectly to do that. We don't have a horse in the race. We're not trying to sell you a broad suite of security tools. We're not trying to sell you a bunch of applications.

We're focused on identity and building the secure Agentic enterprise and giving you the choice and flexibility and neutrality to make it all work for you. A key part of this Blueprint and some very exciting developments on the standardization we're seeking is in the what can they do pillar, and it's all around agent SSO. Now nothing gets me more exciting than SSO. I'm thrilled by this. It's how we built our company. And -- we need this for agents because the current state of things is not ideal. So here to show you this, please welcome Mallory Sword Glenn. Mallory?

Mallory works in product marketing at Okta. So it's not uncommon for me to send her a message frantically speaking a new road map completely updated with up-to-date delivery dates and status of all the deliverables. Mallory, what do you do?

Sure. We're going to use Claude for that. I'm going to try to automate a lot of the boring stuff here. So to do this, Claude is going to need access to a few things to actually do this. It will need Atlassian for our products. It's going to need access to GitHub to go grab those product issues and then ultimately to Slack to send you that road map. So right off the bat, we'll get into Claude here. And what you're going to see, we're actually not connected to any of these resources. So we're going to need to go through.

Mallory, I said fast.

Right. We're trying -- let's get going. So Atlassian, we will go ahead and authenticate into Atlassian. So I'll click here. I'm going to type in an e-mail, type in my password here as well, once we get to it. And these consents, I can accept these, right, Todd. That seems okay.

So from here, we'll do the next one. We have the same thing for GitHub. So GitHub, we're going to run the same flow here. So I'm going to type in my e-mail again. We'll need to type in the password. And I'm again, this agent is acting on behalf of me, so I can just approve these here. We have one more Todd because we got to send it to you. So we're going to do the same thing for Slack. I authenticate the Slack here. I'm going to type in my email...

A wait a minute. These models are going to take over the world and they can't connect with Slack.

That's what they say. That's what they say. And we will password. Probably should have done this myself at this point, I'll accept, would have been faster. Okay. So as you saw Todd and as many of you probably saw, this was incredibly frustrating for me as an end user, but it was also incredibly insecure. By the end of that, you saw I was just kind of blindly accepting consent prompts for this agent.

So clearly, this is not ideal. Clearly, you might call this a mess. So there's got to be a better way. And that's why we've developed agent SSO. It brings the same great user experience for SSO for a person to the world of AI agents. And -- the great thing about it is we've made it available in every Okta product. So you all have agent SSO. You get agent SSO and you get agent SSO and you get agent SSO. No additional charge. It's out there in the world for you to use and take advantage of. So Mallory, once they use this, what's the experience going to be like?

Let's run that workflow again this time using agent SSO. You're going to notice something different right off the bat. I'm going to log into Claude. I'm going to use FastPass for this. Already, no passwords, already biometrics. Before I ask Claude to pull this road map for you, let's see if we're actually connected to resources.

And if you look here, what you can see is we are. We're connected to Atlassian, we're connected to GitHub. We've got Slack. We also have a few other connections here that have been set up for us. We've got ServiceNow and Google because I need those to do other parts of my job. Notice, I didn't have to do anything here. These were all ready for me right off the bat.

Now you're talking. -- now you're talking. Where is my road map?

Yes. Okay. Let's ask Claude to get to work. So we'll say, go ahead and send that road map to Todd. Now Claude is going to get to work. And Todd, you're going to have that road map by the time you walk off the stage here. And something to point out for the audience, for me as an end user, this was great. My agent worked across multiple applications without ever disrupting my workflow.

For my IT and security teams, also phenomenal. They were able to centralize management of all of this through Okta, and it's flexible and scalable. So as we drop more agents across more and more platforms that access more and more resources, this control will work for all of those participating agents and applications, so we can keep being productive.

Love it, Mallory. Thank you so much. Give it up for Mallory. So clearly, that's amazing. And I know -- not only do I know it's amazing because I see it on the screen, I use it to work. And the experience is great. I go to Claude, it's connected to all my resources, no manual login. So why hasn't someone done this before? What's going on here?

Now the answer is because this actually relies on standardization. And it takes a long time and a lot of work to do standardization. We've been working on this for 4 years now, and we're starting to make a ton of progress and the momentum is really to roll -- starting to roll. Now Agent SSO is based on a standard open standard called Cross App Access. And Cross App Access, the concept is simple. Instead of when an AI agent connects to a resource using the normal OAuth flow, where you ask the user for authorization of the connection, Cross App Access specifies how the technology should instead do that it should ask the enterprise identity provider for the predefined policy that specifies the right grant and doesn't bother the end user and gives that visibility and control Mallory was talking about.

Now for this to work, people have to support this protocol. It's not just a protocol gets invented it is adopted, people have to adopt it. Vendors have to adopt it in their technology. And we've made a ton of progress. You can see some of the vendors here on the screen that support Cross App Access now, which is very exciting. If you have a vendor you like that's not on this list, call them and encourage them and make sure that they support Cross App Access. It's an open protocol. It's not an Okta-specific thing. It's standardization. It's a no regret decision. And now that you all have Agent SSO in your environment, it should be easy for them to make that decision because it's going to plug right into your environment.

So we made another big step forward in the last year. And that is one of the most important biggest AI agents in the world, Claude now with Okta as the first identity provider involved here, now supports Cross App Access, even more incentive for all the ISVs to get on board and support Cross App Access, even gives a bunch of incentive for other identity providers to adopt this open standard. And that's because inside of MCP, Cross App Access is the way to do -- accepted by the standards bodies and the MCP folks to put enterprise authorization into MCP.

And now when Claude talks to MCP, it's looking for that Cross App Access hook and you get the experience that Mallory just showed here. So to drill into this more, we're very lucky today to have one of the co-creators of MCP. So it's great to have David Soria Parra from Anthropic here to talk about this. David? Nice to see you.

Nice seeing you, Todd.

So in MCP development, why was it important that it was open?

Look, open standards are really things that give enterprises choice, and it's something that allows them to review, to secure things and build really as an industry together. If you want to build an ecosystem like something like MCP, you really need to do it in the open. We have seen this with cloud providers in the beginning. We have seen it now with identity again. And with that agent, it's once more that we see that we need common standards to truly power like agentic infrastructure.

Does the success -- the openness of MCP, does the success of MCP, does it exceed your expectations?

It very much exceed.

It kind of change the world.

Yes, it does.

We're very proud of that.

Absolutely.

I don't know if you've been able to get a daughter into college, but close.

No. Look, I think when you start out like that with what you try to be a standard in the world, I think you never really expect it to be that broad and that big. And we're super fortunate that we have like all major AI providers. We have cloud providers. We have most Fortune 500 in the world like really adopted. So I'm very, very glad that it's been like the crazy success that it's been.

Yes. In your view, what is enterprise authorization and Cross App Access in enterprises and your customers? What does it enable? And you've talked a little bit about it, but what do you -- from your perspective, what do you see?

Yes. I think -- so one thing that's important is as models get more and more capable, one of the key pieces is really for enterprises to provide models with secure and safe access. And part of that is also providing a product experience that is both seamless and secure at the same time. And what enterprise managed authorization really does is move away from like allowing or having the consent screen in front of the user and to more pushing a lot of the security and safety aspects towards the IT admin, while at the same time, providing a really smooth user experience.

And I think that is really important for us in the world to like make AI systems more broadly approachable, but also at the same time, to really unlock a lot of the capabilities in the model as they are connecting to your enterprise SaaS systems, to your internal systems and so on.

This OAuth protocol was invented to share your Twitter feed. So I think it needs some updating.

Yes.

What -- you mentioned more capabilities for the enterprise. What's next for IDPs and models and security? What do you see as the big rocks left to move in terms of our effort to make the secure Agentic enterprise?

Yes, it's a good question. Look, we have built identity and authorization mechanisms for humans in mind for the last decades. And a lot of these assumptions just don't work for agents anymore. And so there's still a lot of open questions regarding sign authorization, intent-based authorization in time provisioning of identities for agents that we need to solve as an industry together and that we need to continue to develop across AI labs, across identity providers like Okta, across cloud providers, standards that can really power this Agentic infrastructure.

In many ways, it feels like the very early days of the next revolution of building this Agentic infrastructure. And part of that is really building together as an industry, these standards everyone in this room can rely on with their companies, with their enterprises.

Yes. Well, congratulations on your success, and thanks for doing what you with the industry and with Okta. We really appreciate you being here and sharing a little bit of the story with us.

Thank you so much.

It's good to have you, David. All right.

We talk about agent SSO, and it is a big step forward in standardization, and we've made a lot of progress. But it's only part of the story. It doesn't -- it can't discover agents you don't know. It can't do agent governance. It can't broker connections with -- between different kinds of protocol. It doesn't have a kill switch in it. For that, you need something more. And that's why we're building Okta for AI agents. It's our flagship product to do the identity portions of the Blueprint.

So the Blueprint covers many things, but a lot of the parts -- the foundational parts of the Blueprint are all around identity, and that's where we focus. So Okta for AI Agent is to build the identity portions of that Blueprint while, of course, working seamlessly with everything else in your environment to secure the Agentic enterprise.

Now Okta for AI Agent is a GA product. Now you might think it's odd that I'm emphasizing that, but in the current hype cycle in our industry, let's just say it's not uncommon for products to be preannounced and products to be pitched as they're here today, but they're really far in the future. And we're very proud of the fact that Okta for AI Agent has been generally available since April. And we're not stopping there. We're innovating quickly and continue to deliver more. Many of you are using the product and seeing the success. So how are we able to do this? It's actually quite simple.

First thing is we organized the company in a different way. So we have at Okta, an AI takeoff team that reports directly to me. And their job is simple. Their job is to work with all of you and deeply understand your environment, what challenges you have, what you need to better serve your end users to improve your security posture, deep understanding of your environment. And then to take that learning and pump it directly back into the R&D team. And we've reorganized the R&D team to make sure we have one unified team that gives us the priority and it gives us the bandwidth and the firepower to not only build the Okta for AI agents product, but remember, this is seamlessly integrated across all of our products.

So every member of every team and to some degree, is also working on Okta for AI agents. And another thing we do is I meet with the R&D team every day. I meet with them every day, removing obstacles, seeing how I can help push them along. Now you can ask them if they think this is a good thing or a bad thing, but I like it. And we're seeing a ton of success. And the customers speak for themselves. Three -- there's many more, but 3 that really stand out are first Ramp. So Glass is an AI agent for internal productivity at Ramp. And Dmitri [indiscernible] there is our champion at Ramp. We love working with Dmitry and the team. So thanks, Dmitry, for all your work.

And they've seen tremendous success across this productivity suite across the entire company, Yahoo!. So we're going from an emerging fintech star to an Internet icon in Yahoo!. Now Yahoo! has something internally called Y Connect, which is like an Agentic system for software engineering and they're evolving over time into more of a harness for all of R&D. And this is built on Okta for AI agents. Okta for AI agents brokers the connections between this agent harness and their virtual MCP servers, giving them visibility, giving them this kill switch. We're really excited to work with Brian Meister and the team at Yahoo! there.

And finally, Dell Technologies is overhauling their complete company, but more specifically their customer service and success organization by having an AI platform that automates and suggests the next best action for all of their services people. And Dell operates 100,000 people at massive scale. They can take the learning over millions of customer interactions and the AI crunches that and feeds it back into the next best action for their people, which means better outcomes for their customers, better customer satisfaction and what everyone wants, more revenue for Dell.

So it's 3 amazing stories. And it's not just these stories. Okta ourselves are using this product internally, and we've had a ton of success. We have an internal AI agent called Dex, which is connected to all of our internal systems and automates a bunch of work that employees had to do manually in terms of internal operations, and we're going to save 250,000 hours this year, hours that can be spent doing more productive things like building great products for you and providing better service to you. So Dex is a huge hit, and the visibility control is all based on Okta for AI agents.

We have a way -- when we started really using agents internally, the marketing team was actually an early adopter that took off and was innovating here. And instead of locking it down and worrying about risk of data loss, we used Okta for AI agents to cover that risk and push that innovation forward. And now we have a central hub where they can share these -- the whole company, 100% of the company can share these AI agents across -- collaborate with other people and share best practices and people can use the agents. And we've seen a ton of benefits in productivity, but also unexpected things.

Like, for example, if you actually get the authorization right on what tools the agents can call, you can actually save money. Up to 90% of cost of the tokens can be decreased in certain cases because the agent isn't spinning through tokens, looking at tool calls, it doesn't even have to access the call anyways. So it's like unnecessary work and you can save costs there.

So we're moving very fast. We have a tremendous amount of focus. We love the feedback from you, and we're using this AI takeoffs team to make sure that this is not a big science experiment. We are building innovation in the product that's prescribed and purpose-built for your environments. And we're committed to keeping up with that and keeping investing here so you have this secure agentic enterprise. We have 25 major features we've released since April. So the drumbeat is happening. You can see the breadth and the capabilities we've been releasing here.

And 3, I think, are particularly important. The first is shadow AI agent discovery for endpoints. The second is the agent gateway. And the third is third-party IDP support. First, we all know that in last year, what's happening on the endpoint, mostly on your developer's laptop with CLI and client-based agents is a big deal. Powerful, a lot of innovation, but also a lot of risk. Developers have access to tokens, and many times they have access to production, and it's a big problem. You need visibility there.

So this capability integrates both with CrowdStrike and with the Okta Verify app to make sure you get complete visibility into what's going on in the endpoint, and that gets piped back into Okta for AI agents, letting you have visibility and then make the required controls and protocols around that to make sure that you mitigate that risk. Second is our most requested feature, and that is agent gateway. It's a virtual MCP server that allows you to place all of your MCP servers behind this virtual server and then use Okta for AI agents to govern the authorizations and the permissions to groups and roles and users across every tool in the whole catalog.

It works with MCP servers you built yourself or MCP servers that every SaaS application is providing for you. It's a very important control point. It gives you complete visibility into what's happening because it's a gateway. It's a network gateway that actually is in line with the traffic. It gives you the ability to take tokens off the client and house them centrally in the gateway, which is much better for security. It allows you this kill switch. So you know that there's no way around it. The agent has to go through this gateway. If it's calling MCP servers, you know it's going through this gateway and you can shut it down when you need to.

The last capability, I'm going to talk about today here is this support for third-party IDPs. Now we realize that not every company in the world, including my daughter's college, does not use Okta as their IDP. Now that part of our soul internally, that's very frustrating for. But we want to support those organizations with Okta for AI agents as well. So Okta for AI agents now works with third-party MCPs. So you can have your human identities in one system and still manage your Okta identities and Okta or your agent identities and Okta for AI agents, so you can implement this Blueprint in a heterogeneous environment, which we all know the reality of every one of your environments, it's incredibly heterogeneous. No one company can secure agents alone. So we're taking this independent neutrality incredibly seriously and investing here with supporting third-party IDPs.

Now we've talked -- a lot of this conversation has been about internal productivity and how can we make our processes, existing workforce more productive. And I think that's the right place for the industry to be focused on. It's -- sometimes the risk will be lower. But I think that if we really want to get to Genius, if we want to have the product breakthroughs that no one thought of, grow revenue, take over new market share, expand our organizations, fulfill our missions more, we need to get to the customer-facing activities. And we're investing here as well.

We support Auth0 for UCP and the Auth0 platform. So Auth0 for UCP is Universal Commerce protocol. It's a way for the Gemini AI agent in that platform to interact with any e-commerce site that supports UCP to do account registration, shopping cart, checkout, basically make the commerce experience inside of Gemini seamless. And if your e-commerce site uses Auth0 as the identity provider, now that works seamlessly with UCP.

So this is more -- I think, more of an emerging area for the industry, but my prediction is in the next -- when we're here next year at Oktane, customer-facing Agentic is going to be a huge deal, and our whole industry is going to move there. And this is going to have the same kind of tension between what's the risk? Should we lock it down, should we open it up for innovation? And our principles and the governing architecture of the Blueprint is going to work here as well. And it applies just as much to this side of the equation as any other side. So we're excited to continue to innovate here.

How about we see some of this stuff? Harish, let's welcome Harish. Harish Peri, come on out.

All right. Thank you. Thank you. What's up Oktane? No, no, no, that's not going to cut it. I said what's up Oktane? That's better. That's what I'm talking about. So our customers, all of you, you are the key to our AI innovation. You're moving fast, but we're listening, we're learning, we're keeping pace. So thank you, keep the feedback coming.

Now one such fantastic customer is the PGA, the Professional Golfers' Association of America. Thank you so much for being an awesome customer of ours. They're on a great journey. They're transforming their whole enterprise. Let's take a look at the video. Let's roll tape.

[Presentation]

All right, give it for PGA, thank you so much for being an awesome customers. Now what's great is they're on an Agentic transformation journey. They're deploying agents for their workforce, they're deploying agents for their customers for Agentic commerce. It's a complete transformation. So the next couple of minutes Mallory and I are going to show you how Okta secures AI for the PGA. But I want to anchor everyone in one fundamental principle, which is in Okta every agent is an unique first-class identity this is important. We are not representing them as users, we're not hijacking service accounts. They're a first-class identity that gets all represented here in Universal Directory.

Now every agent gets a unique cryptographic identity. They have a human owner. So if something goes wrong in the governance cycle, you know exactly who's accountable. But what's better is these agents come from everywhere. They live in AWS, they live in Salesforce, they come from ServiceNow. They are agents that represent workforce agents, customer agents. They can be manually registered. They can be pushed in here automatically through your DevOps pipeline. It doesn't matter. This is the one-stop shop for your secure agentic enterprise.

Okay. Now let's dig into this. Let's answer the very first Blueprint question for PGA, which is where are my agents? This is Okta's ISPM, Identity Security Posture Management. Now ISPM discovers agents from across their enterprise. These are agents that are running on the endpoint. These are agents that are embedded in known platforms like AWS or Salesforce. These are agents that are running in the browser that need OAuth consent grants, and these are shadow MCP servers. It doesn't matter. They really have nowhere to hide. ISPM discovers them all.

Now let's look into a specific type of discovery, the endpoint agent. I've spoken to so many of you on a regular basis. And the one single biggest point of heartburn is I have these local agents running on my people's endpoints. I don't know what they're up to well. Fear not. ISPM now integrates with CrowdStrike and with our own Okta Verify, so we can discover these endpoint agents and bring them into the light. We can see critical metadata like the Agentic harness, the name of the agent, the associated user and any MCP servers that this agent might be using.

Let's actually click into a specific agent. Right here, in ISPM, we have the AI agent graph. That gives me immediate visibility into this agent's entire blast radius. I can see who's accessing it and I can see what resources this agent in turn is accessing. Now in this case, I can see it's connecting to Slack and some kind of a homegrown MCP server. This MCP server was never approved nor was it registered. It's the perfect definition of shadow AI.

Now this is where ISPM changes from being a phenomenal UI and a phenomenal discovery tool to actually being fully integrated into our platform. Right with an ISPM, I can register this shadow agent and the Shadow MCP server directly into Universal Directory. And I want to emphasize what we just saw. We took a shadow agent. We took a shadow MCP server that was running on some laptop somewhere. We discovered it, we surfaced it. We gave it a unique identity. We brought it into the light and now it's part of Universal Directory, all within the same platform.

No e-mails, no tickets, no calling somebody, no texting your friend. It just happens in one place. It's securing AI. That's what this is all about. That's pretty cool. But that was only question #1. Let's move to the second Blueprint question, which is what can these agents do? So let's click into this one specific agent. That's a SalesOps agent. Now this needs access Salesforce and Gmail. It's a very typical kind of workforce agent that we have at a lot of our customers.

This is the configuration designer. This is phenomenal because here, I can visualize the entire access graph, every connection, every other agent that it's delegating access to, every MCP server on the path from user to agent to resource. I want to emphasize a very, very important point here. What's incredibly important is this is not just about UI. The UI is fantastic, huge kudos to our teams that are building this. Thank you to the customers for all your feedback.

But this represents one of the biggest pain points that I hear from all of you every day, which is chain of custody. This actually shows me the entire delegation chain from a user to an agent to potentially a subagent to an MCP server to a resource, all connected in a single unbroken log chain that is logged to our system logs and streamed out to your SIEM if you need to for threat modeling. This is huge because without this, you have no auditability, you have no traceability and you're pretty much flying blind. And trust me, when that end of your audit happens, this is the stuff you're going to need to tell the auditors exactly what your agents can do.

Okay. That was question #2. We discovered agents. Where are my agents? What can they do? We mapped out their connections. We got to keep this rolling. Now we actually need to see what happens at run time when these agents are executing what they were meant to do, which brings us to the third Blueprint question. What are they actually doing? You have to control what they do. You need to be able to look at exactly what tools you're talking to and shut it down if something goes wrong. So to show you that, I want to pass it over to my friend, Mallory, take it away.

Thanks, Harish. So we'll use agent gateway for this. Normally, every single one of these agent to resource connections would be its own integration point with its own set of permissions. But Agent Gateway puts one control point in front of all of them so that I'm not managing dozens of point-to-point integrations. What this means is that I can now see and control at a really granular level what this agent can connect to and set what it's allowed to do all in one place.

For our sales agent specifically, it only needs access to Salesforce, especially for the sales auditors group. We can use agent gateway to scope that down right now. We'll click in, and here, we can see all the different tools. We'll just click the ones that we need here, easy enough. Now agent gateway is also where our enforcement will happen at run time.

That means every time this agent calls a tool, the gateway is going to check identity. It's going to apply the policy that we just set, and it's going to write everything back to our audit log in real time, which brings us to that fourth Blueprint question. How do I respond? We head over to Claude. What we'll see is we have our sales agent. Let's put ourselves in the shoes of a seller. Let's say that our seller needs a summary of their top 5 accounts.

Go ahead and ask our sales agent for that. And our agent is going to use those managed connections that we already set up to actually pull that list from Salesforce. We notice how I didn't need to authenticate or consent to anything here. Let's see our seller is going to be on the road today. They want to be able to access this list on the fly. They try to send it to their private e-mail account, personal e-mail account here.

And when they attempt, you're going to see 2 things happen. First, the agent refuses this request. But second, you'll see that connection to Salesforce is now severed. Okta detected this exfiltration attempt and automatically blocked this tool call. Now while the prompt itself here might not have seemed malicious and the seller didn't even mean it that way, it could have ultimately left sensitive customer data sitting in an unprotected personal inbox.

And this is the power of having all of our authentication and authorization in one place. You can block those individual tool calls and flip a kill switch the moment this agent is asked to do something that it shouldn't. Let's take over and see what happened behind the scenes here. In Slack, our security team got an alert right away. We'll click into this to get a little bit more detail.

In it, we can see the MITRE tactic that we used here. We can see the rule, the severity and some other details that we might want information on. Now if I want to see even more detail on this, I can click full session here, and I'll see everything from this session from the prompt to the agent tool call all the way through to that response.

Now what you just saw was the Blueprint in action from design time to run time. We took an agent in Universal Directory with a unique identity and a named owner. We then applied policy for this agent using least privileged access. And then at run time, we evaluated every single tool call to make sure that identity is in the loop. And then when that agent was asked to do something that it shouldn't, no big deal. We flipped the kill switch and cut off its access to that resource. But these internal workflows are really just one piece of the puzzle. For PGA specifically, they also serve millions of customers every day.

Harish, what does this look like when it's a customer that's interacting with these agents?

Yes. customer-facing agents are a whole different game because you're talking about experience, you're talking about reducing friction. You're talking about people trusting you with their money for sensitive transactions, that changes the game entirely. Now your customers and PGA customers, for example, are already shopping through AI tools like Gemini. It's a phenomenal experience. It's right where they live and they work, and we have to meet them where they are.

They can look for products, they can compare prices, they can get personalized offers and they can execute transactions without ever leaving the agent. This is where Auth0 comes in. Retailers can stand up a universal commerce protocol or UCP server, secured by Auth0 and that plugs directly into these AI ecosystems. Let's take a look.

So this is a customer who's shopping on Gemini. They're new to golf. So they're going to use Gemini to look for some golf lessons and possibly some golf merchandise to get started. Now this agent is going to show them personalized results for this customer. This is a very complex prompt, and it's actually evaluating all of this. And this is great because the customers can type in exactly what they want. They don't have to click through 15 different screens. It just works.

But what's more is these are personalized to this customer. They are a new customer, which means they get offered a special new customer discount. It's higher than those for existing customers. It's personalization right in their experience. Now the key is when it time to check out, they actually need a PGA account. That could be a lot of work, but because they're already connected to Gemini through Google, all they have to do is to consent to link the account. This is huge because this customer doesn't have to type in a user name and password. There's no friction. It just works.

And for PGA, they don't have to do any additional work. It just works. That's how awesome this is. But as we continue on this journey, now this customer wants to finalize this purchase, this is where money is changing hands. So we want to always make sure there is a human in the loop. The customer receives a notification on their phone, they approve and they're on their way, all where they're right inside their Gemini experience. It's pretty phenomenal.

Now a little bit more. If this customer sees that there's an AI client that's connected to their accounts that they didn't approve or that looks a little bit fishy, they can kill that connection right there. Okta's job is making sure that, that experience is secure enough to trust and simple enough that the customer always stays in control. Okay. We saw a lot. We saw how PGA, a phenomenal organization is transforming themselves becoming a secure Agentic enterprise. We saw how they're rolling out workforce agents, Agentic commerce experiences. We saw how we're helping them answer the 4 key Blueprint questions, where are my agents? What can they do? What are they doing? And how do I respond if something goes wrong.

Ultimately, when you bring this all together, that's what it means when we say Okta secures AI. Now one very, very important point. Everything you saw here is available right now or is expected to be available by January. This is all real stuff. We're moving tremendously fast based on your customer feedback. So thank you, keep it coming. What's even better is we have multiple road map sessions throughout the day where we're going to click into double, triple click into detail on every single feature, bring us your feedback, let us know what you think. It's going to be fantastic. What do we think? How what do we think? Do you like it? There we go. There we go. All right. I'm going to have Todd come on back out. Todd?

Nice job, Harish.

Thank you. Thank you.

So you are the leader of the AI takeoff team.

Yes, sir.

So that means you're the tip of the spear.

That's exactly that's what you tell me every day. So...

Do you like this? Do you like this job?

I'm loving it. Dream job.

How many of these innovations were prompted directly from customer?

Every single one, agent has unique identity, authorization, the governance work, the kill switch, intent authorization, everything. This is all thanks to all of you. So keep it coming.

Yes. Thank you so much, everyone. We couldn't do this without you. We really value your collaboration, and we're going to keep the ball rolling here. Thank you so much. Harish Peri.

Thank you. Thanks, Todd. Thank you.

Okay. Now we're going to hear from a great Okta customer that's really on a role and been with us for a while.

[Presentation]

Now we're super lucky. So let's get loud and bring on an amazing leader from a great company, Doug Schmitt, CIO and President of Dell Technologies. Doug?

Todd. Great to be at Oktane.

Thank you for being here, my friend.

Yes.

So Dell has been on this Agentic journey for longer than most other companies. What started it? How did you get there? I mean it's been a while now.

It's been a long journey. I think actually, you have to start back about 6, 7 years ago, actually. We actually started by digitizing our processes. It's been a digital journey for a while. where we looked at everything and we said with machine learning and where we were headed with the ability to do data science, we had a huge opportunity in front of with structured data.

So 7, 8 years ago, we started digitizing our processes, seeing where things were at on the structured data, then let's carry that through when AI really started with unstructured data. And we thought, wow, this is really a huge opportunity. And we saw 4 major platforms we could build inside a Dell about 2 to 3 years ago, actually about 3 years ago. And those were around our supply chain, our direct sales team as well as our services, next best action and then our incredible development programs that we had in terms of our R&D.

And so we started building the AI around those platforms. It quickly -- we could see where agents were coming where they would do work autonomously or together and then help build that around. So it's been an incredible journey.

And around that time, you made the, I think, the really prescient decision that every agent was going to have an identity. What gave you that insight? Or what was that -- again, you were ahead of your time on that.

Well, I think...

I mean I'd love to say it was my idea.

When we met with you, clearly, you and your team almost 2 years ago. Once you had the platforms built, you could see agents could work together autonomously or stand-alone, observability. Look, it's all about observability. What we knew and then when we were talking to you was if we could see it, we could manage it. So you had to have that observability and it built into the agents right away as well as we had to have them track.

So we could see, hey, where are these agents being used? What are they being used for? And more importantly, who's using them? And so from there, you start to build backwards and say, okay, how are we going to do that? And that's when we started.

And this is all in context of an overall, really, I would call it, massive run of transformation and success at Dell. And so we're talking about the -- a lot of the internal efficiencies, but you guys are trying to get to Genius. You're thinking about the external and customer-facing. How does that fit into this equation for you?

Well, I think if you saw where the journey was after the observability and we knew we could start to track that, get it into the architectural plans, we actually started looking at the platforms and saying, okay, you're going to have to have agent Agentic to agent to agent, so you could have identification inside of there. We also started then quickly identifying you're going to have grandparent, parent, child relationship with those agents, everything that you've kind of been showing up here to see this afternoon or this morning.

And from there, what we could see is that what we could do is stitch things together end-to-end internally, if that makes sense. So these platforms could now start speaking together from those agents, have manager agents. And what that really does, that really opened up a whole new area of Agentic, which is the key to all of this is really about what we're providing our customers, their end-to-end outcome and experience, that horizontal, well, those agents gave us that ability to start delivering on that promise.

It's really transformational. So you thousands and thousands and thousands, and I'm sure more people joining the live stream right now, IT leaders, security leaders, general people. What's your advice? So you've led this transformation. What do you actually have for the room?

I don't know that I'm qualified to give advice because we're still in the learning. I think we're in the early stages of all of this, right? I'm drinking from a fire hose like everyone is. But what I do believe is that this is beyond just a technology change. This is a business model change. And to that end, it has to be an all-in experience. And what I mean by that is it can't just be IT-led and driven. This has to be a company-led and driven program.

You have to rethink how you're doing things. Business models are changing. AI native is out there. It's going to be a competition or it's going to assist you with your business model. And then I will tell you what I always tell my team, it's 3 things: speed, speed, speed. This is moving at a faster pace every day.

Yes. That's super exciting. Thank you for your collaboration and your partnership. It's great to work with you.

As always. It's a great partnership.

We're excited to deliver for you, and we're also very appreciative to get the input and help us push forward on our road map and work together.

Look great, Todd. Always great to see you. Thank you for inviting me.

Doug Schmitt, absolutely. Doug Schmitt from Dell. Give it up for Doug.

Thank you.

So this is absolutely critical that we do this together. We need to build this secure Agentic enterprise. So here's my ask of all of you. I want you to download the Blueprint. I want you to join the Alliance. I want you to encourage your vendors to embrace the Blueprint and get that clarity in the market and avoid the confusion. I want you to encourage everyone to support Cross App Access.

I want you to help us all in this journey for massive standardization. It's the only way we're going to get the visibility and control we need. And it's the only way we're going to be able to get the security and the innovation. It's how together, we're going to get to Genius, and we're going to do it.

And the last thing, I want you to buy Okta for AI agents. I'll just come out and say it. The talent hits the target, no one else can hit, but Genius hits the target no one else can see. So let's get that visibility and control. Let's change the world together. Let's get to Genius. Thank you so much. Enjoy the rest of Oktane.

All right. Excellent. Hey, thanks so much for joining us at the Okta session, Day 2 of the Goldman Sachs Communacopia Conference. My colleague, Callie Valenti, and I are really excited to have Eric Kelleher, President and COO of Okta Ventures. Hey, thanks for joining us today.

Thanks for having me. It's great to be here.

Eric, I want -- I thought maybe the way we could start this conversation is to imagine that we're one of your larger enterprise customers. And the customer calls up -- calls you up or calls up their salesperson and says, "Look, we're really concerned. We want to do all this cool stuff with agents, but everything we hear in the news is terrifying. You are our trusted identity partner and make our problems go away." Talk to us about what that customer conversation journey looks like.

Yes. Our leadership with customers is typically to help them understand the problem. So the biggest competitor -- Todd talked about this on earnings, but the biggest competitor we really have right now is just confusion. So for an enterprise just trying to navigate the technology landscape today, it's never been more volatile and the security landscape has never been scarier. And so -- and every vendor is pitching to them all the various ways they're going to solve all their problems.

And so, one of the first steps that we've taken to help customers is just to simplify the landscape. And so we published what we call the blueprint for the Secure Agentic Enterprise.

So hey, we want to do something with agents. We don't know how to navigate this. So we've given them a blueprint. And the blueprint tells them they need to solve for 3 things. One is, they need to know where are my agents? So there's a problem of discovery of understanding where agents have been activated by employees, where they exist within the company, where are my agents?

The second challenge they need to solve is knowing what can these agents connect to. So what systems have these agents been allowed to connect to talk to? And the third thing they need to solve is, what can they do? What have they been authorized to take? Can they read? Can they write? Can they delete? So those 3 questions. Where are my agents? What can they connect to? What can they do?

Those are the 3 things that customers need to be able to address to give them confidence in their -- what we call their security posture as it relates to agents. And our -- not surprisingly, our implementation to address the blueprint maps to our product offerings with Okta for AI Agents, and we help them do exactly those 3 things.

I want to ask you an architectural question, which is we hear particularly from new entrants in the identity space that the way that you do identity access for agents is fundamentally different than the way you do it for humans. And the reason that is, is because agents are ephemeral. And so, it's really tricky to take an architecture like Okta's and make it work for an agentic architecture because of this change in scalability, throughput, ephemeralness for lack of a better word. Maybe push back against that hypothesis.

Yes, I was going to say we don't agree with that, so that's not surprising. The -- first of all, not all agents are ephemeral. Part of the challenge is -- in this landscape is the word agent means many things to many people and vendors reapply it to whatever is going to suit to whatever narrative that they want to share. At its core, we have over 20,000 customers today that trust Okta to secure identity.

Securing identity started for them with securing their human identities with their workforce and then their extended workforce and then their customers. And from that base, we've earned the trust of customers that we have the capabilities and the know-how to secure identity and keep them secure. It's a natural extension of that trust to now talk about how we're going to help secure the agentic identities.

And agents, pieces of autonomous software that typically today run on behalf of a human, in the future, we can all see a future where that's less the case. But today, they run on behalf of a human that's enacted them. They need an identity. Whether they're ephemeral, they come on and off as they're needed or whether they are permanent, they're running 24/7, the agents need to have an identity. As a company, I need to know what agents exist. I need to know who created them. I need to know what they've been given access to and what actions they're authorized to take. And to do all of that, I need to have an identity for that agent.

So Okta provides a universal directory of identities. And historically, those identities were human, first workforce, then customer, then service accounts and now agentic. And so that directory has expanded in this use case that allows people to manage that. And then once you have the identities in your directory, all of the capabilities of the Okta Identity Security Fabric apply.

So single sign-on, we just launched Agent SSO a couple of weeks ago. It's now GA to all of our customers on our workforce platform, which means customers can now add agentic identities into their directory at no charge with their existing platform. Our governance capability, which allows people to provision and deprovision accounts. So in the case of an ephemeral agent, just-in-time provisioning and then deprovisioning, turn it on when it's needed, turn it off when it's not. So it doesn't have standing privileges.

And things like auditability, who authorized an agent to access the system, who gave it delete access. All of that's captured in our governance product, which does all of that for human identity and will now also do it for agentic identity. So the Identity Security Fabric story has never been more real than right now with this new category of identity, which we've elevated as a first-class identity category in our stack and all of the use cases for humans are now available to agents as well.

I want to ask you a little bit about what separates out the customers who are signing the multimillion dollar deals from those that are still deliberating and evaluating and saying, "Look, the technology is changing so quickly. We don't want to commit right now." How do you get more customers from the evaluation uncertainty confusion stage through to, "Here is a multimillion dollar deal?"

Yes. It's -- the sample size is still small. So I'll speak to the examples that we have. But we announced with our quarterly call, we've done dozens of transactions on this product. Remember, this product went GA on April 30. So we're less than 120 days in at this point. So we're still learning -- actually, just crossed 120 days. So we're still learning how to shape this product and how to shape the transactions and how to shape the pricing in a way that's going to get people over the hurdle.

But I'll say there's a couple of different categories of what causes first movers. One is, we have some enterprise CIOs and Chief Information Security Officers, CISOs, who are very forward-looking in their vision, and they see where the market is going, and they know that this is something that they have to solve more so than their peer group and they're investing ahead. We have some customers that have seen agentic activity that's caused them concern and that gives them an acute need to make sure that they're investing ahead.

And we have some customers that surprise themselves. So one of the examples Todd talked about on the call was a multimillion dollar deal we booked in the quarter with a Fortune 50 healthcare company. And one of the specifics we shared on the call is, we had a discovery call with them to talk about Okta for AI Agents and what we could do. And at the moment of that initial discovery call, we asked them how many agents that they had deployed and it was 50. They had 50 agents deployed.

And we came back to them a few weeks later for a follow-on call, and that number had increased from 50 to 1,500. And so that realization, the customers' realization, they can't wait. Like they -- this wasn't a problem they could wait. They saw the path, and that was a catalyst for them. Then another thing that we're doing to help convert people is we made it easy to buy. A lot of vendors that are in this space right now are experimenting with pricing models and they're exploring agent-based pricing models. But it's -- you create a chicken and an egg where you ask people how many agents they're going to have, but they don't know how many agents they're going to have.

And not all agents are credit.

Not all agents are the same. An agent that monitors your e-mail is different than an agent that runs your quote-to-cash process. So it becomes -- what ends up happening is your cycles become very long and very detailed and very onerous. And so we've removed all that complexity right now. Our pricing model today is simply an uplift on the per user pricing, which is imperfect from an agent architecture standpoint, but it's really easy to buy. And so our customers know that there's a predictable purchase amount. This is what we're going to pay with Okta to allow us to secure agentic identities. And our agreement with these first transactions is we're mostly doing 1-year transactions.

The one you mentioned is a multiyear, but we're mostly doing 1-year transactions and very open expectations with the customer that, "Hey, a year from now, you're going to have better information on how you're using agentic identity and securing that with Okta," and we'll have better information on what it's costing us to manage that security. And so the pricing model will likely evolve. But today, we're making it really easy to get started, which is what our CISOs need. They need to be able to get started to secure this challenge that they have.

Let me ask you one more on pricing, and then I'll hand it over to Callie. How did you pick the pricing uplift given all of the moving pieces that you just highlighted?

In close collaboration with early customers. So we've created a specialist team for securing agentic identity that has these conversations all day, every day. And we've talked to many hundreds of large enterprise customers who have an acute need and a need to buy and a procurement process and a budget. And we have set the price to value based upon what these customers have shaped with us. So we feel right now very good about where we're starting, and we're very confident we will evolve this over time.

So I wanted to ask, a year ago, we were having a conversation on which part of the identity stack was going to benefit most as a result of agentic. And it feels like what you guys have come out with is kind of grabbing a little bit from each of those categories. You've talked a little bit about the PAM functionality. We know that at some point, organizations are going to have to prove that agents don't have access to parts of an organization that they're not supposed to and prove that to regulatory agencies. So with all that being said, like how do you think about what that product looks like today versus kind of what you would need to secure a human?

I think it's interesting for -- I talked about this, I think, last time we were here. But a year ago -- our user conference every year is in September, and it's coming up in a couple of weeks, a bunch of exciting stuff to announce, so pay attention. But last year, our headline for our user conference only 12 months ago was the Okta Identity Security Fabric. And the Security Fabric story was our very common narrative with customers that -- what I hear from customers is the complexity in their fragmented environment causes them to feel insecure.

And looking for an identity partner that can solve for all their categories of identity across all their identity use cases from access management to governance to privileged access to development is very important to them. And that was our headline a year ago at our conference. And our subtext, our secondary topic was securing AI. And boy, how the world has changed in the 12 months since then, where we have -- we continue to provide Okta's Identity Security Fabric. We continue to innovate very aggressively. I feel great about our product velocity right now. We've continued to acquire technologies, which improve our product capabilities.

So our Permiso acquisition, which we closed the day of earnings, is going to significantly accelerate our product road map for our Identity Threat Protection product. These are all exciting innovations into that Identity Security Fabric. But the conversation that's been most vocal has been the conversation about this need to figure out what's going on with agents and how we secure agents. But both of them are very real.

So for us, the way that we look at the landscape, the Security Fabric is still the core. People don't need to solve just token management or just just-in-time provisioning or just access management or just on-behalf-of ability, they aim to solve all of that. And our product portfolio is the most broad portfolio to address all of those use cases. So we'll be talking more about that this year at Oktane as well, which is in 2 weeks. But yes, I guess that's how I would respond to that.

And identity M&A has become very popular, both from companies that sit in security, but maybe haven't traditionally been part of that identity stack and also for companies that are outside of that security definition, I would say. How has that kind of changed the competitive landscape? Where do you see kind of the pros of Okta's positioning versus those other companies? And maybe as part of that, you can talk a little bit about like the importance of being independent.

We think it's really validated. We've been saying for 17 years that identity is the fundamental perimeter. And there are different players that have felt network was the perimeter or that felt that systems were the perimeter or endpoint was the perimeter. We have long established identity as the perimeter and how to ensure you have a secure enterprise corporation. So the steps that you just mentioned, recent acquisitions are really validating that that you have to be with identity to secure it.

And we have a 17-year head start on establishing that and broad distribution with our customer base to demonstrate our ability to deliver on that. And that's been -- and we've been very successful with that. That being said, we also partner with everyone. The -- you mentioned the importance of neutrality. The stack vendors, whether it's an application stack or a security stack or a network stack, the stack vendors that are dabbling in identity are just that, they're dabbling.

And everything that they build in their road map is going to evolve to perpetuating their stack. We're the only provider that has identity as the perimeter that integrates with everything. There's over 8,000 integrations with Okta out of the box. And people have come to Okta to integrate their technologies with us because they see us as the identity layer as the perimeter. And because of that, buyers that buy into Okta know that they have flexibility.

They know that they can use best-of-breed technologies wherever they want to because they'll all work with Okta. And right now, we are seeing more volatility in the tools than we've ever seen. If you look at these -- the frontier models right now, they're leapfrogging each other every 30, 45 days. So our buyers are seeing this need to be agile, the need to be able to adjust the technologies that are in their environment more acutely than they've ever felt it before, which make neutrality that much more important, which speaks to a core differentiator for us.

Yes. And then I wanted to ask about CrowdStrike specifically. I think they've had some identity offerings out in the market for a long time, but I think labeling it as identity versus what Okta does it almost sits a little bit next to each other versus overlapping. So if you could walk a little bit through like how some of these tools are complementary to Okta versus competitive, that would be helpful.

Yes. We have thousands of mutual customers with CrowdStrike as an example, and we expect that to continue. And their positioning in endpoint, in particular, is uniquely strong, and they're a provider of shared signals into our threat detection product, and we continue to leverage that. So we believe there's plenty of room for their stake in what they're doing and where Okta is standardizing. And we haven't seen any material change in our competitive dynamics on that front with CrowdStrike.

And developer ecosystem has been a very popular topic of conversation recently. Auth0 has kind of had that outsized developer mind share for a long time now. So how are you leveraging that mind share that, that product already has in this new agentic world? And kind of walk us through that Auth0 for AI agents use case?

Yes. So one of the missing factors in the industry right now with securing agentic identity is the early lack of standards. And the challenge has been that there hadn't previously been standards that developers could build to that would allow their agents to be deployed in a secure fashion. We saw this happening early. And a year ago, we proposed a new standard called what we call Cross-App Access.

And Cross-App Access is designed to allow agents to support it to integrate with Model Context Protocol for various applications and harnesses in a secure way where those agents can then be managed in a directory and secured. Cross-App Access is an open standard. It's not an Okta standard, and we proposed that from the beginning. It has since been embraced as an extension to the Model Context Protocol. It has been established now as a standard. It is being adopted. We have a lot of exciting announcements about this in a couple of weeks.

But there's broad industry interest in having a standard that can be used to build and secure agents. All of Okta's products support Cross-App Access out of the box. So if customers are using Auth0 for AI Agents to build their agents, those agents are able to be stored and vaulted in any IDP, including Okta's, but not exclusively Okta. And so that gives developers peace of mind in knowing that they're building agents that customers actually can deploy and can deploy in a secure fashion.

So that's a significant differentiator for us there. But we continue to serve the developer community closely. They're having an exciting time right now because their technologies have never been evolving more rapidly than what they're seeing today. And so with things like Fine Grained Authorization, allowing agents specific access to take specific actions with specific applications, they have that in the Auth0 toolkit already.

Yes. And on that point, as AI is creating more code going forward, how do you think about making sure that AI coding agents are using Auth0 and not kind of going off and building something on their own?

I think that's an early space. And I think the evolution of vibe coding and the SaaSpocalypse will be fun for all of us to kind of navigate and see how this goes. But developers who are developing agents that are going to be deployed as autonomous actors in the company are going to need to have those agents built in a way that they can be managed and Cross-App Access is a key to that.

You've made several rounds of kind of go-to-market changes over the last couple of years, but it feels like things have been stable for a little bit now, so...

I'm glad it feels that way.

I hope it feels that way for you too. Could you talk a little bit about what you've learned over the past couple of years and kind of how you've repositioned the sales force for this like new world we're in and stability and everything?

Yes. I think our big learning we talked a lot about 18 months ago. It feels like it was not that long, but also longer. The big learning for us was the products had grown in capability and to the point where there was too much product for any one rep to do a good job with all of them. And also, we really identified that we had 2 distinct buying personas. We had the corporate buyer, the CIO and the CISO, who is predominantly looking for use cases best served by the Okta platform.

And then we have the developer buyer, the developer buyer persona, which was looking to build applications, whether that was B2B SaaS or whether it was an internal build, which had very distinct use cases. And so the big move that we made 18 months ago was to separate our sellers into platform specialists. So the majority of them are either an Okta platform specialist or an Auth0 platform specialist. But really, they're a buyer specialist.

So they're a CIO, CISO, persona specialist or a developer persona specialist. That has been hugely important and hugely impactful. What we've seen since we've rolled out all these changes is people see more success. You've heard us talk about pipe gen. Pipe gen being very, very strong. People are in their accounts. They have continuity in their accounts. They're generating pipeline. They're closing more cross-sell and upsell. So we're seeing our new products start to contribute more because reps are now specialized, they can pull in add-on products.

We just shared in this quarter, our -- what we call our new product portfolio contributed 30% of our bookings. And that's one of the outcomes of having people specialize on a platform and really focus on the cross-sell opportunities for that platform. So that's been very effective for us. And so as we see productivity improve, as we see tenure improve, we're very confident that the go-to-market engine is functioning the way that we designed. And we're now at the point -- one of the questions we got on the call was when do we burst capacity further.

We have announced right now that we feel like we have the right capacity. And one of the reasons we feel that is account continuity has been a contributor to people that have time within their accounts. And when we choose to burst capacity, that causes us to have to recarve territories and reassign a bunch of accounts. And there will come a time when we do that. It's not right now because we're confident in how we're executing. But overall, the motion is working.

Yes. And as you kind of put more and more products out into market and you have kind of these individual specialized sales reps, how do you think about how that impacts when you try to elevate the sales conversation towards the CIO or CISO level?

We -- that's -- every multiproduct tech company has this challenge, right? How do you -- where do you specialize? Where do you overlay? Where do you support with specialized sales? Where do you support specialized presales? How do you design all of that? We have chosen to anchor our sellers on the buyer. So we don't intend to create a new sales function every time we release a new product and just that doesn't scale. But we also recognize that there are some conversations that are very specific and we're having a high volume of [indiscernible] sellers more ability to be effective.

And so, AI right now is one of those examples. So we have our CIO buyers, our CIO sellers, we have our developer sellers, but we support them with a team of specialists in AI conversations. And so that team engages with our sellers on both sides of the business. And we'll scale that team as needed to support it. We expect, as with any new product, eventually, those conversations will become such a normal part of the routine that our primary sellers will require less specialization support, but we can continue to subsidize that as long as we need to.

Yes. And you spoke about the improvements that Okta has made in sales productivity and rep tenure and all these things. What are you kind of looking for in the business when you're making these forward decisions on when to increase sales capacity? And I guess the real underpinning of that question is you guys have stated that you want to accelerate growth. So how do you think about what inputs you need from a sales capacity standpoint to get there?

We have a very granular planning process that looks at that market data informed by what's the vended market, where are people spending money, where is the emerging market? And it's multidimensional. So we look at segments, we look at region, we look at country, we look at different product areas.

And based upon all of that, we have a set of targets that we expect to be contributing. And from that, we understand how much sales capacity we need to hit each of those targets. So we model it on a very scientific level down to what we call the slices. So one marketplace would be governance in Germany, in enterprise as an example. So our sales capacity model comes from that. Where do we see the growth? What capacity do we need to make sure we deliver that growth and then we add that capacity.

Eric, I'll ask the acceleration question in a more macro way. So one of the questions we get from investors is, we're at the very beginning of a very interesting secular shift towards the inference economy, where if you look at agentic deployments in enterprise, it's so early, and you're already seeing a stabilization and potential acceleration in your revenue cadence.

So if I were to zoom out, yes, there's the inputs on the sales capacity side. Okta has seen these really exciting periods of secular growth before. Based on everything you know, why would that not be the case for the next 3 years where you're going to write a secular wave that drives growth to be structurally higher, at least for the medium term?

This feels -- this is a very exciting moment for humanity and for technology and for Okta. And Okta's really had 3 chapters. Our first chapter was the move to cloud computing. And we benefited from that, and we helped catalyze that, right? Okta helped people move to the cloud faster. And that was a significant shift in the industry and something that really catapulted us in our early years. Our middle chapter has been the chapter on identity security and companies realizing that 80% of successful cyber attacks start with compromised identity.

And now our buyer shifted from a CIO trying to get to the cloud to a CISO who is trying to secure their company and had data to make it clear they needed to secure identity to be secure. And so that was kind of our middle chapter. Now we're on this frontier right now where we can see a future where human identity and service account identity continue to be important, but there's this rapidly evolving future where agentic identity becomes massive and both very exciting in our ability to innovate and also scary in the potential threats that it creates and that need to be mitigated.

And we believe Okta has earned the right -- we think we're very well positioned, and we've earned the right to own that market. And so that's -- we're working very hard on it. It's still very early days. We talked in the quarter, we have dozens of transactions for this product that's been GA now for 4 months. But we're very excited by the future, both in the core business, which had a very strong quarter and for this new frontier.

One of the things -- let me ask one more, and then we'll go to Q&A. One of the things that I've observed about your management team in particular, they're very balanced and open about the things that are working and the things that are not. A couple of years ago, Todd talked about wanting to upgrade the quality of R&D internally at the company. And now we think about things like the reference design and the cadence of product innovation that you're putting out. Maybe just reflect on the quality of R&D and the engineering talent that you have and not just the talent, but your ability to execute on product road map.

We -- I think we've -- I'm really proud of the progress that we've made there. I can take no credit for it because that's Todd and Ric. But Todd brought in a new head of all of our technology a year ago, Ric Smith, who's got a storied career at Oracle and Medallia and SentinelOne and -- he's brought a new culture for the R&D organization, and he's brought in new leadership across the R&D organization.

And that's been a very important shift for us in our own identity as who we are as an innovator. And we've seen our product velocity accelerate. You've seen our technology acquisitions, our inorganic growth come in as well as we've expanded our capabilities, things like Permiso is the most recent. That's all part of a culture of accelerating product velocity and getting more value to customers faster. And staying grounded on the value we're bringing to customers has really, really led us. That said, we're not complacent. We can always be better. And so we're always looking at areas where we can bring more value.

One of the areas that we talked about in Q2 is we've just attained IL5 authorization for our FedRAMP business. IL5 is the highest level nonclassified for operating in the federal government. Our pub sec business continues to be an area of strength. The U.S. Federal continues to be an area of strength, and that opens up new doors for us further.

So our innovation is both in the infrastructure and in the features and in the integration of tech tuck-ins. And I feel we've made significant improvement in our velocity. And we -- as I said, we're not complacent. So we're always looking for how we can get even better. But ultimately, we anchor ourselves in the value we're bringing to our customers and are we solving the needs that they need now.

In the core business, I mean, that's primarily what's driving the growth in the future. But, can you talk about the sales force and the changes you made, how that's working. What's driving the core right now? And how sustainable do you feel like...

The question for the webcast is, what's driving the core and how sustainable are those drivers?

Yes. We saw in Q2, it was really the fundamentals across the business. So it was a strong quarter for our workforce business. It was a strong quarter for our customer identity business, which right now, it's about 59%, 41%. The mix there, the balance feels very healthy, and we expect that to continue. It was a strong business for large -- a strong quarter for large enterprise and strong execution for our small business and commercial team.

It was another strong quarter in pub sec. Our partners contributed really well. We saw a great partner contribution. And with increased tenure and increased productivity, like all those things contributed to the health of it. So it's the core business in general has had a really good quarter. And, in addition to that, we have pipe -- our pipeline is at record levels. And so our ability to generate pipeline.

How do you think it's doing so well besides [indiscernible].

I think product capabilities are a big part of it. And I think -- I think that's newer. I think we'll see that be a stronger contributor in the future. But right now, our products -- our Identity Security Cloud has expanded to the point where we have more land use cases. So our governance product is now a land product for us. And so we're able to displace legacy deployments of long-standing on-prem deployments. That opens up new opportunities for us. But it's really -- it's a combination of all the things you just mentioned.

What's the landscape -- the competitive landscape for agentic AI, so early -- you're a big company, the start-ups or other big...

The question is what's the competitive landscape on agentic?

On Agentic Identity. Todd talked about this on the call. And I think he answered it really well. Our biggest competition right now for securing agentic identity is just confusion. It's really hard for an enterprise buyer to know what's real. And our biggest differentiator with that is the fact that 20,000 companies already trust us to manage their human identity and their nonhuman identity. And agentic is a natural hybrid between the latter 2. And so with that, we feel we're very well positioned for that.

Eric, where does something like Agent 365 from Microsoft intersect on the governance point?

We don't see them a lot yet. But obviously, we keep our -- we keep very close. Microsoft -- across all of our use cases, Microsoft is our largest competitor. And for people that are looking for E5 bundles or E7 bundled capabilities and are -- and where the capabilities of the Microsoft stack are adequate, that's a viable competitor for us. But where we typically compete there is on neutrality and on the breadth of product functionality across the Security Fabric, which Microsoft doesn't match today.

The other question that leads nicely from Alex's question is we have been concerned in the '22, '23 time frame that the best part of the cloud cycle was actually behind you for the identity access management business. Is there another push happening from a modernization standpoint that gets you that last 15, 20 points of industry penetration? Or is that sort of relevant to the next phase of the Okta story?

All growth is relevant, and our interest is across the board. Our core business continues to -- we believe there's room left to run. And so, we're continuing to invest in core workforce and core customer identity. And we believe that the most exciting additional frontier, the Horizon 2 frontier for us right now is going to be agentic, which is why we're investing as heavily as we are in bringing a product to market for that space. And we're learning with customers how to evolve that in a way that adds most value.

Any other nuggets to preview for Oktane?

Tune in to Oktane, some good partnership announcements, some great road map announcements on the Identity Security Fabric. And a keynote that, "Don't be surprised, he's going to talk a lot about agentic identity."

Hey, please join me and Callie in thanking Eric for his time.

Thank you.

Hi, everyone. Welcome to Okta's Second Quarter Fiscal 2027 Earnings Webcast. I'm Dave Gennarelli, Senior Vice President of Investor Relations at Okta. Presenting on today's me will be Todd McKinnon, our Chief Executive Officer and Co-Founder; and Brett Tighe, our Chief Financial Officer; Eric Kelleher, our President and Chief Operating Officer, will join the Q&A portion of the meeting. And around the same time that the earnings press release at the wire, we posted supplemental commentary to the IR website.

Today's meeting will include forward-looking statements pursuant to the safe harbor provisions of the Private Securities Litigation Reform Act of 1995, including, but not limited to, statements regarding our financial outlook and market positioning. Forward-looking statements involve known and unknown risks and uncertainties that may cause our actual results, performance or to be materially different from those expressed or implied by the forward-looking statements. Forward-looking statements represent our management's beliefs and assumptions only as of the date made.

Information on factors that could affect our financial results is included in our filings with the SEC from time to time, including the section titled Risk Factors in our previously filed Form 10-K. In addition, during today's meeting, we will discuss non-GAAP financial measures. Though we may not state it explicitly during the meeting, all references to profitability are non-GAAP. These non-GAAP financial measures are in addition to and not a substitute for or superior to measures of manual performance prepared in accordance with GAAP.

A reconciliation between GAAP and non-GAAP financial measures and a discussion of the limitations of using non-GAAP measures versus their closest GAAP equivalents are available in our earnings release. You can also find more detailed information in our supplemental financial materials, which include trended financial statements and key metrics posted on our Investor Relations website.

In today's meeting, we will quote a number of numerical growth changes as we discuss our financial performance. And unless otherwise noted, each such reference represents a year-over-year comparison. And now I'd like to turn the meeting over to Todd McKinnon. Todd?

Thanks, Dave, and thank you, everyone, for joining us this afternoon. Our Q2 financial performance was driven by broad-based strength across our core workforce identity and customer identity platforms. Particular areas of strength were once again with large enterprises, partner engagement and contribution from our newer products. This afternoon, I'll walk through the strength of our core business, the momentum of our portfolio of new products and our investments in product innovation and breadth.

And finally, with AI security remaining top of mind for our customers, I'll share the advancements we're making with AI product development and early customer wins. We were pleased to see an acceleration in annual contract value growth for both workforce identity and customer identity, driven by strong execution and sales productivity.

Additionally, the emerging use of AI by organizations and threat actors alike has further elevated the role identity plays within a company's security posture. Organizations are accelerating their infrastructure modernization time lines to address this heightened threat environment and we're seeing conversations that begin with securing AI broaden into identity modernization initiatives.

Our portfolio of new products are an important and fast-growing component of our solution set. In Q2, new products represented approximately 30% of bookings. Okta Identity Governance was once again the leading contributor. On average, the ACV uplift when any of the new products are included in a deal is about 40%. Product innovation is a primary investment area aimed at accelerating top line growth. Those efforts have already resulted in faster product velocity, including advancements in our AI products and in the public sector. We're excited about the launch of Agent Gateway, which enforces policy at run time and delivers vendor-neutral protection across platforms and clouds, including cloud code, cursor, GitHub CoPilot, Salesforce agent force, in any agent pointed at an MTP endpoint.

The public sector has been one of our best-performing verticals over the past few years. We look to build on this momentum with the general availability of Okta for AI agents core. With this new SKU, Okta became the first independent neutral identity platform to bring AI agent governance to highly regulated environments, including FedRAMP and HIPAA. We're also unlocking more U.S. federal opportunities with the recently earned Impact Level 5 or IL-5, the highest level unclassified cloud authorization for the U.S. Department of Defense.

Achieving IL-5 authorization is a critical milestone as defense organizations aimed to meet the DoD's 2027 Zero Trust mandate. In addition to our organic product innovation, we have a successful track record with our tuck-in acquisition strategy, which helps accelerate our product road map. We just completed the acquisition of Premis, a cloud-native identity security platform that detects and mitigates threats across human, nonhuman and agentic identities in multi-cloud environments. Premiso will be integrated into a unified security offering with our existing ITP and ISPM solutions, the combination strengthens Okta's AI security offerings with enhanced visibility into autonomous agent behaviors and additional runtime controls to ensure secure agentic activity in real time.

While there's been a lot of talk by other companies about identity security for AI, Okta has generally available products that are already delivering real value for our customers. Okta's proven leadership in identity uniquely positions us to secure the AI era. Identity is the primary control plane for securing AI and customers are extending the trusted foundation they already rely on with Okta's neutral, modern enterprise great identity platform to now cover agents.

We continue to build on 3 unique advantages to help our customers navigate the shift distribution, product breadth and neutrality. While adoption remains in its early stages, momentum is growing. Advantages are translating into customer demand reflected in the dozens of AI deals we won in Q2. Our product breadth was a key driver in securing a multimillion dollar Okta for AI agents deal with a Fortune 50 health care company. AI was spreading across their organization, and they couldn't tell where their agents were what those agents were connected to and what they could do.

Okta will give them a single control plane to discover, secure and govern those agents, helping them meet strict HIPAA compliance requirements. Okta will manage their entire identity fabric including agent governance, privileged access and identity security, helping to ensure every human nonhuman and agent identity is managed. Our distribution advantage comes from the reach and trust we built as the identity system of record for more than 20,000 customers.

We saw that work with a global business management consulting firm that was racing to put its own AI agents into production after considering an in-house build, the firm chose Okta for AI agents for its single control plane for human and nonhuman identities, faster deployment and lower cost of ownership.

Okta will carry the agent's identities through every handoff, binding the agents to the original employees delegation with a verifiable record that can satisfy client and regulator requirements. Our neutrality was critical to an Okta for AI agents deal with one of the world's largest asset managers where AI was rolling out faster than their security team could govern thousands of agents for multiple vendors who are running in production, creating risks the organization couldn't consistently see our control. Only Okta's independent and neutral platform could cover their heterogeneous environment from employees and devices to AI agents without vendor lock-in.

Okta will provide visibility across all agents and enforce least privileged access, so every agent gets only what it needs. The common theme across these 3 wins and the other AI deals we've closed is that customers want to move quickly without compromising on security and control. Okta free agents lets them do both by helping them discover, govern and protect every agent. More broadly, the fragmentation of the AI landscape creates significant opportunities for Okta as enterprises deploy agents across models, clouds, applications and infrastructure. They need a neutral identity layer that can secure at all. That's why we partner with industry leaders, including Anthropic, which this quarter named Okta, the first IDA provider supporting enterprise managed off for MCP connectors.

Now generally available, Enterprise Managed off enables IT teams to centrally authorize and govern how Cloud connects to enterprise applications. We also recently expanded our work with AWS, Cisco, OpenAI, Data Rx and Snowflake, alongside more than 25 new cross-app access integrations providing a standardized way to govern how AI agents connect to a growing ecosystem of enterprise applications and resources.

In just a few weeks, we'll talk more about AI security and product innovation at Okta at our annual customer conference. We'll bring the market's leading minds together to lay out the industry blueprint, open standards and new innovations required for building the secure agentic enterprise. In addition to the keynotes and product demos, we will host a Q&A for analysts and investors. Come join us in Las Vegas or online for the AI Security Event of the year.

To wrap things up, we're pleased with the strength and durability of our core workforce and customer identity businesses, and we're enthusiastic about the early success we're having with our AI products as customers recognize our advantage as the leading neutral modern identity platform. It was a strong start to the first half of FY '27, and we look to build on our momentum as we move through this year and beyond. I want to thank the entire Okta team and our loyal customers and partners who put their trust in us every day.

And now here's Brett to cover the financial commentary.

Thanks, Todd, and thank you, everyone, for joining us today. Our strong Q2 financials build on the momentum we've generated over the past several quarters. We continue to focus on operational efficiencies throughout the organization while driving top line growth by investing in product innovation, go-to-market and our partner ecosystem. As a result, we experienced acceleration in many of our top line metrics, while also maintaining very healthy profit and free cash flow margins.

I'll provide insights into our Q2 performance and then move into our outlook for Q3 and FY '27. Q2 was a record bookings quarter for Q4 driven by strong pipeline conversion and deal expansions. We continue to see productivity gains within our go-to-market organization aided by our stable sales force that has low attrition and high AE tenure rates. Strength with large enterprise customers was punctuated by over 20% growth in $1 million-plus ACV customers. We now have over 600 customers with greater than $1 million in ACV. Additional areas of strength included our upsell and cross-sell motion and pipeline build.

The investments we've been making into our partner ecosystem are resulting in positive outcomes for the business. When our partners are involved, our average deal size is bigger and the close rates improve. Channel partners were engaged in all of our top 20 deals in Q2, and our biggest deal of the quarter was partner sourced. At the beginning of this fiscal year, we made the decision to shift more of our professional services business to our GSI partners. This change is reflected in the decrease in Q2 professional services revenue to approximately 1% of total revenue.

We believe this change will lead to greater long-term benefits to fuel top line growth by deepening the relationship with these important partners and increasing our business with large enterprises.

Moving on to our balance sheet and capital allocation. We had another strong quarter of cash flow in Q2, while Q2 is typically our seasonal low for cash flow, it was much better than expected based on strong operating profitability and collections. We ended the quarter with a healthy balance sheet, consisting of approximately $2.3 billion in cash, cash equivalents and short-term investments.

In June, our convertible notes reached maturity, and we settled the remaining principal amount of $350 million in cash. Okta no longer has any convertible debt on the balance sheet. Over the course of Q2, we repurchased and retired approximately 1.5 million shares for a total cost of $125 million. $555 million remains under the $1 billion repurchase program. We continue to regularly evaluate Okta's capital allocation priorities to ensure we're well positioned to deliver sustainable long-term value to our shareholders.

Now let's turn to our business outlook. We continue to take a prudent approach to forward guidance. For the third quarter of FY '27, we expect total revenue growth of 10%, current RPO growth of 11% to 12%; non-GAAP operating margin of 24% to 25%, and free cash flow margin of 21% to 23%. For the full year FY '27, we now expect total revenue growth of 10% to 11%, non-GAAP operating margin of 26% and a free cash flow margin of 28% to 29%.

As a reminder, the FY '27 revenue guidance includes about a 1 point impact related to a strategic decision to shift more of our professional services business to our GSI partners. In addition, the FY '27 free cash flow margin guidance includes about a 1 point impact related to lower interest income due to the stock repurchase program and our cash settlement of the remainder of the 2026 notes.

To wrap things up, we're pleased with the first half of FY '27 and are optimistic about the trends we're seeing in the business. We're invented for growth while remaining disciplined with our cost structure. Our strong core business and growing portfolio of new products provides the foundation to extend Okta's leadership in identity security. We're well positioned to deliver profitable growth for years to come. With that, I'll turn it back to Dave for Q&A. Dave?

Thanks, Brett. There's quite a few hands raised already, and I'll take them in order to the top of the hour. And in the interest of time, please limit yourself to 1 question.

With that, we'll go to Eric Heath at KeyBanc.

Thanks, Dave, and congrats on the strong results, Todd and Brett. Maybe sticking with the deeper Okta for AI agents, Todd, I was curious to hear just how material the entropic partnership you're having is contributing to the go-to-market and kind of the product maturity that you're delivering and Secondarily, maybe for you, Todd or Brett, but just the uplift you're seeing on these deals for Occupy agents and maybe just some sort of perspective on what the ratio is looking like in terms of the agents to humans thus far?

Yes. We're really excited about the quarter. It was an amazing quarter on a lot of fronts. Specifically, 1 of the highlights is that are placed in the ecosystem. Our place in the ecosystem is super important and super strategic. And it's not just me saying that I think it's in all these customer conversations. I'm having many, many customer conversations and flying around meeting these customers that are trying to solve these security challenges in general and particularly around AI agents. And they see us as like the natural naturally well positioned to secure this genetic future.

And so we're going after that on all fronts. Okta free agents is the main product front there. But in short term, we can solve these problems in a lot of different ways. We can help them roll out agents today. We can give them visibility. I think longer term is something we're working on as well.

I think longer term, the entire industry needs to work more -- they need to work better together. The industry right now in security, everyone is coming at the customer saying they have the only answer. They can secure agents, they're going to be the 1 to do it. And the reality is it's going to take us all working together. And so Okta has been working on this. You know on these calls the last 5 or 6 calls we've talked about standards and ecosystem.

And we made a huge step forward in terms of 1 of the main standards we've been working on, which is the standard we've talked about called Cross app access. And so the huge step forward this time is 1 of the biggest AI agent in the world, Cloud, is supporting cross-app access. They released enterprise managed off, which is the first time an AI agent has been compatible with this protocol.

And Okta is the first identity provider to support this protocol. Now it's an open protocol, so we hope every identity technology company supports it. And we hope every other AI agent supports it. And then also, everyone in the resource side of the equation is starting to support it as well. We announced top SaaS vendors are supporting from a resource perspective, this protocol.

So this is one example of many things we're going to be doing in the ecosystem to make this whole world fit together better because that's what customers need. We need to stop everyone confusing the customer by saying one company is going to do it all and start defining how we can all work together to bring concrete solutions to these customers.

In terms of like where the product stack up in the quarter, we had, as I mentioned, the quarter was strong across almost every dimension. Particularly strong was that 30% of the new bookings were from new products. Okta for AI agents inside of that bucket, there were dozens of deals in the quarter, including several million-dollar-plus deals, which is super exciting. But the reality is it's still very early.

We do thousands of transactions every quarter. And as exciting as that is, Okta AI agents, it's still -- it's too small to show up in the numbers right now. But going forward, especially over the next couple of years, we're super optimistic. We think this being a system of record for agents in the enterprise and being the system of record for agent identity. In the fullness of time, it could be the biggest category of cyber. That's how bullish we are on it. It's going to take us some time to get there, but I think we're off to a good start.

Yes, I would just add, Eric, like Todd said, we had close to $1 million deals in the quarter, and we've got dozens of customers. But what I said last time around the average deal size for AI deals being bigger than the average deal size for the rest of Acton. That still remains the case. But like Todd said, it is very early on. We are still very -- it's a very nascent opportunity for us. And so looking forward to continuing to execute against that opportunity going forward.

We'll take the next question from Jefferies.

This is Brent Darling on for Joe Gallo. Results were super impressive, and it was great to see those early AI security ones. I was wanted to touch a little bit more on just competitive dynamics. Could you help us understand that seen right now maybe what are bake-offs looking like? Is competition more the Wild West or are you seeing more existing customers going to you without Bigo? Just anything on competitive dynamics would be helpful.

Two interesting trends there. First is that the biggest competitor is confusion. We're competing against confusion. So our solution has to be clarity. And customers are confused because there's so much excitement and so much opportunity in AI. It's the natural tendency of every vendor to say what we are doing and what we've done in the past is critical day. We have the answer. We have the one answer. And I think that confuses the customer because they have 17 vendor meetings, and every vendor tells them they have the right answer.

So one of the things we're very focused on is getting close to the customers and learning from them and pouring that quickly back into our product road map. And that process not only enables us to build a better product, a product that will deliver value to their customer and cut through the hype and also that those experts on the ground help clarify in the customers' mind what needs to be done. And the simple fact is that is that it's a big trend. AI security is going to take a lot of different vendors working together. And we don't have all the answers, but what we do know is that there are some no-regrets investments.

We know that every customer is going to have to figure out where their agents are, they're coming from all over the place. They're going to have to figure out what they can connect to and they're going to have to figure out what they can do. And no matter what happens at the model layer, the platform layer, the app layer or if applications build their own agents or they get disrupted with agents, what the companies build themselves, what they that's all going to unfold what models the best is an open source model. Is it a frontier model, and that's all going to unfold as it will over the next several years. But the no regrets decision is you have to have this foundation of where are my agents what can they connect to and what can they do?

And this no regress decision is what's leading to this momentum. It's leading to these dozens of deals, these million dollar deals. And they look at us as they say, "Hey, most of the use cases for agents now, they're working on behalf of a user. They're automating workflows, helping users. And so it's a very natural place for the identity provider across the enterprise to step in there and answer these questions.

One thing I would add to that is in addition to the genic competition and the confusion, and Todd really well articulated the conversations we're having with customers right now on that front. In addition to that, the overall core business also had a very strong quarter in the category. And as we talked about our workforce strength and customer identity strength, and the competitive dynamics there, our differentiators remain the same as they've been.

We have broad distribution with over 20,000 companies that already trust Okta to secure identity for their humans to secure identity for their service accounts. And having an adjacent conversation about how we are now also going to be able to secure identity for their agents as they're deployed is a natural engine for us, and it's how we can bring clarity to that overall conversation. So that distribution helps.

Our neutrality has always been a key differentiator for us as well. You hear us talk here about how we have over 8,000 integrations. Todd talked earlier about the expanse of partnerships we have in the AI space and with the frontier models and technology providers, the platform providers and scalers. Our customers know that their stack is going to evolve, and they know that they're going to need to work with all of these technologies because they're advancing so rapidly. And Okta is the provider that allows them to work with all of that. And so the standards that Todd mentioned, the distribution we have, the neutrality that we have, all positions us very well to be able to win this next opportunity.

Next from John DiFucci, Guggenheim.

Thanks, Dave. Todd and Brett and Eric, listen, subscription revenue growth has really stabilized over the last 4 quarters. And our calculations of new ACV, which is going to drive future revenue growth, it looks really strong for this quarter against the toughest comp of the year. I guess at the same time, you've talked a lot about AI and securing AI agents and per our work. That message is really resonating well with customers and partners in the field. But you also say it's really early.

And by the way, we hear that in the field, too. I guess I was just curious, so I think we're all curious based on your expertise and experience, when do you think this is going to turn into meaningful revenue? I know you said you had some deals that -- and it sounds like it's starting. But do you think we're going to have to wait until something really unfortunate happens in the world or will corporate customers get ahead of this before something like that happens?

John, the corner was really, really a successful quarter. The bookings in the quarter, you mentioned ACV. The bookings in the quarter were a record all-time for Q2 -- they're also, by the way, a record all-time for Q1 and Q3. So all-time record outside of Q4. And even if we had a competition for Q4, it would almost be on the podium, not quite, but close to be on the podium for Q4. So yes, we're very excited about the momentum. And like you said, the materiality of the AI contribution, the business is $3 billion roughly in revenue and you saw the CRPO growth. It's a big number. And so we're optimistic about moving the needle on that. And we think we're on the right path.

And one interesting thing is that I'm not -- the conversations I have, it's kind of like -- it's almost like an infrastructure foundational conversation. It's not necessarily like, oh, a breach happened and now we're reacting. So I think that's good for what you said because I don't want a big breach to like knock this all down the industry. I want customers to proactively put these no-regrets investments in place and then have the right foundation to be successful.

So I'm optimistic that kind of we're on the right track there in terms of like clarifying the message for customers, having the right product in the market. And by the way, one of the things that's true and helping cut through the confusion is that we have a GA product. It's been generally available for a couple of months now. That's pretty rare actually. If you go around and ask all the vendors, is your product generally available, you get no a lot of the times or it's an acquisition that's kind of still running as an acquisition. So we have a generally available product. We've shipped 24 significant enhancements to that product in the last 2 months.

We're moving fast. We're innovating. We're listening to customers. And we're trying as hard as we can to make sure we turn this into solid top line acceleration across the board as soon as possible.

So I guess maybe just real quick, Dave, on the same topic, Todd. Like what percentage of your customers are you having these conversations with, with AI security? Is it just about all of them? Is it half of them? Because that -- just trying to understand timing.

A little bit? We have one of the things -- the organization in place, like I mentioned, we have a dedicated expert team in the field, helping customers have these conversations. And as many smart, motivated people as we put in that team to have these conversations, we fill up their calendar. And they're working 6 days a week, 12 hours a day, and we keep adding people and keep filling up the conversations, and that's leading to this record pipeline we have.

Last year, we talked about -- or last quarter, we talked about record pipe. The pipe is even bigger. -- and if there's more pipeline. Now the question is how fast it will convert, right? And we don't have 4 years of history on conversion. So when we think about the future, there's obviously some degree of being prudent about how fast that's going to convert. But the pipeline is there.

Now it's up to us to take this generally available product and convert it as fast as possible.

And John, this product went GA on April 30, right? So 90 days ago. So it's relatively new. But to your question around how many customers, a stat that might be valuable for you, and we put this I think with our post commentary today. Recent surveys we run across our customers, 81% of the CES that we talk to, are aware right now that they are exposed with agents deployed in their enterprises where they do not yet have an adequate security platform in place.

So a very high percentage of our customers know that they have the need. And as Todd mentioned, our teams are working aggressively to schedule as many customer conversations as we can to make it really clear how we can help. So this has been -- we're very pleased with what we've seen.

Next, we'll go to Matt Hedberg at RBC.

Congrats from me as well. I think 1 of the most encouraging elements here is the 200 basis points of CRPO acceleration, and it doesn't feel like it's even being driven by AI yet, I think we all see the pipeline. So I guess, are you seeing -- because you sort of force rank the most important elements for that CRPO acceleration. And I guess, as a follow-up to that, are you seeing deal cycles accelerate.

Todd, you just mentioned the pipe is as big as ever. With AI-driven concerns, even if it's not AI specific products, are you seeing faster deal cycles in this environment?

I would rank them as follows. The first #1 thing is large enterprise. You see the 22% growth in $1 million-plus customers. It's a large enterprise that has been for several quarters is a very important part of this the performance of the business.

The second thing I would say is that we're the only identity vendor with this broad range of products. You see that 30% of bookings and new product introductions that's a little bit of AI governance, privilege, I deity threat protection. We have this broad platform of products and you're seeing that really shine. So this message of -- you can buy from a one-stop shop for identity. I was having a conversation with a large Fortune 25 customer yesterday. And they have 200 identity vendors, 200. They're already paying a significant amount of money for the part of their identity we're doing. But that -- I mean, 200, they could replace -- they could save tens of millions of dollars by standardizing on us across the board. And we're the only identity vendor that can do that.

Everyone else has a silo, whether it's just access management or it's really tied to their own stack or it's very privileged or governance. We're the only one that has that breadth of product. So that's very important. And then the third thing, which is really exciting is that these conversations about AI and our ability to help clarify how they can secure AI and how this ecosystem can fit together to help them secure. It's catalyzing change conversations that are resulting in deals for other products.

So you might go in and have an AI conversation and they're like, "You know what, we've been talking about upgrading our governance legacy product for 6 years. We just have to do that. Oh, and by the way, we should probably think about customer identity. And so you're starting to see that happen. So that's not an AI deal per se but it's kind of like a large enterprise. It has a bunch of vendors that want to take out, and it's coming to the company that seems smart about AI and has a GA product and has real success there. And by the way, it has a large platform. It's a powerful combination.

Next up, we'll go to Josh Tilton at Wolfe Research.

Thank you, Dave. Hedberg sort of stole my questions, so I'm just going to maybe ask it, but a little bit more directly. Are you seeing strength in our business because it is accelerating the pace of legacy migrations said differently, our customers coming up to you and saying, like, I might not need the II security product today, but I definitely need to replace my core product because I know the legacy product I have is definitely not going to support my hand strategy whenever I get there.

And then maybe the second part to that question is just 15% short-term bookings growth year-to-date, it sounds like most of that is not from AI. But -- how do we think about the durability of that growth profile when AI really starts to layer into the model.

For the first part of your question, we absolutely believe that the exposure our customers are feeling to agents proliferating in their organizations and not yet being able to secure them is starting a lot of conversations. And those conversations, as Todd just mentioned, can expand into other areas of the portfolio.

So your question around legacy migrations, are people looking to the future and ensuring they have the identity security fabric, the platform that can solve all those use cases, that's absolutely part of the conversations that we're seeing evolve with customers. In that sense, the agent conversation is bringing a more acute awareness to perhaps their lack of readiness and their need to find an identity -- a secure identity partner that they can have confidence is going to solve for their challenges, both today and in their road map in the future.

So that's absolutely something that we think is contributing. But overall, as you look at the core business, and Todd and Brett mentioned this, we saw strength up market and the $1 million in a $100,000-plus cohort. We saw strength down market. We saw strength in public sector. Our largest deal of the quarter was a public sector deal. So we continue to have confidence in the durable strength of the core business as we're also starting to convert the pipe we talked about in Q1 and continue to build in Q2 for these new AI products that have come out.

And as mentioned, with multiple million dollar wins just in this first quarter of availability.

I'll give you a very specific example. I was a couple of weeks ago, I was in Pennsylvania, talking to a large customer of Okta, it's a retailer and the conversation was about a big M&A they were doing. And the company they bought had a legacy identity provider. And the conversation I had was all about AI, AI agents, Okta for AI agents, how we answer these 3 questions. And that conversation in the POC and the sales cycle that's just starting there, absolutely helped us win the consolidation business to consolidate the acquired company all on Okta because it wasn't on Okta, that legacy identity.

And of course, when you kind of bring a big company and like that, everyone wants to evaluate which vendor should we use? Is this better for this? And that AI conversation catalyzes the whole thing to be, hey, Okta knows where they're going. They're the leaders here. Let's just get rid of all that old stuff and standardize on Okta. So that's a very concrete example of this phenomenon. You just outlined in the abstract but it's for sure happening day to day.

Next up, we'll go to Rudy Kessinger at D.A. Davidson.

Congrats on the strong results here. especially given it doesn't really sound like AI is really kicking in yet. Brett, questions for you. Your CRP outperformance -- this was the largest since fiscal Q4 of '25, which was obviously a very, very strong quarter. The outperformance in Q1 and Q2 were stronger than Q1 and Q2, the last 2 years. And so does your Q3 CRPO guidance -- does it assume that any of this level of stronger execution and conversion rates, except that you've seen in Q1 and Q2? Does that Q3 guide us to many of that continues or does it still have the same kind of prudent assumptions at our Q1 and Q2?

Yes. I mean you hit the nail on the ready, Q1 and Q2 this year have been quite strong in Q2, I talked about record non-Q4 bookings, record non-Q4 bookings quarter for us. It was really good. So when we think about the guidance going forward, we're applying the same guidance philosophy. We have for several quarters now. We've talked about getting closer to the pin. So clearly, it's pretty quick. It's quite simple, right. We had a great quarter in Q2, great quarter in Q1. Q3, we're applying that same guidance philosophy. So no change in terms of many of the variables you just mentioned.

Next up, we'll go to Shrenik Kothari at Baird.

Yes. Congrats on the great results. Just to follow up on an earlier competitive question and Todd and Eric, you touched upon it a bit. We are increasingly hearing the fear, the CSOs who are exploring a genic identity also become a very of these AR first private vendors like OSS getting acquired. Further creating that integration road map uncertainty. Are you seeing that also capitalize more in terms of pipeline towards scale sort of independent platform by you guys?

And just on a related note, importantly, since you and Eric mentioned the phrase, no regret investment a couple of times with the simplified agent pricing that you launched an oral packaging also designed to remove this procurement friction and more scalable as deployment scale. Is that also pulling a lot of these evaluations towards other areas, as you've said, and customers wanting this no-regret durable economically scalable, playing across humans and agents. I know it's a couple of questions, but yes.

Yes. I think there are about 3 in there. Let me apart the first 1 and then Todd and Brett can comment on the second. We absolutely believe that the uncertainty in the market right now around that customers are faced with. In fact, I was with a customer event last week abroad and we had an opportunity to talk to a half dozen CSOs on their plans for how they're solving both core workforce and customer identity and also agentic identity. And they share the concern that you just articulated, which is the various players in the space and the venture fund companies are moving very rapidly, and it's difficult for them to have confidence in predicting what the future is going to be.

And one of the reasons that they come to Okta and talk to Okta is specifically because we are a proven company. We've been solving this problem for 17 years for over 20,000 customers, and we've earned the trust of those customers and the partners that we work with to solve these problems. And so they have confidence in our ability to work with them for the long term as well, not just for the short term.

In addition to that, this also again highlights the importance of our neutrality as they know the various stack components that they're using, the various frontier models they're using all of those technologies are evolving and leapfrogging each other regularly. And they know that a bet with Okta is a bet that's going to carry them with continuity through whatever happens elsewhere in the technology landscape.

So that's absolutely one of the primary reasons our customers have confidence that Okta a smart long-term bet. One of the interesting things is that a lot of these little companies are pivots so they started off as like trying to detect service accounts or trying to do service account discovery or agent discovery, and they've more recently pivoted in this comprehensive vision like we have of discovery, where are my agents, what can they connect to, what can they do?

And so a lot of their products end-to-end are quite immature. They might be strong in one area, but end-to-end, and that's pretty frustrating for these CISOs and CIOs I talk to because they don't want -- they're hasn't enough about buying a small vendor because they're worried about getting it acquired or having it go away or run out of money. But then they sure don't want to have to buy 5 of them to get the solution that we have.

And so generally available product, comprehensive vision, iterating quickly. That really resonates, like I talk to CIOs and sees us that are amazed, we're iterating faster than startups, and they're amazed by that. And yes, it's tough to go wrong when you have a trusted vendor that's already in front of all your people in your infrastructure and trusted security vendor, it's a good position to be in.

Let's go to Steven Koenig Macquarie.

Okay. Todd, a question for you. maybe pivoting from these -- talking about these small upstarts, turn into AI identity, and looking at some of the majors that are all claiming to have like control towers or control planes or what have you. You got Microsoft sales force ServiceNow. Maybe just can you give us some perspective about like to what extent do those products overlap and compete with your Okta for AI agents? Or to what extent are they useful even if you have Okta if you're, say, a sales force customer? Maybe just some perspective on are you really competing with those products? And how are you differentiated from them?

Yes. I think Microsoft is copying us, which I think they have been for 15 years. So I think they're copying what we're doing and they see the value of an agent registry. And I think the challenge for them is going to be -- it's really hard to be neutral, and it's really hard to make an agent registry that works as well for Amazon and Google and OpenAI, anthropic as it does for Azure and Microsoft. But I think they have a similar vision. And it looks at least from their blogs, I don't know if they have a real product yet, but at least when their blast seems like they are copying us.

And then I think ServiceNow and Salesforce are like every vendor, I think they're coming at the problem from their perspective. ServiceNow is coming at it from a very like an asset management workflow management perspective. And we found it very valuable to work with them because we can add a lot of value in that environment. We can really help them sever the connections, the trusted connections between agents and the rest of the ecosystem, we're at that level of detail. We have the tokens, we have the protocols so that can really help the control tower from service.

Now actually come to fruition with a control -- a kill switch that can actually kill the connections. That's been a really valuable partnership. Salesforce similar. It's like they're coming from more of the service and support and platform layer to some degree, but guess what, people log in to age in force through Okta and we can help people securely connect agent force to everything else in the ecosystem because the more agent forced agents are connected to data across the ecosystem, the better, and we can help with that.

So Everyone's kind of sticking in their own lane. And lucky for us, our lane is perfect for this world. Our lane is people to technology and then technology to multiple different vendors with multiple different plays in the technology space. We're very good at that. We've existed in that middle for 17.5 years. And it's a muscle we have in the company. It's a culture we have in the company, and it's really paying off.

Let's go to Trevor Rambo at BTIG.

Great. Yes. Trevor -- so maybe looking at the rest of the portfolio, it seems like OIG is going more and more mature every quarter from a technology standpoint. And while the AI side of the business is very exciting and doing well. Feels like OIG is contributing more to the business right now.

So maybe if we take a step back, can you give us a sense of how that product performed in Q2? And are you starting to see more net new lands there? Or it's still mostly just expansion from parts?

The whole new product portfolio was super strong. LIG is the biggest bucket in there. So you're right, it's the biggest bucket. The whole bucket outperformed, like I mentioned, 30% of bookings performance was across the board. -- everything -- I think every product in there beat our plan internally, which is great.

And more and more, you're seeing the -- I think when you think about OIG and Privileged Access Management and access management, the most important thing is that we're starting to see them be sold as a sweet more because we're transforming the identity industry. We're going from an identity industry that was very stovepiped. It was OIG was separate than access management with separate than customer or separate than privileged was separate then. So that world is going away.

And we're the only vendor that has everything under 1 vendor, and we can -- it's all integrated. It works great. It's not a bunch of stuff that was bought and slammed together. I mean it's been a product that there's some acquisitions in there, but the vast majority of that is organically developed and which is better for customers. Customers want a real platform that works together, not a platform that was bought and renamed and slammed together and sold from one salesperson. And that's really resonating.

So yes, that part of the business, like I've said before in a couple of answers, that's what's driving the -- that's what drove the overperformance is the new products and the core business, workforce and customer, both accelerated since the ACV growth accelerated since we last released it in Q4. So that's kind of the secret sauce there.

And you can't -- and you have to build that up over years, right? We've been working on OIG and privilege and for 6 years, 6.5 years, and it just takes time. You can't slap stuff together and have a leading product, leading products take time. As much as I like to rename it and have it be something cool and new -- you can't do it. It takes time.

Next, we'll hear from Jonathan Ho at William Blair.

Congratulations on the strong quarter.

What do you think? Do you think we should rename everything?

It'd be pretty interesting. You usually have Okta in front of everything.

It used to be a Azure Active Directory and then they renamed it to Entra.

Yes. It sounds exactly like Opto. Why did they do that? Good question. Good question. With the Formeso acquisition, can you help us understand how this sort of expands your product set? And what is post authentication behavioral, what does that opportunity look like, particularly in the ad-driven world?

We see an interesting phenomenon in the customer base. 80% of breaches are identity-based attacks. And -- but when you look at our customer base, relatively small percentage have the most advanced identity threat protection product. Identity Threat Protection, we've thought while Jonathan, it's like very, very important and very unique. And by the way, very differentiated. None of the other IDPs have this. It's not only evaluate session risk at the time of login but also post login continuously monitors it, looks for risk signals not only from Okta, but risk signals from the ecosystem from CrowdStrike and Palo Alto Networks and takes those all together and can shut down session after log in.

So it's any company that is running identity without this technology, it's -- you're at risk and you're behind, but not everyone's upgraded to it. So I guess this is a plug. Everyone should upgrade to this thing. And if it's not, you don't get it from Okta, force your vendor to build it and so you can get it or you could just buy from us.

Now Permiso, the way to think about Permiso, it's like the next generation of that. So instead of 90 native risk detections, they have 400 native risk detections. So it's a much richer and deeper set of correlative processes and machine learning that can really look at a session deeply across many vectors and many variables and detect risk. And of course, that's going to pay off in just person log in. It's going to pay off in just an agent login. They also have a very strong threat research team that bring to the company.

And it's most business is probably the most exciting thing it's the perfect size for Okta to take and add to our products and extend our products. For what's going to be a big area for us is this advanced identity threat protection over time. Yes, we're really lucky to have them on board, and it's been great to get to know them. We just closed. I think the acquisition actually officially closed only today. So we've been working with them preliminarily, but now it's going to be great to dig it with them and built some great together.

I asked that GPT and it said to call the product, Okta Nexus there you go. There you go.

Jon, I would just add, this is another one of these tech tuck-in M&As that we've done over the last several years. you've seen them be very successful in a variety of products. So we've got a good track record here, and we think this is going to be another nice addition to the portfolio of products like Todd just said, it's pretty exciting for us. So looking forward to selling a bunch of this in the future.

Yun Suk Kim at Luke.

First, congrats on the quarter. Just given how quickly genetic AI adoption is happening out there, how are you incorporating the number of AI agents in your deal because that number will probably grow really fast. Are those numbers staged over a period of time.

So you would expect renewals to happen pretty quickly as customers probably will probably underestimate what they need initially?

I'll tell you an interesting story. We were -- in terms of -- you mentioned that the -- you said that the number of agents is growing fast. So this is -- I want to be super concrete. I think it's the most helpful for everyone on the call when I'm super concrete about stuff. So we were talking to a company that ended up being a nice Okta for AI agent steel in the quarter.

And when the evaluation started, we ran our technology and we detected 50 instances of a cloud agent in the environment and they were thinking about what they wanted to do, and then we came back a few weeks and there was 1,500 cloud agents in the environment. So it's like 52 weeks, 1,500. So it's -- these customers are -- it's really tangible. The risk that they're seeing and the way this is coming into their organization.

So this is catalyzing some of these deals, this on-rush of agents. To your question about licensing and pricing and renewals and so forth, everyone is figuring out how to price this stuff. Now I mentioned A lot of companies don't have a GA product, so they can get up here and talk about like what they might do and this and that and the other and talk about all the stuff. We have to have a pricing model because we're in the market. And so our pricing model is per user.

So if you want to buy Okta free AI agents, it's an uplift to your per user charge. The product works across different use cases. So it can be log in for the user and the agent. It could be passing the agent credential across the whole chain of command. It can be governing the agent, but the pricing is per user, an extension of the per user price. Now the first thing everyone says is, well, that's crazy. Seats are going away and you've got to charge per agent. That all might be true.

But the way customers are using agents now and the way they want to buy is per user. And one of our advantages is we're super close to the customers. And as I'm sure this is for sure going to evolve. And as we come up with ways that work for the customer and work for Okta, how to package it and price it differently, we'll iterate quickly and give them what they want. But for now, they like the predictability. They like the investments, matches the business value they see. It's helping these deals move faster. So I think that's the winning formula for now.

Is there any consumption limit on those per-user pricing?

Yes. It's an interesting question, like we haven't in our products, we haven't done that much, but we're starting to add that stuff because particularly, I don't know if you guys saw the announcement we did about supporting agent SSO in our base addition across the board as we did it on Monday. Agents are going to log in way more than people. So in that product, we actually have a cap of agent SSO that we're actually not going to enforce right away, but we're putting the framework and the scaffolding in there to have a consumption-based pricing eventually because it's very likely that with agents proliferating and how they behave, that the usage is going to be quite high.

Let's go to Kingsley Crane at Canaccord.

Great. I want to ask on Siem. So Todd, you mentioned you're talking to customers, enterprises all the time in developer time. You won the hearts and minds of developers, but products is somewhat changing with AI. Yes, well, of course, yes. So they may be amenable to whatever vendor has suggested as an example. So like how important is it for you to be the default Super important those kinds of environments and what can you do?

Yes. We have like the last 6 months, we have tons of focus on this. You have to show up in the LLM, you have to show up. ensure surging for tools. And so you have to be at the top of the leaderboard there. So we're really focused on making that happen. Yes, it's really important.

Let's go to Mark Cash at Raymond James.

Yes, on for adding today. I don't know if this is for Todd or Brett, but last quarter, I mentioned our AI contribution was significant to the guide maybe they're a little bit expected to get big. 90 days later, you pity understand that AI is still relatively small part your sale in the quarter. And maybe can you talk about how much the raise in the outlook was due to AI.

Still immaterial, still very small early innings. But like we've talked about here, we're excited about the long-term opportunities. So for FY '27, we don't think it's going to be material, but and beyond, we do -- if things keep going the way that they're going, then we do think that there is a real possibility for this to be material for the business in the long run.

Great. We've got about 5 minutes left. Let's try to get to the rest of the questions. We'll go to Junaid at Truist.

Great. Thanks, Dave. Todd, you've noted identity governance being a leading contributor in your new products bucket, and it's matured into a land product. But you've talked about PAM remaining earlier in its life cycle and more of a cross-sell product. with AI agents requiring capabilities like token vaulting, credential management and just-in-time privilege access. Are you seeing agenetic workloads materially increase the strategic importance of PAM and could Agentic identity be the catalyst that drives PAM from this cross-sell motion towards a much.

I think this association between PAM and genic is maybe was overemphasized. I think there was this mindset 3 years ago that agents needed privileged access, and so PAM was going to be the right place to do agents. I think it's wrong. I think it's wrong. I think agents do need privilege actions for sure. but it needs to start on a much broader base. PAM is too narrow. PAM was -- had a very small number of users in super lockdown environments.

Agents -- the whole dream of agents is that they're there for everyone. So it doesn't make sense to start your agent journey and figuring out where the agents are and what they can do and what they connect. It makes no sense to start it from the most lockdown things sit next to the Oracle database on a sun server.

It makes sense to start it from the broad IDP, whether it's customers or whether it's employees and then start from there and say, "Hey, how can I take this token that was generated for this user and pass it through with traceability and accountability all the way through the chain, it needs to go through. That's what we're seeing in the industry. It's a much better place to start, which is I think a lot of these vendors are seeing that, and that's why it's hard for them to get their products out and that's why the products are more narrowly adopted, and I think you're seeing us be really well positioned, which is why I think if you look at what Microsoft is doing or it's companies with the access to more users that are at an advantage there versus narrow security vendors that were more boxed in.

Okay. Next up is Joe Vandrick at Scotiabank.

You've got Joe Vandrick here on for Patrick Colville. So Todd, we did see the release of agent SSO a couple of days ago, which is now included in the core SSO products. So we were wondering if this is a way for Okta to give your existing customers a taste of that AI agent solution and then what will eventually cause a customer to upgrade into purchasing that broader Opta for AI agents product?

You described it exactly right. It's spreading the kind of the core, core foundation of Okta for AI agents, which is the the directory entry that tracks the identity of an agent that puts that everywhere, ubiquitous. And so what the upsell is, is like policy, how you want to do governance, how you want to have a software MCP Gateway, a virtual MCP server, there's 5 or 6 or 7 really key upsells. But in signs the core entry and the dreary.

There's another more important strategic reason to do it, and that's because we're on this mission to standardize AI security, in particular, this agent single sign-on across the industry. And we're doing that on many fronts. The biggest front right now is this cross app access protocol. And we mentioned a huge step forward where Anthoropic is supporting cross-app access in what they call enterprise managed authorization. And we're the only identity provider that speaks this language and they're seeing it solve a customer problem in their customer base or they're putting it in cloud, and we're trying to get every agent company to follow their lead very important.

Now imagine going to every app, Salesforce, Slack, Asana, all these companies, hundreds and hundreds of these success companies and tell them, "Hey, we want you to support this new protocol for aged single sign-on. The first question is, how many customers can do it. And now the answer is 20,000. So that's the reason to do it to spread the standard and really catalyze this whole industry with customers benefiting the most.

Okay. We're getting to what looks to be our last question from UBS.

This is Jack on for Roger Boyd. Brett and Todd, I wanted to understand a little bit on the Fed side as we head into 3Q here. You mentioned you had a good 1Q on the pub sec side and where there was a nice customer identity solution win in the prepared remarks with the DoD here. So -- now as we enter 3Q with the IL-5 certification, the DoD 0 trust mandate Brett, would love to understand just what's baked into 3Q guidance relative to last year, the Federal.

Public sector overall is really important, and I'm pumped up about it. We've done so much work. I've I was recently in Maryland and Virginia, talking to top government people. And like everyone else, they're really, really excited freaked out about AI. And we have super relevant offerings for them, both on just talk about legacy identity. I mean they have the most legacy of the legacy identity and also an understanding of how critical it is.

So we're a U.S. federal DoD, public sector, in general, is a tremendous opportunity for us. It's only -- it's less than 10% of our business right now. So we have tons of success, but -- or tons of momentum, but tons of room to run there, which is quite impressive. The other interesting thing in U.S. federal, specifically, I don't know if it's from other companies. But the first part of this year was kind of a mess. It was dose, knew they're going to have a job, every spending is being scrutinized. It's starting to normalize now. It's starting to get back to, hey, they know they have projects to do. It's like more of the same environment, they have to invest, they have to make long-term decisions.

I think that's benefiting us, like we mentioned, it's the largest deal in Q3 was in U.S. Federal. And if you look at the next couple of quarters for us, there's tons of big opportunities out there we're working hard to close.

Okay. Great. Well, apologies, we weren't able to get to everybody. Before you go, just let you know that in addition to the on-site and virtual bus tours coming through this quarter. We've, of course, got our Octane Conference the week of September 21, we'll be at the Goldman Sachs Conference in San Francisco on September 9, the Wolfe Conference in San Francisco on September 10. And the Piper Sandler growth comes in Nashville on September 15 and the JPMorgan software form in Napa on October 2. So we hope to see you at one of those events. Thanks.

Thanks, everyone.

Dave. So Ely, Harish, Dave, thanks for being here, Janice as well. I very much appreciate you all being here to hopefully get a technical session for people. And go into a topic that I think is very interesting. So Ely, the Chief Product Officer; Harish, SVP and GM of AI Security. And then we all know Dave and Janice on the IR side of things. So I'm going to throw it over to Dave to hit the safe harbor, and then Ely and Harish have some prepared slides and topics to hit. So I'll throw it over to you, Dave.

Great. Thanks, Eric, and thanks for hosting us today. Really appreciate it. And just Janice is going to throw the safe harbor up. You guys are all familiar with the safe harbor language, just a reminder of that. And just to remind you that today's conversation is really about the technology. We're not going to be taking financially related questions today.

So with that, I'll throw it over to Ely.

Thanks so much. And once again, my name is Ely Kahn, Chief Product Officer here at Okta. I've been here about almost 6 months, but been in cybersecurity my whole career, first inside the U.S. government, U.S. intelligence community, doing cybersecurity, then a startup called Squirl that was acquired by AWS, spent 4.5 years there building products. Most recently before Okta, I was Chief Product Officer of SentinelOne. And yes, excited to be here to talk a bit about our vision, our road map and our strategy.

Okay. So just as a refresher, I thought I'd start with a reminder about what is the Okta platform. And really over the last 3 to 4 years, we've been building out a complete identity platform that covers all the major use cases that you need to protect your identities, preauthorization, at authorization and then post authorization.

So maybe first starting with the preauthorization focused products. We have our identity security posture management products. This will be an acquisition that we did 3 years ago, a company called Spara. This gives us the ability to discover misconfigurations, identity-related misconfigurations in hundreds of your SaaS and other types of applications. So generally speaking, we're looking for overprivileged or misprivilege administrators or other identities, including administrators that haven't been -- accounts that have been used in a period of time or other examples of misconfigurations that increase your blast radius.

Next up, we have our identity governance products. This has become one of the fastest-growing products in our portfolio. And it just recently has crossed over 2,000 customers, which puts us on par now in terms of customer adoption with other IGA products like SailPoint. And so this gives us the ability to ensure that those users that you've onboarded to Okta have lease privilege, allows us to access requests and access certifications to ensure that those users continue to have the right amount of privileges over time. This is also complemented with Okta Privileged Access, which I think about as the flip side of the coin to our IGA products. With Okta Identity Governance, you're provisioning access to sort of standard sorts of applications. And with our Okta Privilege Access, you're provisioning access to high risk, high trust resources, things like databases or Amazon EC2 instances.

When we do that, we can do session recording. We can also plug into on-prem resources, ensure that even if you're using a long-lived credential or API access key, we then short-term federal tokens to ensure that even if there is a compromise, the blast radius is small.

Next up, at authorization time, we have a couple of products. Of course, our flagship [indiscernible] product around access management, which provides secure cross-platforms fishing resistance authentication. And then we sync that up with Okta device access so that you can use the same login processes both into your device and into your applications.

And then lastly, Identity threat protection. This is our Identity threat detection response product. This gives us real-time signals that can be used to look for misbehaviors and anomalies during the session. And the real power here is these aren't producing just another set of alerts. We can tie this into other products so that we see users above a certain risk threshold. We can do things like universal logout or step up authentication to really contain that risk within that session. Now these products, they're not siloed. The power here is that they're part of a unified identity security fabric and they allow us to cover a broad set of users and devices, including employees, partners, contractors. It can plug into both modern SaaS applications and legacy on-prem infrastructure. And now most recently, we've extended the platform to support AI agents as a first-class identity in the platform. I'll get more into that, and Harish is going to go real deep into that.

In terms of that Unified Identity Security Fabric, let me give you just one example. So let's say, as part of our ISPM, our Identity Security Posture Management product, we've identified that a particular administrator is not being used. That account is not being used. We can use that information then kick off an access certification in our IGA product to officially recertify whether that user needs that administrator account? And if not, revoke. So we have a bunch of out-of-the-box integrations across our products. We also have a low-code, no-code solution called Okta Workflows that lets you stitch together any other type of custom integration between the products that you might want.

And then lastly, and certainly not least important is our uptime story. So we're at 4 9s as our official SLA. This year, we're actually at 100% uptime. And over the last 3 years, this means that we've had roughly 69 minutes of downtime. And compare that to Microsoft that's had over 2,000 minutes of report uptime. This is a key differentiator for our platform and one of the reasons customers love us.

Next up. Okay. So a big move for Okta has been that we've been really pushing towards this identity platformization story. And we've been working with some of our largest most complex customers on this story where they're making a big bet, and they want to take a very complex set of legacy solutions and simplify. So this is a customer that we've been working with for the last year. We'll complete this platformization story this year. And they're very typical of a large Fortune 2000 company. In this case, they've used a legacy solution for identity management. I think they are using SailPoint here. And they're using another vendor for their access management, in this case, Ping and then another vendor for privileged access management, in this case, CyberArk. And they have specialized teams for each of these vendor solutions. And -- it's not only a cost issue for them, but it's a complexity issue. And that complexity also translates to security, meaning the more complex your stack is, the more likely there are gaps in which adversaries can compromise. And so they wanted to solidify down into a single vendor, Okta, not only to reduce costs, not only to reduce complexity, but also to increase their overall security posture. And we're well on the way to this. We'll finish this complete replatformization this year, and the customer will be seeing significant -- they're estimating somewhere around 40% economies of scope gain in the form of cost savings.

All right. So maybe backing out now in terms of our 2026 product strategy. And this closely relates to that last slide there in terms of the platformization play that we're making. So we have 5 main elements to our product strategy. These are not the only things that we're working on, but these are the top 5 most important things that we're putting our efforts around. The first one is our Okta for AI agent story and ensuring that we have a first-class set of experiences across all of our products to support AI agents and to protect the identities of AI agents. I'll get more into that in just a second.

Next up, second and third, maturing our IGA and PAM solutions to be world class so that they can [indiscernible] replace legacy vendors like a sell point or like a CyberArk and even just win head-to-head in greenfield competitions where the customer may not even be using us for access management. And we're well on our way to that as well this year, and we have a number of wins where that happens. Identity Security Fabric. I'll actually talk about Identity Security Fabric a little more detail in the next slide through the lens of Okta for AI agents, and how all of our products are coming together to provide that unified Identity Security Fabric for the AI agent use case. And then lastly, Okta, like a number of companies is all in on AI native product development. And we are aggressively using coding agents across all of our product teams and seeing 50% gains in product life cycle development which means we're shipping products and features faster to our customers while still maintaining the really high bar around uptime, resiliency and security.

All right. Let's jump into the AI agent story here quickly. I'm not going to go through this in detail, but I saw there were some questions and the pre reads about what type of agents does Okta protect. This is a common question, and we actually built out an AI agent taxonomy to help with this. At a high level, the 4 major categories of agents as we think about them are embedded agents. These are things like your Zoom companion agents. Now embedded agents are the one type of agent that we do not try to protect. These agents are essentially hard-coded into SaaS applications. They don't expose APIs, so we can't really manage them.

Next up, stand-alone SaaS agents. So this would be something like a Devin or a [indiscernible]. So this is an AI agent that exists as a SaaS agent, we can onboard these types of agents into our platform to govern and protect them, agents associated with automation platforms, where the agent built into a boom or a torque or times. That's also a type of agent that we're working to protect. Homegrown agents as well. So if you built out a fully custom agent using plan chain or an agent builder platform like Amazon Bedrock, those are also agents to support.

The other dimensions of agents that we oftentimes look at and have some unique characteristics in terms of how we protect them is the delegation pattern. So is this simply a human prompting agent? Or is there a set of subagents that are spawning. And then how long is that agent exists? Is it a very short-term ephemeral agent or a more lasting one. These are all considerations that we've gone through as we built out our Okta for AI agents platform. Let me talk about that quickly in the next slide.

Okay. So this is a busy slide here, but let me talk through it real quickly, and then Harish is going to, I think, touch on some of the details here in more depth. So when we talk about our Okta for AI agent story, at the top level, we think about it through 3 simple questions. Where are my agents, what can they connect to you and then ultimately, what can they do? And so what you're seeing here is our reference architecture. Most of these things are in place, not all of them yet, but these are all the things that we're building towards really over the next -- either we have now or building over the next 6 to 12 months. And it starts with discovering your agents. And so we built integrations with a number of different tools to directly import agents from those tools. This could be things like Amazon Bedrock or our sales force control tower. Any of those types of agents we can directly embed them into our registry through a direct import by calling their APIs. Also if you build a homegrown agent, you can use our SDK to then import that agent directly into our registry. But we also have the ability to discover unknown agents. And the first capability that we launched earlier this year is using our browser extension to discover all of claims between users and agentic tooling and then giving the users a workflow or the administrators the workflow to register those unknown agents in our registry.

Once they're in our registry, then they can be registered with a human owner or they can be registered as a fully autonomous agents. You can apply additional meta data to them to ensure they have a full identity and they can come under user entitlement reviews. So is this a user that should have access to that agent and doing access requests and access certifications. Also, does this agent have the right access to resources and able to do access certifications over time on that. From there, once that agent is registered in our agent registry with a first-class identity, you can start giving it permissions in the form of scopes. So these are considered core screened permissions. And so you might give it sort of provisions to Slack or to GitHub or to Jira in terms of being able to read versus right, versus update, et cetera. And from there -- and this is really important because you want to give those agents the least amount of privilege possible, but enough privilege to fulfill their goals and objectives.

Now we've also shown some -- we put some blocks on this recently, how you can apply fine grain access controls to agents. So not only can you apply these core [indiscernible] grant scopes. But if you also want to give it a more fine-grain access policy like say, "Hey, this agent can only view not sensitive data or they can't write sensitive data." Those would be additional fine grain access controls. This is where we bring in some of our of 0 capabilities in its FGA products to combine with our Okta for AI agents solution.

All right. So once you've defined the access policies, then it can start accessing resources can access resources through our MCP servers, authorization servers, our SaaS authorization servers. We also have a new agent to agent capability and ultimately, we are able to monitor these capabilities, produce logs that can be shipped to a SIM. And perhaps most importantly, if things start going wrong, if that agent starts misbehaving, acting suspiciously, we also give you a kill switch that allows you to revoke tokens. -- and ensure that those agents cannot continue accessing resources in a malicious way. So like I said, there's a mix here of things that we've delivered and things that we're working on. But this is really the complete story that we're working towards and will ultimately help customers not only identify their agents but ensure those agents operate with lease privilege and have a small blast radius if they're compromised.

All right. So with that, I'll hand over the mic to Harish.

Yes. Yes. Thank you so much, Ely. And I see some questions trickling in. So I will keep this brief, so we can make sure everyone's questions going to address because that is what is most critical.

For introduction, I am Harish Peri. I run the AI business at Okta. So I spent majority of my time with our customers in the field, making sure our everything to do with our AI security story resonates and that we're growing this business. So that is why I'm here. So some of the content I have is more around our positioning our capabilities and how we tell the story to the broader market, which I think will also be very helpful to this audience.

So if you go to the next slide, the goal that we have for every one of our customers and folks that are not our customers that are embarking on their agentic journey is every company will become an agentic enterprise in the next year, 1.5 years. What that means is many pieces of their product development, portions of how their employees interact with their tools, how they connect with their end customers, how they connect with our partners, suppliers; all those are going to become agentified. There's going to be agents in the flow there. Our appeal to all of them is you could be anagenic enterprise or you could be a secure agentic enterprise, which means you have a centralized security offering to be able to control the identity and access and authorization of everything those agents are connecting to. So that's the broader kind of hook that we have for the market, which is to say, how do you not just be an agentic enterprise, but how do you do it in a way that's secure? Because the difference between building agents and rolling them out into production is security and scalability concerns. So that's really how we're starting our position.

We go to the next slide, please. And since we've embarked on this journey, we've engaged with hundreds and hundreds of customers. I mean we're talking CISOs, CIOs across some of the largest companies in the world. And the thing is the tongue in cheek way of putting this is the cat is out of the bag, everyone has the agents they're rolling out. The question is, where does the cat go, right? And that gets into something -- some of what Ely was touching on, which is discovery is a really huge issue. But the common themes are, we are -- everyone in our company is going to become a developer at some point. How do I know that they're developing within the right guard rails. How do I ensure that all of my Claude code or my open AI or my cursors or all those development assistants are actually being control in the right way and how do I ensure that they don't execute judgment and delete something important overnight with no human oversight, right? So this problem is very real. It is very top of mind for pretty much every one of our customers and every new company that we're talking to. So it is very much in the zygus, the topic of securing the agents.

If you go to the next slide, please.. Now I want to I want to spend a little bit of time on maybe some broader topics, which is -- I actually spend a ton of my time educating our customers about just the nature of the overall problem. And one of the topics I get pulled into a lot is, "Well, I have an AI gateway. I have guardrails around my LLMs." And to that, my response is that is necessary, but not sufficient. When you think about what it takes to secure agents, you really have to think about models, which is, of course, the brain behind the agent that is making decisions in response to a prompt and deciding what tools it can be accessed. But there's a second part of it, which is how do I actually secure the identity and the authorization of what that agent is actually accessing. And that's a lot of what Ely was touching on. And so model is one piece, identity is another piece and the third piece is the data itself. So for those agents that are accessing your data at large scale, either for [indiscernible] generation or as part of what their -- just their daily operations also getting down to a level of is this agent authorized to access this data at this moment in time given all environmental signals is a third big piece. So we like to think about model identity and data and where Okta starting right now is this notion of how do we control the identity, the authorization and the access of every one of these enterprise agents that are running around your organization. So this is an important concept because people now get hung up on the model side, but that's only 1 out of 3 things after a bigger problem.

So if you go to the next slide, please. And this is just an example. This is a completely hypothetical example, but this is -- as we see agents being rolled out, this is kind of a calling pattern. One of the fundamental issues you're dealing with when it comes to agents is unpredictability. This idea that in response to a given prompt. So this is a hypothetical finance agent that's going to help your procurement team with contract or PO approvals. In response to the same prompt, there's going to be tools, there's going to be memory, there's going to be LLM that are accessed and it might caught with different responses in each situation. And I bring up this slide because it's very critical for people to understand that this is actually -- you're not dealing with a deterministic piece of software. You're fundamentally dealing with something that at scale will get you a lot of efficiencies, but has a level of nondeterministic to it that does require a level of human control, which is where dent comes in. So again, very powerful but also has a very nondeterministic aspect to how they work.

If you go to the next piece. And there's a builder, so we can just kind of click through this. In the interest of time, we'll pause here. So when you take an average large enterprise. Once you think of their agentic roll out at scale and you think about their users, you think about their [indiscernible] functions, you think about the various applications and resources that this agent is accessing. When you start to do the math and you multiply through the various MCP servers, the various other agents that single agents are calling. When you think about the external services that they're accessing. This is a little bit of a large number, but you could -- when you do the math, you're talking on the order of billions of access decisions that have to happen per day to get a truly agentic enterprise to work because, again, when you multiply the users, the applications, the resources, the agents, the agentic agent chain, the complexity increases tremendously. And each one of these access arrows is a potential risk factor because what you're dealing with is not just a deterministic access claim, but it's an agent that is making a decision at that moment in time and could be exercising adjustment.

So that's why the notion of the attack surface becomes even more complicated when you're thinking about agents. And as you multiply that across the entire estate of technology that your average large company has, the complexity is quite mind-boggling and requires centralized control.

So if we go to the next slide. There's another thing that you would need to think about here, which is -- so I touched on nondeterminism. There's also a notion of autonomy. Agents are going to take actions on their own, right? And traditional Zero Trust was not made for a world where you have these autonomous actors that are nondeterministic. So you really need to think about how do you control that.

The other important piece, which there was a question in the chat about differentiation is this notion of delegation chain. So every regulator, every auditor out there is going to come knocking on a company's door to say, can you prove to me that a specific resource was accessed by a user, was accessed by an agent or was accessed by an agent acting on behalf of the user through a multi-agent access chain. And being able to centralize and track the delegation chain is the other important concern that breaks kind of Zero Trust as we know it today, which was made for humans really.

And then finally, there are more and more models emerging ephemeral latents, which is agents that spin up other agents that are short-lived that might execute a specific task. It's an entirely new paradigm of technology and software, and we really need to think about Zero Trust holistically and why we are so bullish on this is, the one common thread across all of this is that context is what was the intent of the original user that gave a prompt to an agent that then either spun up an ephemeral agent or call the subagent and then access to resource. It's the authorization and the identity that's the core of all that to be able to say we can actually control the chain of what is happening. So I don't know there's a little bit of zoomed out, but it does require the industry at large to rethink what Zero Trust is all about and identity and authorization end up being at the core of all of this.

So if you go to the next piece. So again, when we think about what Okta for agents is, is really the direction that we're heading in and actually not even heading in. The GA capabilities that we have in market today are really providing this notion of a control plane for every enterprise agent in your organization accessing every resource on behalf of any user in the organization. Centralizing that, governing every call, binding into user context, ensuring that access is provided just in time with lease privilege and then creating an immutable layered audit trail, so you know exactly what resources access, by who, on behalf of who at what moment in time is the core of the platform that we're -- the capabilities we're adding on top of the Identity Security Fabric that Ely touched on earlier. So it's very powerful stuff. It's in market today.

And in the interest of time, I'll go to the next slide, which is which is actually this. So just I want to leave you with one -- maybe something a little provocative. So I said maybe a minute ago that I spent a lot of my time educating our customers. There's a lot of its that are popping up that we end up doing myth busting around, things like, "Oh, I have an MCP gateway. I think that's good enough." And the answer is that's good enough if you're not interested in full user agent to resource chain mapping and auditing, which is something that every company is going to need. So that's some education there. The other thing is "Oh, I use Bedrock Agent Core or a copilot studio today. And that has some identity stuff built in." But think about where Okta is today. We are an independent neutral central broker of human identity to every resource in your ecosystem. That's exactly what we're doing with agents. Separating the identity from the core agentic platforms actually gives you not only a level of control, but also a layered defense and depth strategy that reduces your single points of failure. So that's the other big myth that we spend a lot of time on.

And the third is, well, shouldn't -- this is just acting on behalf of a human. So why do I care just going to carry the humans credentials? Sort of, but not really. When you have agents that really are helping your organization, these are multiplayer agents to use a term from anthropic or these are enterprise agents that are accessing multiple resources. They do need their own independent identity that can be intersected with the permissions of the invoking user to then create the perfect permission chain. So this is just an example of some of the education we're doing. The market is moving very fast. We are right at the forefront of it. We're spending a lot of time educating our customers, but there's tremendous, tremendous momentum on that front. So I'll pause there, actually, I think we can we can call it a day on the slides because I want to make sure we have time for questions. And I don't know, Eric, if we hand it back over to you.

Yes. Thanks, Harish and Ely, for the comprehensive both review. So a lot of things I want to dig into. Maybe Ely, just coming back to where you started or one of the things you started with was the 4 different buckets of agents. Today, can you just high level give us like set the ground or just lay the framework for us in terms of what's the maturity of AI agents today in organizations that you're talking to? And secondarily, what are the most like prevalent types of agents that you're seeing.

Yes. One quick AI joke here. So we had a large financial services customer in our customer executive briefing center a month ago, and I was asking them how many production agents they had. And they responded with over 2,000. And when we were first doing our pricing analysis for Okta for AI agents, we assume there will be somewhere around 20 production agents in a large customer. And so we -- that was done back in October. And you can see like how fast the market is moving just from that one customer anecdote.

But in reality, the most prevalent type of AI agents that's out there, our customers right now are coding agents. So there's certainly a lot of -- and probably more sophisticated customers are building their own agents. But almost every organization we walk into has a Claude code or a codec or another coding agents. And so these are top of mind. And with those agents, it's not really about the number of agents because typically, you can think about that as like one agent for the entire development team. But it's the breadth of usage that's happening and the types of tools that those coding agents are able to connect to, and it's those developer to agent tool interactions that needs to be protected.

Right. Okay. And then, Harish, one of the things that you said that was interesting is I think you called out that discovery is the biggest issue that customers are facing right now. So can you just help us understand what Okta does today from a discovery of agent's perspective. And really, I mean, I think there's a lot of emerging vendors out there that we are familiar with and see you getting a lot of momentum just -- what are they doing that's unique and novel, and like how differentiated is this capability that either you or the emerging vendors have when it comes to discovering agents?

Yes. I think -- so more broadly, Discovery is -- it's not enough to say I run something and I have a dashboard that shows me a list of 10,000 agents. Like that's fine, but then what do you do. And so where Okta is coming in is to say, where most likely are the most critical agents is going to be living and how can we find them the fastest. So that's what Ely touched on, there are known platforms like AWS, Copilot Studio, Azure foundry, agent force ServiceNow. There's a whole host of them that they're already partners of ours, and we could easily detect agents in their agentic run times and then import them doctors. That's one kind of discovery.

And the point I want to hit on is Discovery is half the equation. You also want to register those agents in a central identity directory and give them their own identities such that all the tool calls then get routed through Okta. That's the real value there is Discovery is part of it, but giving them identity and then controlling the flow of access is the other part of it. So there's the no platforms. There's browser plug-in capabilities for a variety of browsers because one of the -- one type of agent is also sort of the SaaS agent that you're accessing through the browser. The other one are local endpoint. And so the good news is we already have deep partnerships with the major cyber providers to be able to tap into their APIs and detect agents that might be running on the machine. But again, I want to emphasize that finding them and showing them in a dashboard is 50% of the equation. The other part of it is, say, now what? And that's the part where the full connectivity with Okta matters is to say, "Okay, now I'm going to give you a unique identity and ensure that there's no MCP calls, there's no tool calls that this agent is making that is not authorized and vetted and brokered by Okta." It's really becoming in line and the flow is the end goal that we have here.

Yes. From a product capability perspective, is Okta on equal footing with some of the emerging vendors out there when it comes to discovery? Or do you think this is an area for development, if you will.

Yes. I mean I'll let Ely take that as he's deep in that on a day-to-day basis.

Yes. So right now, what Okta supports is one mode of discovery, which is browser-based discovery. This is for unknown agents. We also have those direct imports for known agents. But for unknown agents, we support browser-based discovery. You can see in our strategy slide, we'll be adding additional forms of discovery. I do think that there are some really unique aspects of the Okta platform that will allow us to differentiate something that folks forget is that Okta is on every endpoint. Every Okta customer has an endpoint agent called Okta Verify, and this is a very powerful capability that can give us broad visibility into what is running on that endpoint. This is -- I mentioned Okta Device Access. It's how we discover what's running on that device to ensure that you have a secure locking experience. So we'll continue expanding our discovery capabilities, including using the full power of the Okta platform to do so.

All right. Staying on the governance topic for 1 more question and maybe switch at 1 time. But on the governance side of things, I think 1 of the maybe things that 1 might theorize in terms of who has an advantage when it comes to the identity stack is -- the IGA vendors, the traditional ones have a lot of understanding of all the entitlements, MediConnect or all these applications, and they have deep visibility into all those different fine-grain nuances that you need to know in terms of establishing access in the application. So what's your perspective on the IGA vendors having that unique advantage? And I understand that Okta has IGA, so it's a little bit of your in both camps, but what's your perspective on that being a strategic advantage or moat?

I mean my take is that we caught up with the legacy IGA vendors, in it's proven out through our customer adoption. With over 2,000 customers using Okta IGA, we have a very powerful IGA product, where some of the biggest customers in the world are looking at us from an IGA first perspective. So I think this is an area where we've invested significantly. We're going to continue to invest to close some of the long tail of feature gaps. But I'm very happy with where we're at on the IGA side. And yes, it's a critical part of our overall products to secure AI agents, but I'd say it's one component. And frankly, it's a really important component, but it's not the most important one. The most important one is ensuring that the AI agents themselves have a least privileged identity that has a small blast radius. And the IGA piece can help you ensure that, that blast radius stays small over time, but we see it as an add-on capability, not the core central capability you are offering.

Yes. What we hear from customers across the board is they're looking for a system of action versus like a system of record where you can keep track of rules and things. They need a system that can enforce the most critical thing, which is, is this agent allowed to execute this specific action on behalf of this user at this moment in time based on a variety of signals, some of them being entitlements in the government system but there are other signals like network signals and endpoint signals and other risk signals and that ability to do dynamic real-time authorization, managing the entire chain of custody is the true ask that the requirement that the entire market is converging on. And IGA is a portion of it, but it's not the all and all. And then that's where the rent piece comes in is because we have a platform that can stitch together a user agent resource and that entire chain.

Right. Maybe moving to the authentication runtime side of things. So we talked about the gateway, and I think there's been lots of mentioned the gateways from all sorts of vendors, et cetera. But can you just double-click on what you guys mean by agent gateway or access gateway, if you want to delineate the language there? And what role that is playing because we did this in our piece, but Okta's role from the authentication side of thing is like, okay, we need to narrowly define the scope of what the user and the agent can do. And if we do that right, the simple side of you might say, okay, it's all established in the token itself when they go to authenticate. But I think you and the market are saying, "No, you need the agent gateway on top of that." So just help us understand what the agent gateway is adding incrementally that's not defined in the agent's token.

Yes. So the agent gateway does a couple of things. One, you can think about it as a single endpoint or access point for a variety of agentic tools. So if you're using Claude code or Codex, the agent gateway is the access point for how those tools interconnect into our platform. And then the gateway itself, once those agented tools are connected to the platform, serves as a policy enforcement point. And so it's where we enforce that those agents are accessing the tools that they're authorized to access. It's also where we provide the inventory of tools that those agents can access. So onboarding various MCP servers, each of those MCP servers have a variety of tools, will allow folks to mix and match those tools into lease privilege virtual MCP servers that then those agents could access, and then it serves as the real-time policy in portion points to ensure that they're only accessing things that they're authorized to.

Can you just be more specific, Ely and Harish, with like real-time enforcement because, I mean, to be can, I think we see that in a lot of like product announcements and press releases, but just be a little bit more specific, if you could, on like what real-time policy enforcement is. Because to me, that seems like it is where the market is really trying to focus its efforts on when it comes to AI agents.

Yes. I'll start, Harish, feel free to jump in.

Yes, go ahead.

Yes. Yes. And so each agent is granted a set of scopes as part of its access policy. And the agents themselves can either be acting on behalf of the user or fully autonomously, we support both of those modes. If they're acting fully autonomous, they're acting on behalf of the user, they actually get the intersection of the humans permissions and the permissions granted to the agents. But ultimately, you need a policy enforcement point to decide whether that agent which is making a request to access certain tools should be granted that request. And that enforcement point is the agent gateway. So it's making the decision there or it's enforcing the decision whether that agent should get access to the tools based on the permissions of the agents and the permissions of the user if it's acting on behalf of the user. And that happens in the agent gateway. But Harish, anything else to add on that?

Yes. Maybe I'll give a different way of thinking about it, which is -- so put coding assistance side because their access patterns are, I need to talk to Jira and to talk to my S3 buckets. I need to talk to Artifactory like those. But we have many large customers that are building internal agents to help their employees with like a finance use case. And so the downstream systems of that agent needs to touch are the in some cases, the MRP inventory, very complex legacy systems that all may or may not have APIs and may or may not support cross-opexes, for example.

So the flow would be somebody in finance, they have the interface of the agent, they say, can you approve this PO like the hypothetical example I gave. The LLM behind the agent will say, "Okay, I need to first go check inventory, then I need to go make an update in SAP, then I have to go talk to [indiscernible] system then I have to send an e-mail," whatever it may be. There's different levels of scoping, meaning what level of access does this agent have to work day or to SAP. That's the first piece that Okta is controlling. But then there might be custom authorization rules that also need to be enforced depending on attributes in the users' profile, depending on other attributes that might be custom. Chaining all those together and making a real-time decision based on all that available context, that's the core of run time, the authorization that we're getting at. So the gateway brings all that together in a highly performing way, right? And so we can support some of this with our finger and authorization capabilities today, and we're pushing towards this notion of intent driven, which is what is the other theme that you might be hearing in the market today, which is let's make sure this agent doesn't go off on its own and try to execute an action that was not matched with the intent of the original user. So keeping track of that entire context at every transaction and enforcing that in a highly performed way based on things like [indiscernible], but then also custom authorization rules. That's the holy grail of this runtime capability that we're pushing towards. So having a central authorization point is critical, and that's a big part of what the gateway does.

So maybe kind of jump into the punchline, Harish and Ely, how do you see this market evolving in terms of where the point of differentiation is going to be an identity stack, whether it's the registry, the IDP, the discovery, the gateway, the token path like the actual issue of the tokens. So just how do you think about it, give us a framework of where you think the unique differentiated aspect is going to be in this market?

Yes. I think help double down on something Harish was just talking about. So and this goes to -- also touches on some of the other questions that came in. In terms of what is fundamentally different about AI agent identity versus human identity. And there's a number of like technical differences, tactical differences, like agent to agent connectivity required a whole new type of standard because there wasn't a good corollary on the human side. But I think one of the most interesting difference is where -- and Okta is making big investment here is the fact that we're going to have to fundamentally rethink identity management and access management with agents. Because the traditional process of defining static permissions and then every quarter reviewing those permissions to see if there's still a least privilege, that's eventually going to break down because AI agents are becoming more and more powerful and more and more autonomous. And that means that it's going to become harder and harder for an administrator to predefine all the permissions that an AI agent might need upfront. And instead, we're going to need to move to a world where the permissions are granted to agents in a more dynamic, just-in-time basis. And they'd be granted if the tool [indiscernible] that's the agents attempting to do is not anomalous, does not drift too far from the original agent intent, does not contradict any guardrails that you want to ensure are adhered to. And so it's this mode of moving towards just-in-time dynamic permissions for AI agents that I think will become the biggest differentiator, and that's a big place where Okta is focusing.

I wanted to have maybe a little bit less of a technical question, maybe a little bit more market questions. But one thing I've noticed and picked up over the last several months is you guys seem to have a tight relationship with Anthropic when it comes to their identity announcements and with workload inaction and I forgot the other things. But it seems like you have a tight integration. So can you just elaborate on what you do or don't have when it comes to partnerships, whether on product or go to market with these Frontier AI labs?

Yes. Yes, go ahead, Harish.

Yes. So more broadly, we have been and always will be an ecosystem player. The power of Okta is very much to do with how we can, one, help drive the right industry standard and then help bring all the ecosystem players along with us and implement that standard. And so anthropic is one example. But yes, we have -- there's been a lot of kind of public announcements around how they're supporting cross-app access. What that does is, one, that helps drive the adoption of the standard call cross-app access, which reduces things like continuous OOP consent fatigue and also creates a central way to control permissions. So it helps drive entropic adoption. It helps drive adoption, helps bring the industry standard up. But I would look at -- that's one example of many. We have -- to ultimately to make an enterprise a secure agentic enterprise. We have to make sure that our ecosystem integrations are tight with every player in that blueprint that Ely was showing. Enthropic and their frontier models are one of them. We have integrations with the cybersecurity vendors like Cross-track and Zscaler. We have integrations with the Agentic platforms where agents are created. We need to think about integrations with other gateways that customers may have. And so it's the same story that we've had for human identities. We need to plug into all the players in pace to bring it to life. Same thing for agents. It's just a new set of players.

One thing I wanted to ask you and get your perspective on is, I always tell clients, investors that like identity is probably the most fragmented market in cybersecurity. There's a whole slew of start-up vendors out there and point solution vendors out there and -- maybe help frame for us if an organization spends $100 on identity today for humans, I don't know, Okta maybe can get 20% wallet share of that. Maybe it's 40% with IGA and PAM. And then we have agents. We can decide if that $100 for agents is equal to humans, and it's another $100, but do you agree with the premise that like your share of wallet opportunity is relatively small today in the grand scheme identity stack. And with agents, could that 20% of wallet share be 80% of wallet share, 90% of wallet share. Does that question makes sense? And does it resonate at all?

It's being a bit. My take is that this is not the same wallet share and that the wallet is expanding. Meaning, as customers more quickly adopt AI, they are also adding budgets to protect those AI agents, and that's not coming from the same budgets that they are using to protect their other identities. So I think what we're tapping into with our customer base is new budget associated with AI adoption. And so it's not the same denominator. Now putting that aside, the stack for protecting AI agents looks very similar at the 30,000-foot view as the stack for protecting human identities. I mean we have ISPM, we have ITDR, we have SSO. And so we're building out that full stack to protect AI agents in the identities of them. So I would say that our wallet share for human identities is very similar to our expected wallet share for AI agents. But it's a different wallet.

The simple part of the question is just the identity market is highly fragmented today. Does it look much more consolidated when it comes to securing AI agents? [indiscernible] kind of the punchline.

There is a consol -- yes. So the -- and it goes back to what Ely was saying, which is companies are taking a more centralized approach for rolling out AI. So like they're at a -- this is a decision being made at the CEO level, at the Board level to say, okay, we're going to spend X billion dollars on an agent transforming our company with AI. Given that agents live in the application layer and identity authorization is a center of all of it. Two things. We do believe that we have a shot to go and take a slice of that entire spend, which is a more elevated conversation. And the evidence there is fruit. I have conversations every day now with CSOs and CIOs were coming and saying, "We need you to draw the reference architecture of how everything comes together." So we are in the middle of the ecosystem now and the evidence is showing that. So it's a different wallet. It's a bigger wallet and the mechanics are going to be different. It's going to be -- it's a slice of the entire thing because it's essentially a security blanket around your entire Agentic investment.

Yes. And Eric, I think to answer your question, is it fragmented or more fragmented or less fragment. I mean, it is a brand-new technology area -- so there is a plethora of startups in this space, which makes it feel very noisy. But I think similar to what we saw with like cloud security vendors, there will be a consolidation because ultimately -- and we hear this from our customers, I don't want that -- our customers don't want different stacks to manage their human identities and their Agentic identities. They want one unified solution where they can manage all of their identity issues together. So I think there will continue to be consolidation and platformization in this area?

All right. Well, Ely, Harish, David, thank you so much. Great place to leave it at the top of the hour here. Wish I could spend a lot more time with you guys, but it's been a pleasure of tracking what Okta has been doing in terms of leading and shape in this market for a and so it's been great to see. So I appreciate it. Appreciate the time. Thank you, everybody, for tuning and listening, and here to help if anybody needs it.

Thank you.

All right. Thank you all.

Thanks, everyone.

Thanks, everyone, for joining us. With me today is Eric Kelleher. He's the COO and President of Okta. So Eric, thank you again for joining us.

Great to be here.

I will maybe kick it off. There's so much going on, and there's a lot of questions I was putting together, but I really wanted to start from your perspective, there's so much has changed with AI. So if you think about the identity market year-to-date, what surprised you the most in terms of like the changes that you're seeing?

I think for year-to-date, so if you go back six months ago, prior to the beginning of this year, our conversations with customers were fairly broad. And Okta has grown over the years from providing basic access management to also providing workforce and customer identity.

And then also adding in identity governance, privileged access management and new security products like identity threat protection, identity security posture management and developer products with the Auth0 platform. Our conversations prior had really been about the breadth of all of those use cases for customers. And we would talk about the Identity Security Fabric.

And that fabric was the combination of all those capabilities to help customers solve identity and secure identity for all their use cases across all their products and all their technologies. What surprised us this year, to your question, is while all of that is still true, and we continue to innovate and develop for the Identity Security Fabric and all those use cases, the only thing customers want to talk about today is how to protect themselves from the AI problem they know they have within their companies. Their employees are using AI.

They're turning on agents internally. 91% of them report that they know they have agents that are live in production and 22-ish percent of them believe they have them secured properly. And so that's what people want to talk about. They have an exposure today, and they need to contain it. And so I guess what surprises us about that is just how acute that transition has been, and it has really dominated our conversations.

And as Todd mentioned in the call last week, it's really been a driver of pipeline for our new products. We brought Auth0 for AI agents to market in November and Okta for AI agents came out last month on April 30. And so those products have really been built in consultation with customers talking to us over the past six months about how specifically they need us to help them secure AI.

So maybe we'll stick with the AI theme. And to your point, it was AI agents GA for a couple of weeks, on the call last week that it's the largest, I guess, pipeline build for a net new products. So in terms of like how you go to market, like what are your reps doing to convert pipeline to actual dollars? And we'll talk about the monetization, but just curious more so like what does that pipeline look like? And how are your sales reps converting that?

Yes. And it's interesting because the space is so new, and it's evolving so rapidly and the underlying technologies are evolving. So a few months back, Gemini was the predominant platform and conversation and Anthropic would leapfrog it and now ChatGPT 5.5 Cyber is out.

And our customers are living in this world where they're not sure which technology is going to ultimately land. And so they need the flexibility to be able to protect against all of them. So our conversations have largely been talking to them about the importance of neutrality and the importance of having a broad solution that can allow for the rapid evolution of these platform technologies.

And one of the challenges we have addressed and continue to address with this particular pipeline is it's a newer motion. It's adjacent to conversations we've had about securing human identity and securing nonhuman identity and service accounts. But agents are newer conversations. So for our sellers, they don't have depth years of experience positioning these products.

They are new products that are just coming out. And so one of the things we've done to help them is we've stood up a tiger team of resources from a sales standpoint, a product standpoint and engineering standpoint with forward deployed engineers that are working actively with early customers and early enterprise customers to help us both design and build the products and convert pipeline.

So that team has been really driving our strategy and our engagement and our specific feature prioritization over the past many months, which is why we're confident that the product that we brought to market is going to fit the need because it was really designed collaboratively with customers.

The -- I know it's a small sample set, but on the call, a lot of investors kind of focused on the commentary where I think you said if there's -- I think it was more so on the call back, which was a customer comes in for an upsell, they buy IGA, if they were to attach AI, that component would be larger than the upsell.

I know it's a small sample size, but can you just provide some color on what you meant like when you say larger in size, I assume absolute dollars, but to the magnitude, and again, smaller sample set, but can you touch on that a little bit?

Yes. What Brett talked about in the call is that it's about 40% larger, significant. And it is -- it really is a testament to the value that customers place on the exposure that they're working to mitigate. And as every successful cyberattack earns a headline, customers get more and more aware of the fact that they have an exposure that they need to mitigate against.

And so that helps them understand they need to control for all the use cases. The challenge that customers have to -- enterprises have today is that they can't control their employees. Employees are able to spin up an agent and give it access to their e-mail and access to their calendar and access to their Google Drive, which contains things that they don't even know they have access to.

And so as that becomes more prominent and more acute and as there's more issues in the press, companies don't want to be tomorrow's headline. And so they know they need to invest to put themselves -- to increase their security posture and put them in a position where they can protect against having their own agents compromised or over-permissioned or impersonated. And so that's really what we're seeing and the level of investment we're seeing is that's where customers see the biggest exposure to.

And then if you think about Auth0 and then Okta, where -- it sounds like Okta is having more success early on with AI, just given the deployment because it's more internal versus Auth0 side. But maybe walk through those dynamics. And does that shift over time? How do we...

I don't -- I wouldn't agree with the premise of that question. We're having good success with Auth0 for AI agents as well. We're -- you might not have heard us talk about it as much on the call because that is -- it's an upstream product.

So Auth0 for AI agents is a tool for developers that helps them develop agents that can be secured. And it allows for example, for fine grained authorization, where you validate -- when an agent takes action, you validate not only that it is who it says it is, but also that it has the specific permissions to do the thing it's trying to do.

That capability is hugely important. Token vaulting, which is included there is hugely important. So -- we've had -- we continue to have good success with that product as well. From an enterprise security exposure standpoint, the more acute challenge our customers are facing right now is that they don't know 3 things.

And we call answering these 3 things, the blueprint for the Secure Agentic enterprise, where they don't know where their agents are. They don't know what they can connect to and they don't know what they're authorized to do. And so Okta for AI Agents is a platform that addresses those 3 areas, helping with the problem of discovery, how we find what agents are live in production for your company and then helping with the problem of connection and ensuring that you know what those agents are able to connect to and then helping with the problem of authorization and knowing what they're authorized to do.

I guess the question I have is, and I want to ask within identities, if you think of privileged access, which you have, IGA, which you have further along the maturity curve and think about your core, it's more important or a bigger priority for customers in terms of securing AI.

In terms of securing AI, so governance continues to be a very strong contributor for us, and we don't see that slowing down. In addition -- and governance plays a role in securing AI as well. And for example, one of the use cases there is just-in-time provisioning. So one of the challenges with agents is typically -- not typically, often, agents are configured with standing privileges, meaning you allow an agent to connect to one of your systems and it just has access to that system, standing access to that.

One of the areas we can address that with governance is through just-in-time provisioning and deprovisioning, where you wake the agent up when it needs to do work and then you turn it off immediately afterwards. So you solve the problem of standing privileges to that. So governance is an inherent part of the solution for securing AI.

But then the Okta for A Agents platform helps you -- again, helps with those fundamental questions. First of all, knowing where the agents are so that you know which ones might have standing privileges and you know what to look at, knowing what they've been given access to, what they can connect to. So again, you can help you understand what that exposure is and then knowing the verbs, the actions that they're allowed to take.

So is the analogy where it's everyone needs governance, but not everyone needs privileged access, meaning maybe the CISO, someone in the security team, I don't personally need access to turn it on and off MFA. So does that mean IGA is probably a bigger upsell than privileged access? Or do agents need both?

There's aspects of privileged access that really help with AI and especially in particular, token vault is a feature of privileged access and also a feature of Auth0 AI agents. And that token vaulting allows an agent to have credentials, which are managed in a secure location and have business rules that requires them to be rotated. And if you go back 10 years ago, people would configure a service account and hard code a user ID and password in a config file and be done with it and that would live that way for years.

We've all learned as an industry that doesn't work. It's a huge exposure. So privileged access will become increasingly important for more of those use cases over time. As far as our business is concerned, it's a newer product for us yet. It's not yet a land product. We have now matured Okta Identity Governance to where it's now a land product for us. And in addition to being a frequent cross-sell for existing access management customers, we're also going in to displace entrenched legacy deployments from other vendors.

So governance has matured to the point where it is now a point of entry for us, which is great. Privileged access is a couple of years behind governance in its maturity. It's certainly not -- we don't consider it a land product for us today. But for the use cases that it supports around access management and governance, it's been very effective.

Could you share what percentage, I guess, of net new customers come through IGA?

We don't break that out. Keep me honest with that, [ Dave ]. So no.

Maybe talk about the monetization. This whole conference, everyone has been talking on the software side, how this plays out over time. How are you thinking about monetization of these agents, consumption, usage-based? Maybe just walk us through what that trajectory looks like.

Yes. Todd talked about that on the call last week. The -- one of the challenges the industry has right now is the economics of AI and inference and compute are such that most vendors are bringing to market their AI offer with a consumption-based model. The challenge with the consumption-based model is customers don't know how to budget for it.

And so leading with a consumption-based model slows down your sales cycle materially. And we have this issue internally as we're buying AI products and trying to figure out how do we budget for what our consumption is going to be. So what we're doing with these early customers is we are entering into 1-year terms, and we're only having a seat-based model for now.

And we've talked to all these customers coming in that for the first year, we're going to have a seat-based model, here's what it's going to look like, and they can budget for that. And then we have the understanding that during the year, we're going to learn their actual consumption so that if we were to add in a consumption-based component at renewal, they would have data to ground their budget cycle on. And that -- the reason that we landed on that is just by working with these customers over the past six months is what would make it possible for you to get started. And that's been very effective so far.

Okay. Maybe jumping to, I think, some of the comments you made on go-to-market. You've made a lot of changes over the past, call it, 6 quarters. Most of last year was kind of ramping some of these net new reps. You called attrition is basically at levels where you haven't seen it in a very long time. So we're seeing...

Good level...

At a great level.

To be clear, that could go the other way, right.

So you -- it sounds like you're kind of pulling back, I guess, a little bit on net new hires. Maybe just walk us through some of the commentary on the call in terms of why not step up.

Yes. It's interesting, we went through a couple of years of needed go-to-market evolution. And one of the questions we would get in these conversations is how much disruption is too much disruption? And are we -- how are we managing productivity and tenure and time and seat. And we're looking back, we're very confident the moves we made were the right moves.

So our waves of specialization, we're now in our fourth, which I'll get to, but our first a few years back was to carved out a set of sellers to focus on public sector, federal and state and local and international. And that team has had a very good run focusing on those buyers and that budget cycle and those purchase cycles. We then, 2 years ago, rolled out a hunter-farmer model in our Americas commercial business.

So we moved reps who had been accountable for all new logo acquisition and upsell, cross-sell and upsell, what we had found is that, that business was shifting so much in the cross-sell and upsell and largely as we brought more products to market, they had more to sell that we weren't spending enough time feeding the top of the funnel by bringing in new logos.

So we carved out a set of sellers and put them in a hunter motion where their focus was on new logo acquisition. And we've talked about, it took about a year for that model to get -- to really get running at full speed. And that's what we had expected and how we modeled and set guidance. And then this past year, 5 quarters ago, we rolled out a specialization model on our platform and our buyers.

So whereas previously, every rep sold everything, we divided the sellers into two populations, one that sells to the corporate IT and security buyer, the CIO and the CISO, and they sell the Okta platform to that buyer and one that sells to developers, whether it's software developers or B2B SaaS or even in-house developers, and they sell the Auth0 platform.

And that specialization we rolled out January of last year, and we talked about this throughout the year, it's proven to be very effective. So as a result of all of this, we have seen several quarters of improving rep tenure as attrition has gone down and tenure has gone up and productivity has gone up as well. And overall, when you talk to the field organization, I was just at our club event a couple of weeks back, you can feel the optimism and people know that they can be successful and know that they can make money.

And so when we look at capacity to get back to your question, we want to be careful to add capacity to drive up bookings, but not to add so much capacity that we disrupt territories that we disrupt books of business, that we have to reallocate accounts and then people have to reset new relationships.

We find that when people have accounts longer, they're going to sell more into those accounts. And we don't want to carve territories to the point where reps lose some momentum and feel like they're losing some opportunity to be successful. So we feel like we have that balance about right. We've added a bunch more capacity in Q1. We're adding less incrementally during this quarter and next quarter, but we're going to measure based on our pipeline to make sure that we're not leaving deals on the table. So we'll adjust as we go.

Where is the -- you talked about public sector real quick. We had a good strong Q1. What's driving that? It sounds like it was across the board, state, federal and local.

The -- overall, the team is well tenured and well productive, and they've got the product mix that those buyers need. I think one of the things to keep in mind also is Q1 is typically a low quarter for public sector. The federal fiscal year starts in our Q3. So Q1 is typically -- we don't typically have a lot of renewals or a lot of net new purchases at the federal level, certainly. But state and local continue to be active, and we had some good federal deals in Q1 as well.

The one thing that also stood out to me was just the step-up, I think, in partner-sourced bookings, multimillion, I think, was up year-over-year. Along -- I guess more so, that was part of your shift and I want to talk about shifting more of your pro services to your partners. Obviously, that broadens distribution, makes it a lot more stickier. They're going to push your products. What was the move behind that? And part of it was part of the go-to-market changes. But if you think about this the partner-driven deals, like what -- how does that look throughout the year?

Kind of -- it's 2 things. One, we've had for many quarters, we've had -- our most exciting growth has been at the top of the pyramid, it's been upmarket. We -- I think we did announce in this quarter that our customers over $100,000 in spend are now over 85% of our revenue. And our customers over $1 million represent over $1 billion in ARR. And so as we go upmarket, we're having bigger conversations.

And as our product portfolio has expanded, we're having conversations that span multiple processes and multiple departments and multiple use cases. And as that complexity increases, our partners have an increasing need to be working with a systems integrator that can span broader parts of their business.

And so we have been working with global systems integrators across all this. And what we realized this year coming into our planning cycle is that we could take a deliberate step to refocus our professional services resources on enabling those partners to get greater scale. And so that's the adjustment that we made where we basically shifted 1% of revenue capacity towards partner enablement and working with those GSIs and these accounts. And that played out as we expected. It's both financially and from an engagement standpoint.

We have active engagements at customers with all the major GSIs. And we're seeing that continue to improve. And ultimately, what will happen is as they build more experience, they build more bench capacity, they bring us more business, because the GSIs sell what they have in their bench. And as they build Okta capacity on their bench, they're going to be bringing more opportunities to us.

When does that become more meaningful in the model? Is that 2Q, Q3? Just maybe when does it really start to step up?

Brett's comments last week was that we expect to start to see that contribute in Q2.

Okay. Maybe going back to AI. The question I had for you, and again, it's been a question I've been asked all this whole week is incremental AI dollars being spent, where is that coming from? Is it being pulled from endpoint network? Or is it like new buckets of spend that CISOs are getting?

It's really from -- it's both. So it's people rebalancing their portfolio, but there is a lot of net new investment coming in. And it's coming in because this is a Board-level exposure. So as this market evolves and as threat actors get more published, boards understand that this is a real security concern.

The problem of having agents having standing privileges to corporate assets, the problem people are understanding that they're behind in data governance and ensuring that they have proper -- they're finding their humans have access to data they didn't know their humans had access to, but now agents are on they're 24/7 and they work at a much higher clock rate than their humans work.

There's increasing exposure that needs to be managed and invested in. And so we're finding Board-level engagement and investment in Agentic security specifically. So there's net new funding coming in. And then in addition to that, companies are looking internally at where they can harvest some savings to drive into this area as well. So we feel it's very much a tailwind right now for the product, which is why we've innovated the way that we have with the offers we brought to market.

So it sounds like consolidation is definitely a trend, platformization. Obviously, one of your competitors brought it up. But with that, I mean, I guess -- and within AI, where is the most success? Is there a specific geography, a certain vertical that you're seeing more traction today than you probably wouldn't have expected 3 months ago?

Not vertical or geo, these are pretty global needs. I think where we're having the fastest success in these conversations is where we're bringing in our specialists. And so the reason we've created a tiger team is they do nothing but talk to customers about this specific problem all day, every day. And so we direct that team to the -- what we perceive to be the largest opportunities. We have activity in all of our geos. But I wouldn't say that there's a single vertical right now that is standing out beyond others.

If anyone has any questions, feel free to jump in. The -- maybe let's talk about competition. I would love your input on what you're seeing or what your expectations from Palo Alto with CyberArk. Obviously, it's more on the privileged access side. [ Palo Alto ] is making a big push into identity. I think they came out with FalconID, which I think is more of your core but very low-end products. Where is this market evolving to?

First of all, it's a huge pie. The market is enormous right now. Second, the one core differentiator that -- and we talked about last week as well, is our neutrality is huge. And customers don't know which vendor is going to own which parts of the stack, and they know that they need to be able to solve and secure identity across whatever technologies are coming in and out of the mix.

So that continues to be a core differentiator for us. We also have, from a distribution standpoint today, over 20,000 enterprises that already trust us to secure identity. And so for them, expanding their secure identity to include a new use case with agents is a very natural extended conversation of the work that we're already doing with them. We've done a really great job building those connections. And then from a partnership standpoint, I mentioned we have over 8,000 applications that are integrated with us.

Those companies you mentioned, CrowdStrike and Palo Alto Networks, they're huge partners of ours. We have thousands of mutual customers. So those relationships obviously will evolve as they -- as we overlap more on the edges, but we see it on the edges right now, not in core head-to-head.

Okay. Where do you think Palo will have the most success with CyberArk?

I think where CyberArk is strong is on Privileged Access, as you mentioned. They have many years of incumbent access there. Their solution is legacy on-prem. They're work right now to bring it into a multi-tenant, multi-tenant SaaS, and that's taken some effort for them. It will continue to evolve with Palo.

So for firms that are Palo customers that have a privileged access specific need, they and now are going to be a natural offer for that. But again, that's not a land product for us today. So we wouldn't expect to be head-to-head in those transactions. Where we're broader on access management, governance and security threat protection and posture management, we'll bring those offers in to help balance out...

Yes. For your early identity customers to what extent do they have to have a consolidated identity stack across the 3 legs of the stool to make the best use of Okta's Agentic products?

The Agentic products bundle all the capabilities that are needed from those stacks. So if a customer buys Okta for AI agents, they get the components of access, governance and privileged access that are required to secure the Agentic use case. That's how we would package it that.

So could you -- if I had Salesforce for Governance and [ Cyber PAM ] and I use you for access, could I deploy your Agentic solution or I need to migrate?

No, you can deploy it.

Full feature set. Yes.

The Okta for AI agents, to be clear, Auth0 on the build side, but on the governance side, yes.

Can you maybe help us understand where does CrowdStrike compete? Is it more complementary? Is it more competitive? Where do they fit in the stack? And then how does that...

We don't see them head-to-head at all. We talked about this on the earnings last week. The one named competitor that we see materially is the it's always been is Microsoft. And the primary play they have is bundle, right? So for customers that are -- that have a very specific need for the small subset of capabilities that Microsoft can provide in the E5 and E7 bundle and are under cost constraints, that's a legitimate competitor, and that's something that we grapple with.

But our win rates against Microsoft haven't materially changed in many, many quarters. But that's something that is a constant conversation for us because if you're not using the breadth of our stack and you're only using a subset of access managements and you have -- you're already a Microsoft bundle customer, we have some exposure there.

So our account teams are very driven right now in driving our stickier products that get us great, things like workflows, things like governance and privileged access and our security products. And as we add all those in, we become even more of an established standard and people build on us.

Is there a stat that you can maybe share like how much overlap -- how many Okta customers are using maybe parts of Entra what Microsoft has?

We don't have -- published those stats, but we have many customers that are also Microsoft customers.

Is there a specific part of the Microsoft stack you're using that perhaps that you guys don't have? Like why would -- maybe walk us through like what -- if it's a Microsoft customer using Okta and Microsoft, where is the overlap?

It can be a customer that's migrating over time and coming more -- it can be a customer that has a legacy Microsoft app that they're using that has been previously configured that they haven't yet brought over. Those use cases are very, very common. But usually, it is either that or it is people not really using the Entra components, but they're using other components of the bundle.

Maybe talking about some of the cores. Look, maybe I'll start with Auth0. I mean that business has continued to do extremely well, checks in the channel on the developer side, just the library of applications. Where does that business trend? And what are the investments that you guys are making into Auth0 today that you think will kind of help sustain that growth?

Auth0 continues to serve its core audience, which is developers. Those developers historically, we've talked about Auth0 as a customer identity access management solution, which it is. And the reason that we've used to lump those in as almost synonymous once upon a time was because the primary use cases people were using Auth0 for was to build applications that serves customers in a B2C model.

That's expanding now. Developers are building additional things. So we have a focus on B2B SaaS providers, people that are bringing applications to market. And so for those customers, you asked about innovation targets, for example, we are investing to earn FedRAMP's authorization for the Auth0 platform, which it does not have today.

And the reason that we're doing that is because B2B SaaS vendors need to be able to sell their products to government. So we need Auth0 to earn FedRAMP accreditation so that they can sell their products to government. That's an important investment that's well underway for us right now. And so in addition to B2C, B2B, we are now seeing Agentic development as the net new category. And the reason that we've been investing in that product is specifically to serve that use.

I guess just like how do you manage that investments across Okta and Auth0?

Today, our -- the engineering teams are distinct. They both report into Ric Smith, our President of Technology. And Ric is -- and that's a recent change we announced a month ago. And Ric's charter with pulling them together is to make sure that we don't duplicate efforts. So for example, we've spent many years earning FedRAMP authorization on the Okta platform side. It's FedRAMP high authorized.

We don't want to have to repeat that and start from scratch with the work that we're doing on Auth0. So he's looking for programs like that where we can get some commonality and some reuse of the skills that we've already developed in-house, and that will work in both directions for us.

The other impressive, I think, stat in the quarter, net retention ticked up for the first time, I think 106% to 107%. It sounds like perhaps maybe there is an inflection maybe later in the year. But walk us through how much of that is the core buying net new seats? AI? Is it IGA? Is it privileged access? Like what drove the trajectory to take it higher and then throughout the rest of the year?

Yes. So we've mentioned we expect it's going to travel around here, plus or minus a point for a while. It's all the things that you mentioned. The -- although I would not attribute privileged access specifically to be a material contributor, but cross-sell and upsell across the entire new product portfolio had another really strong quarter for us, and that always helps. And we've -- as we've talked about in recent quarters, we've, at this point, flushed out the COVID cohort of exuberant purchasing and 0 interest rate days. That's helped us on the NRR side as well. So those headwinds have abated and the tailwinds of having new products that are available that are driving incremental value is really resonating as well.

Are there additional I guess why are you talking about maintaining the current level through your go-to-market large Auth0 customer loss in August, I think. So why wouldn't you expect improvement in the back half?

It changes every quarter based on the mix of new business and based on the mix of cross-sell and upsell. And so our expectation is for it to trend about where it is. We're pleased to see it tick up from 106% to 107%, and we're working to drive it further. But for now, we're calling it where it is.

If you think about the growth formula for the full year guide, how much of that is just maybe an uptick in net retention, better upsell and cross-sell, which you are seeing versus just net new logo growth? Like how should investors -- how should we think about the sustainability of, call it, high single-digit, low double-digit growth for the next 1 to 2, 3 years. Obviously, you're not guiding. Walk us through like where is growth coming from?

Get me out of trouble on this. What do we say on this one?

Yes. It's a confluence of all of the major initiatives that we've been investing over the last couple of years. So it's going to be -- what's going to come from improved go-to-market execution, new products, which includes some of the agent that bit further out, investing in the partner motion and shifting some of our revenue over to our partners and success of our businesses.

Yes. Channel is a bit -- we haven't talked about channel much here, but the channel for us as well has been an area where we're pleased with the momentum that we have, and we're investing further in developing that. The GSIs are one example of that.

What percentage of your bookings in today is partner driven? And what does that look like 12, 24 months for now?

Yes. We said that over -- I want to get the numbers right here. Over 80% are partner influenced, over 40% are partner sourced. So that's when they actually source the deal and hand it over to us. We believe we can get those numbers up higher over time. That's why you see...

Now the partner influence versus partner source, like who's getting the pro service dollars? Is that the partner sourced deals?

For deals sourced with SI partners, they take prime on those deals, and we'll support them with expert services. For partner influenced, it can go either way. It depends upon how the engagement is. Our preference is to prime as little as possible. We want to make sure we maximize the opportunity for our partners. But we -- there are some use cases that are either bleeding edge with new product capabilities or require deep work with our engineering team where it makes sense for us to be prime on those transactions. But we try to minimize that so that our partners have the opportunity to build their depth of relationship with customers.

Okay. Maybe one more financial question, and I'll just end it with another. Maybe you can help me keep me honest. So if you think about the margin guide, op margin guide, free cash flow margins now high teens, if not 20%. As you think about going through the year, perhaps if you then double down higher on go-to-market, new reps, the investments in R&D across Auth0, Okta, what's the sustainability of margins and the trajectory there?

We manage to Rule of 40. And we -- so we balance the growth and free cash flow, and we work to keep them in balance and make sure we manage the Rule of 40. Right now, as we've talked about, we have -- we believe we should be growing faster. And so we are indexing our investment to elevate our growth rate as fast as we can. And we feel confident we've demonstrated we can generate cash when we choose to generate cash. But what we want to do is while we're focusing on efficiency, we want to make sure we don't starve investment opportunity that could accelerate our growth rate. So that's how we think about that balance right now.

Okay. And maybe the last question is what's your pitch to investors today? Your stock has obviously outperformed since you guys reported. Execution has been a lot more flawless and more consistent over the past couple of quarters. So if you look at the stock today, your guidance, kind of the tailwinds from AI, the monetization opportunity, I think most of us see within security because every agent needs identity authorization, you need to authenticate what every agent has. So maybe what's your pitch today? And then what does the story look like?

That's a pretty good baseline right there. So securing identity has never been more important than it is right now. Human identity has -- we've known that's been important for a while. Nonhuman identity and service accounts over the past 7, 8 years, people have realized they have huge exposures there.

And now Agentic identity and exposure has really poured gasoline on the fire. So from that overall perspective, there is an acute awareness of the importance of securing identity right now, which is going to help Okta. And I would say in addition to that, the challenge that new players are going to have in this space is the challenge of distribution and connectivity.

And our neutrality and our -- the depth of our network effect of our existing integrations makes us almost plug and play for any customer with all these use cases. And so we believe we're very well positioned to take this market. And we're working our a**** off to make sure that we do that, excuse me. Todd mentioned on the call last week, we don't get paid for pipeline. We got a good -- our pipeline right now is really healthy. We've got to convert it to bookings. And so we're very focused on doing that.

Maybe just one last follow-up. You talked about the monetization. One question I get often is, I think SailPoint puts out their metric is for every one human employee, there's anywhere from 5 to 40, I guess, agents or Chatbots, Copilot to test. What are you seeing today?

It depends who you talk to. The IDC's projection is that we'll have -- collectively, we'll have 1 billion agents live in production in 3 years out. So it's hard for people to project. And as you just mentioned in the question, it's also important in how you define an agent. What's an agent versus a Chatbot versus a piece of software tool that you use.

We -- I expect personally, and I can say on behalf of Okta, we expect there is going to be a lot more agents than there are people. And all those agents bring with them security concerns and security exposure and they expose data governance concerns and data exposures.

And so we believe all of that is going to bring Agentic identity security to the point where it becomes much more of a prominent conversation even than human, which is already critical for folks. So one of the areas that we talk about frequently that remains true is over 80% of successful cyber attacks, over 80% of successful cyber attacks start with compromised identity. And as the industry has learned that, as the industry has become aware of that, they understand that they cannot have a secure company if they're not properly investing to securing identity. And we believe we have the right to earn that business to be that solution for them.

Quantum question. I know it's like a couple of years down the road. Is that a concern at all for customers today as you think about quantum breaking through any -- basically any kind of encryption?

From time to time, I'll talk to CISOs about their thoughts on quantum. But what I can say is it's not a -- I'm not experiencing it as a top-of-mind concern today. It's on the radar, something they should probably be thinking about, but it's -- they have acute issues to manage today, and that's something to think about in the future. Not there yet.

If there's any other questions? I think we could end there. Eric? All right. Thank you.

Thank you.

[Presentation]

Hi, everyone. Welcome to Okta's First Quarter Fiscal 2027 Earnings Webcast. I'm Dave Gennarelli, Senior Vice President of Investor Relations at Okta. Presenting in today's me will be Todd McKinnon, our Chief Executive Officer and Co-Founder; and Brett Tighe, our Chief Financial Officer. Eric Kelliher, our President and Chief Operating Officer, will join the Q&A portion of the meeting. At around the same time, the earnings press release at the wire, we posted supplemental commentary to our IR website.

Today's meeting will include forward-looking statements pursuant to the safe harbor provisions of the Private Securities Litigation Reform Act of 1995. A including, but not limited to, statements regarding our financial outlook and market positioning. Forward-looking statements involve known and unknown risks and uncertainties that may cause our actual results, performance or achievements to be materially different from those expressed or implied by the forward-looking statements. Forward-looking statements represent our management's beliefs and assumptions only as of the date made. Information on factors that could affect our financial results is included in our filings with the SEC from time to time, including the section titled Risk Factors in our previously filed Form 10-K.

In addition, during today's meeting, we will discuss non-GAAP financial measures. Though we may not state it explicitly during the meeting, all references to profitability are non-GAAP. These non-GAAP financial measures are in addition to and not a substitute for or superior to measures of financial performance prepared in accordance with GAAP. The reconciliation between GAAP and non-GAAP financial measures and a discussion of the limitations of using non-GAAP measures versus their closest GAAP equivalents are available in our earnings release. You may also find detailed information in our supplemental financial materials, which include trended financial statements and key metrics posted on our Investor Relations website.

In today's meeting, we will quote a number of numeric or growth changes as we discuss our financial performance. And unless otherwise noted, each such represent a year-over-year comparison.

And now I'd like to turn the meeting over to Todd McKinnon. Todd?

Thanks, Dave, and thank you, everyone, for joining us afternoon. We're pleased with the strong start to FY '27. Consistent with recent quarters, our results were driven by strength with enterprises, partner engagement and contribution from our newer products. Underpinning this performance is the durability of our core business with the Okta and Auth0 platforms, both contributing to steady momentum across our entire portfolio. That said, the #1 topic of interest from customers to investors is Okta's AI strategy. So today, I'll focus my remarks on how Okta is uniquely positioned to capture the AI opportunity.

The future of technology is agentic. For Okta,, this represents a tremendous opportunity and an even greater responsibility. Every agent inside an enterprise is a new identity. Today, AI agents are the fastest-growing identity in the enterprise but also the least governed. Okta helps bring agents under control by treating them as first-class identities that can be managed and governed by their existing identity management system.

We believe, over time, most large enterprises will have more agentic identities than human ones. This shift broadens the attack surface because every agent comes with credentials privileges, and the ability to act on a user's behalf. In turn, this raises the strategic value of the identity layer because governing autonomous systems requires the kind of control, audit, continuous intent-driven authorization and real-time enforcement only an identity platform can deliver.

To help our customers confidently secure this shift, we're building on 3 unique advantages, each with powerful network effects: distribution, product breadth and neutrality. Today, I'll cover all 3, starting with distribution. Okta pioneered identity for the cloud era. Over the past 17 years, we've built the most modern and comprehensive identity platform, which is now the identity system of record trusted by more than 20,000 customers. In the agentic era, identity becomes even more foundational. When a customer secures their agents with Okta, they are not taking on a new platform; they are extending the trusted foundation they already rely on with Okta.

We've already seen how our customers benefit from this expansion in other parts of our business. Customers are finding value in Okta's unified identity system as Okta in governance was once again the leading contributor among our new products. This distribution flywheel is evident in our results.

Our new product portfolio represented approximately 25% of Q1 bookings, a meaningful increase from Q1 last year. We see a 40% ACV uplift when new products are included in a deal. The same customers who trust Okta for workforce and customer identity are extending that trust into agent identity.

Our second unique advantage is product breadth. We are the only vendor with solutions that address both sides of the agent security problem. Okta for AI agents, which became generally available last month, gives enterprises a single control plane to discover, govern and manage agents across their organization. It is the first and best implementation of the blueprint for the secure agentic enterprise, an industry framework for bringing agents under control by answering the three questions that have dominated my customer conversations over the last several months. Where are my agents, what can they connect to and what can they do?

Enterprises need to maintain visibility and control over their sprawl of agents, ensuring they have governed identities, consistent access policies and ways to shut them down to secure every agent to end. Okta provides customers with centralized visibility into agents with identity governance capabilities, including ownership assignment and life cycle management while giving IT and security teams, critical security controls to deactivate rogue agents.

For developers building AI agents, Auth0 for AI agents provides the identity foundation to ship secure agents inside their products. Auth0 for AI agents secures agents, APIs and users effortlessly for B2B, B2C and internal apps, all backed by the enterprise grade Auth they already trust. In tangible terms, pipe generation in Q1 was strong, driven in part by these 2 new products.

The third unique advantage is neutrality, which is more important than ever. The AI landscape is opting rapidly. Customers need an identity solution that frees them to choose whatever technology serves their business best without fear of vendor lock-in. As the leading independent and neutral identity platform, Okta gives organizations the flexibility to do exactly that.

In the same way, enterprises run workloads across multiple clouds. They are deploying agents across various platforms like OpenAI, Anthropic, Google, Microsoft, Salesforce and a growing set of open source frameworks. Managing and securing an autonomous workforce requires a neutral, independent identity layer that others can't provide.

In practice, cloud providers, all providers and agent platforms are partnering with Okta to securely manage agent identities as they continue to proliferate across the enterprise. Okta is the only [indiscernible] platform purpose-built to sit above the agent ecosystem, and it federates with whatever identity provider a customer runs. That means the opportunity for Okta for AI agents is not limited to our existing workforce customers. It extends to every enterprise with a multi-platform AI strategy.

These 3 advantages are unique and mutually reinforcing. The more organizations use Okta to secure their agents, the more identity signals flow into our platform and the stronger our governance and detection becomes, and our neutrality allows us to secure current and future agent frameworks for customers, allowing Okta to capture more of the addressable market.

Neutrality becomes even more important when it comes to technology partnerships and integrations, like the traditional cybersecurity landscape, no single company can address the agentic security market alone. That's why we've partnered with AI leaders from ISVs to hyperscalers to frontier AI vendors, and I'd like to highlight a few of those partnerships today.

We've entered into a partnership with ServiceNow that integrates their AI control tower product with Okta for AI agents. Our partnership with Google brings centralized identity guidance and access control to Google's agent gateway. Okta for AI agents now integrates with Amazon Bedrock Agent core to provide customers with identity governance capabilities for their agents.

We were a launch partner for OpenAI's release of GPT 5.5 trusted access for cyber. And finally, we're collaborating with Anthropic in a number of ways to testing Anthropic's preview model as part of Project Glasswing to a new integration between Okta Identity Security Posture Management and the Cloud compliance API.

It's still early days, but the agenetic era is fundamentally transforming how we deliver success for our customers. By leveraging our unique advantages, great products, deep partnership and industry expertise, we are well positioned to help customers thrive in this fast-moving landscape, which will unlock a new growth vector for Okta.

To wrap things up, FY '27 is off to a strong start as we look to build on our momentum as we move through this year and beyond.

I want to thank the entire Okta team and our loyal customers and partners who put their trust in us every day. And now here's Brett to cover the financial commentary.

Thanks, Todd, and thank you, everyone, for joining us today. The investments we've made in product division, our go-to-market team and partner network are yielding tangible results. We're pleased with the strong start to FY '27 and are confident we're on the right path to accelerate the business. My commentary will provide insights into our Q1 performance and then move into our outlook for Q2 FY '27. I'll start by highlighting the strength we saw in our go-to-market performance.

As a reminder, at beginning of Q1 last year, we further specialized the [indiscernible] team into Okta sellers addressing security and its Auth0 sellers addressing developer buyers [indiscernible] are now fully settled into place, allowing us to start this fiscal year with far less change.

The stability of the sales team, coupled with strong execution led to positive go-to-market KPI improvements. including increased sales productivity, strong pipeline build and low AE attrition.

We're also seeing the investments we've made in our partner initiatives take root as partner-sourced bookings experienced a meaningful increase including multiple dollars million plus deals in Q1.

Moving on to our balance sheet and capital allocation. We had another strong quarter of cash flow in Q1 and ended the quarter with a very healthy balance sheet consisting of approximately $2.6 billion in cash, cash equivalents and short-term investments. Next month, our convertible notes reach maturity, and we will settle the remaining principal amount of $350 million in cash.

Over the course of Q1, we repurchased and retired just over 3 million shares for a total cost of $241 million. $608 million remains under the $1 billion repurchase program that we launched in January as we look to take advantage of what we believe to be an undervalued share price. We continue to regularly evaluate Okta's capital allocation priorities to ensure we're well positioned to sustainable long-term value to shareholders.

Now let's turn to our business outlook. Our guidance philosophy is unchanged as we continue to take a prudent approach to forward guidance.

For the second quarter of FY '27, we expect total revenue growth of 9%, current RPO growth of 11%, non-GAAP operating margin of 26% and free cash flow margin of 20% to 21%.

For the full year FY '27, we now expect total revenue growth of 9% to 10%, non-GAAP operating margin of 25% to 26% and a free cash flow margin of 27% to 28%. As I called out last quarter, the FY '27 revenue guidance includes about a 1 point impact related to a strategic decision to shift more of our professional services business to our partners, specifically global systems integrators. This change will result in lower professional services revenue and is expected to start to materialize in Q2.

In addition, the FY '27 free cash flow margin guidance includes about a 1 point impact related to lower interest income due to the combined impact from the stock repurchase program and our intent to settle the remainder of the 2026 notes in cash.

To wrap things up, we're optimistic about the trends we're seeing in the business. We've been disciplined with our cost structure while investing for growth, putting Okta in a great position to extend our leadership in identity security.

We've demonstrated exceptional leverage in our model and are positioned to deliver profitable growth for years to come.

With that, I'll turn it back to Dave for Q&A. Dave?

Thanks, Brett. I see that there are already quite a few hands raised, and I'll take them in order until the top of the hour. And in the interest of time, please limit yourself to one question. So with that, we'll take the first question from John DiFucci at Guggenheim.

I guess I'm going to stick, I was going to, a couple but I'm going to ask one, Dave. And it's going to is going to lead into what Todd was talking about with AI. It's not won I'd like to ask usually, but I think, based on our work anyway, you guys have done a great job of gaining AI mind share among the channel, like the channel is talking about what a good job you're doing that and getting in front of customers, but we realized it's still early. Can you talk about how this is materializing in the market? How are customers actually at the point where they're actually securing agents yet, are they just talking about it? Or are there a lot of them that have already been really doing that and you're trying to make sure you're in front of it?

John, let me set the stage for you out there. I've spent the last 6 months, I'm on this goal to talk to in-person face-to-face with our top 100 customers, about 75 customers in. And when you mix that with a bunch of other conversations, here's what's going on, everyone is deploying agents in some way, shape or form. But they're really just starting to think about and put in programs in place to lay out the rails of governed managed adoption. So a concrete example is you'll have a development team that is using cloud code, but it's connected to GitHub and their JIRA system with static tokens in the local developer box. So that company is viewing agents, but they've really done it in a haphazard nonsecure way. And what's happening now is they're figuring out those rails. They're figuring out how they're going to have secure connections, have a system to monitor where all the agents are, have the ability to support it for multiple platforms. And that's why you're seeing the record interest and the record pipeline for what we do with Okta for AI agents and Auth0 for AI agents.

The reality is of these products, it's still early. They're not materially contributing to the business in Q1. In fact, we're still being prudent in our guide. They're not even -- they're a little bit in the guide, but not significant in the guide but it's going to be big. We're putting a lot of R&D effort into this and focused on it. And the interest is super high unlike you've ever seen. And I think it's because we focused on it, we have a good story and good thought leadership, as you mentioned, with the channel. But I think another big reason is that it's ours to win because they're used to looking to us for trusted infrastructure that they use to connect their employees and their customers to all these resources. So it's very natural to say, who can really manage these connections and give me these governed rails for all these secure connections, where my agents are, what they're doing, what can they do? It's a natural fit for us. So I think as they build out this infrastructure, we're in this really great position to have to be a super, super meaningful part of the business and TAM over the next several quarters and several years. And that's why we're working so hard to take advantage of it.

Todd, that all makes sense. If you could just, in this same topic, when do you think this will start to happen in mass? And like I said, you're up ahead of it.

Well, one thing that's already happening is that we're already starting to get pull-through in the sense that these agentic AI conversations are raising the strategic importance in many of our customers' eyes of what Okta is beyond just workforce, access management to this really, hey, these guys could be this broad platform across governance, privileged posture management, identity security, identity infrastructure, and that is having an impact. That is in the numbers now. Like if you look at our 12% revenue growth, you look at net retention inflecting up to 107, cRPO of 12% that's being driven by Okta being put in a more strategic light because of this thought leadership in AI, and that's and that's going to continue throughout the year as well.

Thanks, John. Next up, let's go to Brian Essex at JPMorgan.

I wanted to follow up on John's question a little bit. So Todd, I would love to know from a macro and spending perspective. I mean you heard beginning of the year, I think there was a little bit of caution around IT security budgets. And then we started hearing about security getting access to budgets outside typical budgets, whether it's like marketing budgets and so forth. And now we're starting to hear about like [indiscernible] or incident spend. Now that mitosis come out last week, which you mentioned, I think CIOs a little bit fearful of the, how the threat environment might accelerate. So could you tie that back into what you're seeing for demand and access to IT budgets? Are you getting that incremental spend? Is the panic around the threat environment a headwind to your sales cycles? Or are you benefiting from it? Would love to just get what you're hearing from customers.

So when we talk to customers, there are cyber professionals, and they're entrusted with keeping their organizations secure. So any kind of intelligence they can get any kind of like edge or information, whether that's something on the dark web or that some new model, they're all over it. And there's a ton of energy around getting access to meet those and Glasswing and OpenAI is a new model. So they're very interested in that.

That being said, I think the world in the population has extrapolated that from thinking that they're panicking and changing their priorities. And that is not true. I think what it's doing is it's -- everyone is reinforcing the fundamentals. They know what they have to do. There's been 0 days forever. And now there's going to be more, and we can debate how many more, but they've known what they have to do. They have to have a good zero-trust environment. They have to have solid identity. They have to make sure they have a patching process. They have to make sure they have visibility. So it's -- I think what I'm seeing is that Boards and CEOs are saying, we know this agenetic thing is real. We've got to put the guardrails in place for that. and we know that security is real, and we're going to spend money on that. And it's, the reality of it, Brian, is that it's the fundamentals. It's identity 80% of breaches are go through identity. And you know you have to patch your systems. You know you have to have a good multilayered defense and Zero Trust so you can defend for multiple ways. And so that's, I think that's why we're so well positioned to be that key identity platform in an unmatched way of products that no one has. No one has governance PAM, identity infrastructure. I did any security agents. So that's why we're really excited about what's going on.

That's helpful. But are you seeing that materialize in like accelerated sales cycles? Or is this more of a conversation?

I think this return to the fundamentals and known you have to fix our fundamentals is helping the identity market and the identity security market. I don't think it's necessarily showing up in agentic identity yet. That's still early. But it's accelerating the importance of investing in your identity infrastructure in your identity security.

Great. Let's go to Todd Weller at Stephens.

Todd, question for you on agentic. If you laser into kind of the run time authorization and policy enforcement area,, could you kind of provide some details on Okta's role in that layer? And then how you interplay with some of these embedded capabilities we're seeing in the hyperscaler and agentic AI platforms?

Yes. So sometimes it's all moving so fast and everyone's got their release and their announcement. And everyone kind of says the future of agentic is centered around what they traditionally have done, right? So it's a little bit hard to pull apart.

Here's what Okta does and it's very much a key part of what is needed. And that is we connect resources to -- we connect traditionally as people to resources, whether that was the apps you need to do your job, whether that was the apps your customers wanted to browse on your website or mobile app. And now it's very similar with agents. We tell you who your agents are. There's a directory of agents. We can scan multiple platforms and multiple systems and give you that source of truth of where your agents are and we can help you set a policy on what they can connect to. Agents can this from teams and they can read this from Slack, and they can read this information from Snowflake and they can you read this from GitHub. So it's like a single sign-on or access management.

Now all the protocols are different. So it's a new product capability and the way agents are built are different than some of these other apps are built. So it's a new set of capabilities, but it hits the same thing. And then you mentioned this last part, which is really key, which is like once you can get into these systems, what can the agent do, what types of data can they see? Is it read only? Is it read-write? How does it work? And so we can lay that authorization actually so we can surround the agents with an authorization layer that will control what the agents can do without having to go into these large enterprises that we're working with the FedExes, the Dell, the biggest companies in the world, they have thousands of applications. And it's not realistic to go -- require the customer to rewire all these applications to set up their agents. So we can surround the agents with an authorization layer that does that in a scalable way. So it's detecting agents, controlling how they can connect to things and then what they can do in there.

And there's a few fundamental truth that are going to play out. I think, one is that they're going to get agenda capabilities from many, many companies. They're going to have different platforms. They're going to have hyperscaler platforms. They're going to have Foundation model platforms. They're going to have open source platforms. They're also going to get agentic capability from apps. Salesforce is going to have there. Workday is going to have their ServiceNow is on and on. Everything is going to be agentic -- have agentic capabilities. But we know they're going to have a directory of these things or roster everything, a policy layer and they're going to have to make sure they can connect to things. And so we're seeing our customers -- it's a kind of a no-regrets move to pick this independent and neutral identity layer that can solve those fundamental problems without locking them in to, hey, you've got to be all agent core. You've got to be all Agent 365 or it's Agentforce. They want flexibility and choice across multiple things.

Let's go to Eric Heath at KeyBanc.

Congrats, everyone. Todd, just to stick with the theme, I wanted to ask about the pricing strategy for AI agents and understand everything is early. So just curious to get your perspective on where the market is in terms of figuring out how we're going to price these things? And then just any update you might be able to share on the uplift you're seeing from AI agent deals at this point?

One of our advantages is that we have 20,000 customers. And the way I've organized the team to attack this opportunity is all around focusing our strategy in our product road map, directly informed by active customer conversations. So we have an AI takeoff team that's out there having hundreds and hundreds of conversations with our customer base, figuring out what they're actually going to do with these agents today, what are their challenges today and tomorrow. So it's very informed by what the customers actually are doing, planning to do.

It's not -- I tell the team, in this area, there's so much hype and so much noise. It's a big risk of science experiments, building things that maybe aren't super useful that sounded like a great idea. So our approach is very pragmatic and focused on the real requirements. And so the way we've done pricing for our products is exactly in line with how our products have been priced in the past. They're priced on, it's an uplift to a named user or it's an uplift to a monthly active user.

Now you might say, "Hey, Todd, but agentic -- agents are this new thing and why are you pricing them on an active user or a named user price?" And that's for two reasons. One reason is that's the way customers want to consume it right now. And two, the majority of concrete use cases in the world right now for agents, it's on behalf of the user. It's an agent working on behalf of a software developer. It's an agent working on behalf of a support rep. It's an agent working on behalf of someone in accounting. So it's very natural how they want to buy it and how they're actually being used. So it's an uplift on a named user, and it's uplift on an active user.

Now we fully understand that, that's going to evolve. And there will be more autonomous agents that have to be priced not by user base or not an extensive user. They have to be the unit has to be the number of agents. It's a little bit tricky because it's very hard to define the number of agents because some person might say, "Oh, I have 1,000 agents, but it's really kind of 1,000 copies of the same agent or 1,000 instances of the same agent. In other cases, it might be literally 1 instance of an agent acting for many, many different use cases. So the industry is kind of figuring that out, and we'll figure that over time how to monetize and price that now. But right now, it's, we're pricing for market share and reducing friction and how customers want to buy. And that's -- we think that's the winning strategy.

The other thing, Eric, I would just add around your question around uplift and how that's going. The average deal size for these AI-specific deals is significantly larger than the average deal size for the rest of the company. So we are seeing a good uplift. Look, we're still early. So that has the potential to change. But the early signs are these deals are quite sizable, and that's one of the reasons why we're optimistic about the opportunity in the long run.

Yes. And we're just in a different, it's a different strategic conversation with customers where you're talking about we're going to be the backbone for your agentic control plane, and we're going to also do your customer identity in your employee identity versus, hey, we want some tactical multifactor authentication thing to pass an audit, and it's maybe done lower level in IT. It's a little different type of conversation we're in, and that's really driving a lot of this positive momentum in the business.

Then we Go to Adam Tindle of Raymond James.

All right. Todd, you mentioned a building pipeline on AI. I wonder if you might hope with the size of this maybe relative to other products in the past or maybe a different way to ask that to Brett.

The pipeline is bigger than anything we've ever seen, like we don't get paid for pipeline.

Very clear, very clear.

So it's not a pipeline problem. It's not going to execute on turning this pipeline into real dollars. And the reality is if you look at like it wasn't, the AI agent products were not materially -- didn't materially contribute to Q1. It's not -- there's a little bit in the guidance, but it's heavily discounted being pretty prudent there. But we're optimistic. We vote with our dollars, and we're investing a lot of R&D in these products. And if you just look at what is needed in the world and thousands and thousands of customer conversations, the need is there. And customers are going to lay down these rails. They're going to lay down these rails of security and identity for their agents, and we're there to convert that pipeline as soon as we get the opportunity.

And I see it in Brett's guidance is about 100 basis points above where we would normally guide Q2 based on the past couple of years. So I can see some of that.

I guess the other part of my question I wanted to ask was the difference between AI for agents in Auth0 versus Okta, the 2 different platforms. Maybe just help us appreciate the technology aspect of that? And is there [indiscernible] difference in size of pipeline between the 2? Is one materializing faster than the other?

They're both healthy, the Okta pipeline is bigger. And I think that's because it's a little bit of a -- I think the companies that are figuring out how to manage and deploy internal agents are further along than people building agents into their products and into their websites. But I think that they're both going to be big opportunities over time.

Let's go to Josh Tilton that Wolfe Research.

Maybe I'll call it to 2 parts, so Dave can kill me. But the first one is just really strong short-term bookings. I think some of the strongest we've seen in a while. How durable is that growth? And then just maybe my second part, completely unrelated to anything we talked about so far on the call, but it kind of stood out to me in the prepared remarks. Large customers represent 85% of ACV now. I think you guys used to call out 80% of ACV. Maybe just help us understand like what's driving that mix shift there.

Yes. I mean I can take the mix shift. Todd, if you want to take the first one?

Yes, for sure. What -- you want me to talk about short-term bookings or...

Yes, absolutely. I can get into too as well.

Yes. I mean I think that the performance in the business, we think, is very, very durable. We don't -- like if you look at the -- particularly the AI landscape, I was having dinner with a bunch of CEOs of companies, different sizes, and everyone is super worried about their spend in their products and their revenue in their products being not durable because it's token spend, and they worry about the products being used and then and maybe someone is going to look at the spin and stop spin the token spend, and we don't have that. This is critical infrastructure. This is -- these are -- whether it's just core identity, infrastructure for people or for customers, the -- it's like good news and bad news. The bad news about identity is it's pretty hard to put in place, and it's pretty hard to change. So it takes longer than some of these other categories.

The good news is that once it gets in is sticky and you're not going to take it as long as you kind of keep innovating at a reasonable level, you keep good customer relationships, you're going to have a very profitable long-term relationship. So yes, we're very confident that the -- in these trends of the business that are durable and sustainable and in a lot of ways with what's going to happen in this AI wave just getting started.

One of the things I'll add to the durability comment as well is in our results for the quarter 1, we reported that our new product inventory overall accounted for 25% of our bookings. So while we're not yet seeing a material uplift specifically from our AI products given that they're newer to market, that's continued growth trend in the diversification of our product portfolio. And Todd talked about that today in his opening comments. Customers are continuing to look for us to solve the breadth of use cases they have across all their technologies and all their stack. And knowing that Okta is going to continue to be the neutral identity provider growing from access management through governance, and we continue to have a great quarter for our governance portfolio and into privileged access, we had some great wins in the quarter for Privileged Access as well, all of that is continuing from a durable momentum basis.

And then as Todd indicated, the additional products now entering the mix with Okta for AI Agents and Auth0 for AI Agents provide further upside to that. So we're very optimistic on the durability of the results we saw for Q1.

Yes. All right. So I'll answer a little bit on the first and second question actually. So Josh, I would say in general, if you look the strength across the quarter was fairly broad-based. As -- for Q1, usually, Q1, as you guys all know, is seasonally a low are of the year, right? But if you look at a lot of the metrics in Q1, they were quite healthy, whether it's the pipe gen, whether it's the bookings number, whether it's the AE attrition, AE productivity, across the board that's pretty good for Q1, which we're really pleased with, which is why you hear all the optimism in our conversation today and the prepared remarks and you see it in the numbers, frankly. So I think it's very exciting from that perspective.

In terms of the 80% to 85%, it's something simply we've been working on very hard over the last few years. We've talked to you a lot about large customers, right? We've talked about the investments we've made into those large customers and getting more large customers, and so it's really the result of the hard work that we've been doing over the last few years. You can see it in the $100,000, which is what you talked greater than $100,000. You can also see it in the greater than $1 million customers. So obviously, that was growing quite nicely in the quarter as well. So I think it's just the result of our hard work.

If you look at our strategic initiatives this year in FY '27, large customers is on the top of the Board as well. right? AI and large customers are really the 2 of the main 4 on the board that we've talked with you guys about in the past. So it's -- I mean, it's not hugely surprising numbers are out there because of all the hard work we've been doing over the last couple of years. So hopefully, that helps, Josh.

I'll just -- hearing that commentary, one thing I want to throw out there is that the large enterprise opportunity is still -- we're still relatively early. We've done really well in the mid-enterprise, and we have a lot of opportunities still in the Global 2000. So it's paying off, but we still have a lot of upside there as well.

In addition to all that, we also talked about the fact that we had a great quarter in pub sec in our federal and state and public sector business as well. So across the board, we're very bullish.

Okay. We'll take the next question from Roger Boyd at UBS.

Todd, in your prepared remarks, you talked about Okta's ability above the agentic ecosystem that Okta for AI agents is not necessarily limited to your existing workforce customers. I guess are you seeing your thought leadership and the conversations you're having with customers around agentic Identity starting to influence broader identity deals or creating or competitive wins down the road?

Yes. I think we're definitely seeing that. We're seeing that the products we've offered for AI agents in this blueprint, this vision we have for the industry and agents is raising the strategic level of conversations, which is pulling in other products and helping us displace legacy faster and sell more of our existing products and our newer products into new customers in the base than we would be otherwise.

I say that because to make it clear that the AI agent products are still, is still immaterial, the contribution with Okta for agents going GA in April. They had a good quarter, but it's still a small base. So the pull-through is real already though.

We'll go to Peter Levine at Evercore.

Maybe for you, Eric, just to kind of piggyback off the prior question. We've talked about, I think, Todd, in your prepared remarks, bookings. So maybe just talk about IGA PAM. Like are these competitive displacements versus greenfield opportunities? Just curious to see how much of your IGA product today are you seeing customers attach as a stand-alone similar to the Privileged Access product. I know that's not as mature, but you're really seeing a lot of traction of IGA. So just curious what you're seeing from a competitive displacement versus greenfield? And are you getting net new customers coming in buying these problems?

We are. Thanks for the question. The reason that, I mean, that comment to the par is I didn't want the breadth and success continued momentum with governance and Privileged Access and the rest of our portfolio to get drowned out with all the conversation we have about our AI products. We're very excited about our AI products. But governance continues to be a strength for us.

We talked over the past couple of quarters about how governance has evolved from being primarily a cross-sell add-on product to also now being a land product. And we are seeing sizable land opportunities, starting with governance at some companies that are displacing systems that they've had in place. So we're very excited about the enterprise readiness and robustness of our governance product and the rural deployments. We have some very large customers, including Fortune 100 customers who are consolidating all of their identity use cases onto Okta, including governance and including privileged access, and we're very excited for where we get to. As you mentioned in your comment, privileged access is further behind governance on that maturity curve. It came to market a little bit later. We're continuing to invest heavily in it and we did an acquisition back Q3 at Axis to add capabilities to that. And we're continuing to invest in that breadth of portfolio, kind of rounding out the identity security fabric in addition to all the momentum that we're seeing with our great success in the AI product. So we expect that new product portfolio contribution to continue in future quarters and not be limited to the conversation we're having about.

Great. Next up, we'll go to Shrenik Kothari at Baird.

So among the enterprise partnerships that you announced, and given your strength, the ServiceNow Control Tower sounds really interesting, especially because we have heard ServiceNow is talking becoming a workflow governance layer for enterprise AI already beginning to monetize it. So can you walk through the partnership dynamic? How is that passing or how do you envision reaching brand customers and budgets earlier in this AI governance process? As you said, it's a little players out there.

And just as a quick follow-up, also tying to your earlier comments, are these strategic partnerships also weigh because managing identity is being pulled into a broader identity of workflow transformation programs instead of now stand-alone, is it something which is showing up in these kind of partnerships?

ServiceNow is, as you mentioned, super interesting. They are -- their product strategy is they want to be the control tower for all AI agents. And what is, what they were really interested in was this kill-switches capability. When agents go awry and agents aren't following the policy, how do you shut them down, and that can mean a lot of different things. That can mean actually stopping the running of the agent that can mean quarantining the agent at a network level, there's many different strategies.

The one thing we do really well and that they wanted from us is the ability to sever the connections, the access tokens, the actual logical connection at the authorization layer to the back-end resources, and we're really good at that. That's kind of the core of our product. What can these things connect to, what can they do.

And people -- everyone is trying to figure out who's going to be the winner, who's going to be the losers and how is the competitive dynamic going to play out. I think there's going to be way more working together than people think. We're really excited about our conversations with Amazon and their agent core, ServiceNow, Agentforce from sales force. And the message from customers is clear, they want this identity layer and this connectivity layer to be independent to give them more flexibility. And I think the industry is coalescing around that, and we're leading the way there.

Yes. And what I would add to that, Shrenik, is, this is something can does really like we talk a lot about the importance of neutrality and our philosophy that we want to meet our customers where they are with the technologies that they're deploying within their companies. And we want to make sure that we provide the identity control plane across all of their use cases and all their vendors and all of their stacks. And so you'll see, just with our highlights during this quarter, we're really engaging with and partnering with all the major platform players that are active in the space right now. And that's one because our customers wire it and it's important for neutrality. And it's two, it's something Okta has been really good at throughout our history.

We are an integration company. We have 8,000 integrations for our core products through the Okta Integration Network available today. So for us, expanding those integrations with the active providers who are gaining traction right now in this time is something that's very natural to us and something we expect to continue as these tools are evolving. And as you all know, the landscape has been very dynamic with different vendors leapfrogging each other. We expect to be partnering with all of them going forward as well.

Okay. We'll go to Yun Kim at Loop Capital.

Right. Great. On Brett's earlier commentary that average deal size when AI products are included as much as the regular non-AIR deals, I am assuming that the actual AI deal itself is small and it's still very early. So is the larger deal sizes mainly driven by customers adopting Okta platform as they adopt AI security solution? So in that way, is your AI agent in a way, driving the customers to adopt auto more broadly? And is there like a specific go-to-market or a push to do this prospect is showing interest in your AI agent product?

To be very clear, and I'll let Todd comment on the second part of it. But the AI product itself what I'm talking about when I say the average deal size, that -- I'm only talking about the AI line on the deal. I'm not talking about the broader deal. And so it's a very sizable deal just for the AI products themselves. And so then you heard Todd talk about earlier about how we're getting this concept of pull-through, like, which is what you're, exactly what you're mentioning, which is AI as part of it in some of these deals, but also it's forcing customers to modernize their tech stack to be able to look at identity and really examine it and make sure it's working for them then that helps the other side of the platform as well. So I just want to make sure that was clear in you can add anything I might have missed. But that's the general idea of it is just the line item itself is a pretty large line item at this point. Granted, we're still early on potential for it to change. But right now, it looks pretty good.

Yes. In the early days of, it's early days for Okta for AI Agents and Auth0 for AI Agents. But as we scale it up, as we kind of convert this record pipeline, it's about doing more deals. It's not actually about doing bigger deals. The deals are big, which is a little bit different actually than other new products. And even governance 4, 5 years ago was the initial deals were small. Then they got big, then we did more of them. So this one is they're already big. We can do more of them.

Okay, great. Looking forward to the progress.

Just one additional comment as it ties back to a couple of the questions we had from earlier in the session. questions around budget durability for customers. This is one of the reasons that the deals are big. And one of the reasons we've had great momentum and success with hundreds of enterprises we're engaging with and one of the reasons our pipeline, we feel very strong about our pipeline, as Todd mentioned, we haven't seen a pipeline like this for a new product ever. And all of that is because of some of the statistics we shared in the opening video, which is customers have both today. They have a problem today where over 90% of them have agents in production, and only 22% of them are confident to have them governed. That is a real problem. It's a measurable, quantifiable exposure customers have right now within their companies, and they need to invest to fix it. And we are working very hard at Okta to meet them at that need to make sure that we've got the products that are going to help them address that exposure. And we're very bullish about being able to continue that as we help more and more of our customers secure -- become what we call the secure agentic enterprise.

Great. Next up, we're going to go to Junaid Siddiqui at Truist.

Todd, the role of the model providers is hotly debated within cybersecurity, even though it's early days. But to what extent is your participation in initiatives like Project Glasswing and trusted access for cyber translated into measurable improvements in win rates or competitive positioning? And more broadly, how do you see their role evolving in the broader cybersecurity landscape?

That's a really good question. I don't think it's -- these partnerships have moved the needle yet in real customer conversations. I think we have such an interesting vision and our blueprint is so helpful for customers. that's what's driving it. I do think we need to partner with everyone, including the model providers because they're going to be providing platforms and a agentic scaffolding and infrastructure, and we're going to fit well with that, and we're going to make sure that we can take that from a model provider or from an app company or from an infrastructure cloud and make sure it can help the customer answer these questions. Where are my agents, what can they connect to and what can they do when they do connect?

And I think in terms of the model providers, how they're going to play in the broader cyber ecosystem, it's going to take a village. I think we've seen that in cyber forever. I think consolidation in cyber never seems to work. All seems to be -- gets to a certain point and then new threats emerge, and the companies that are trying to consolidate cyber have such a hard time integrating amongst themselves. It kind of fractures a part. And I think that will continue. I think cyber in the agentic world is going to take a village, and we're going to have to make sure it's integrated together and make sure we have layered defenses. And that's why I think it's really healthy to be coming into this conversation with this open mindset of, hey, we have our lane, we're going to try to provide the best identity foundation in the world and then connect around that in a standard way that helps customers get great outcomes.

All right. Let's go to Fatima Boolani at Citi. Fatima are on? If not, we're going to go to Gray Powell.

Congratulations on the results. It's good to see. So maybe just sticking with the AI topic. In RSA this year, the messaging from just different identity vendors on agentic security. I mean I have to admit, it all sounds pretty similar. Everyone is talking about some form of agent discovery, guardrails, identity governance. And along the CISOs that we speak to are just, well, they're confused. So I understand you have strong relationships. I guess my question is like how does Okta cut through the noise in the market, differentiate yourself and get to the people that are actually in charge of making decisions?

First reason, that's why we wrote this blueprint, Gray. We're trying to -- people want a blueprint. In fact, it was based on a customer conversation ahead. This guy, he was a great customer of Okta, and he's been in the value visiting a bunch of companies, and he said the same thing you said. He's like, "Todd, I don't know how you're saying, you're all saying the same thing. It's like, you should really, you should come up with like a blueprint for us." I said, "that's a great idea." So that's why we made this blueprint. And it kind of tries to -- make clear -- tries to define the swim lanes. And it's been really well received, and it kind of -- it makes it very clear that there's a bunch of stuff you need to do. Here's the different roles and here's the different ways to do it, and here's what Okta is doing, and here's, so yes, that's one way.

And the second one is just customer traction, as we get customers live, and we keep saying that the agent products have -- are just getting started, but there's still many, many customers on them going live. And so once that happens, that's going to be very valuable. That we're going to tap those stories and make sure everyone else in the world knows about them, and that's how you set standards, and that's how you go from like a blueprint and a concept at an actionable implementations that people can pivot off of and have their own success. So that's the plan.

And like I said, a lot of it is it comes down to the reason -- I believe strongly that the reason why we're seeing so much pipeline and early momentum is it's partly because, like I said, we have a good product and a good vision, but it's also -- because we're in the right position, and people give us the credibility to do this. We've been connecting people to all these resources in a way that's scalable and neutral, and the agentic problem is pretty similar. I mean it's different protocols and how they speak and some of the development tools are different, but conceptually, they think of it in the same bucket, which puts us in a good position, I think.

That's one thing I was going to highlight as well, to your point, Gray, about how we cut through the noise is the first point that Todd talked about in our differentiation is our distribution and our footprint right now with over 20,000 enterprises that already trust us as their provider to secure identity for their humans and their service accounts. And for those conversations, these customers are going to look to us first as the natural partner for them as they think about how they secure agents in their model as well. And so we really had very engaging conversations across the board on this. And because we're responding so directly to what we're hearing these customers need, we've had great success in turning that into pipeline. And so that's why you hear some of the commentary we're sharing today.

Okay. I see the Fatima back. Go ahead.

I apologize for the kerfuffle earlier. Todd, this question is for you. It's a strategic question. I know you've made the choice to offload professional services to some of your DSI partners, but it's an interesting dynamic we're seeing in the broader cyber space and even with larger tech companies that are actually leaning into services on a more direct basis. So I'm wondering if there's still an opportunity for you to maybe take a more strategic and architectural stance as it relates to building and defining strategies around a agentic identity cybersecurity architecture. So just curious about that dichotomy because you've decided to step away from it, but all your peers are kind of leaning more into it.

It's the great irony of our industry right now. We're going to automate all the jobs except for the forward deployed engineer. We need people to do that, right? And so we're doing -- our services team is evolving into that architectural over, giving the overall high level of consulting and helping the GSIs get enabled to do that and then do that on their own. That's exactly where we're going.

Think about it as we're not getting rid of our services. We're repurposing them so they can be in this architectural consultative type role. And then the GSIs can help us just get the scale. Because overall, there's -- there needs to be way more capacity to do Okta work in the world, and then we need to improve that and increase that and that's what this move is try to facilitate that while at the same time making sure the thought leadership and the architecture and the strategic stuff can still be done by our the core of our team here.

Also keep in mind, it was a decision to try to get the partners sourcing more business for us. And if you remember some of the comments we had earlier, we talked about partner source ARR in Q1 did really well. And part of pipe gen in the quarter also did really well. And so it's only 1 quarter, let's not get overly excited one way or the other. But it's a nice first data point for us to suggest that the strategy is the right strategy to go down the path of. And obviously, we'll update you guys as we go through the balance of the fiscal year. But that was also another reason to do this. And we see these early data points that are suggesting that it was the right decision.

And just one clarification for the way you frame that question is I wouldn't, we wouldn't describe it as we're stepping away from services. As Todd mentioned, we are focusing on the high-caliber work that you described with our customers and partnering with the GSIs to give us the scale, as Todd mentioned. So we're very aligned with the scenario that you identified.

Okay. Next, we're going to go to Gabriela Borges at Goldman Sachs.

I have a different Glasswing question. Todd, when you and your R&D team when you got hold of some of these next-generation models, what are you doing internally either from a vulnerability management standpoint or from an R&D road map standpoint? And Brett, the follow-up here is how do you put the right guardrails on your insurance costs such that you don't find yourself spending on tokens inefficiently?

Yes. So we're -- like everyone else, we're using these models. We're testing our own stuff. We finding some interesting things. But I think what people miss is that there's a lot of 0 days out there. And we may debate how many more we find with these new models, but it's not taking the number from 0 to 10. It's not 0 to 1. It's -- there's many out there. And so everyone has to have guardrails in place and everyone has to have capabilities in place to defense fast patching, multilayer defense. So we're no different. We're putting those guardrails in place in our products and our processes, et cetera, et cetera. The cost thing you're talking about is real, the inference costs and the AI tooling and what it's driving in terms of expenses. And I think you're going to see at Okta, and then over the whole industry over the next 6 to 12 months, you're going to see a little bit more scrutiny in terms of what are you getting from all this, the inference cost you're spending? How is it translating, which is not surprising given the amount it's rising across the industry. And we're going to come out the other side with more balanced ROI-driven investment portfolio of how we spend these things. And we're optimistic about how it's going to work out very well for us.

Yes. I would just add, remember, one of the, the #1 thing we've talked about for years has become one of the most secure companies in the world, right? So it's still priority #1. And this is just another tool for our security teams to try to achieve that goal, right? So just like Todd is saying, we're going to prioritize it and develop an ROI and all that good stuff like any other investment but it is still in service of that goal of becoming one of the world's most secure companies out there.

Yes. In that example, it's not limited to the Glasswing, but also ChatGPT 5 cyber, and we continue to make those investments.

Okay. Next, we're going to go to Rudy Kessinger, D.A. Davidson.

Congrats on the quarter. I'm curious as how you are approaching pricing some of these agent deals. In terms of the number of agents, we've heard in some few conversations. You guys are doing deals where basically the contract is for an unlimited number of agents. The good thing is in those deals, I'm hearing that the spend is very, very high relative to your existing spend and other products. But the risk there is what if the customer doesn't get to unlimited agents, so there's downside renewal or other things that could happen. So how are you approaching that dynamic with customers in factoring in the contracts?

There's no unlimited. If there is unlimited, it's time bound. So there have been some deals where we've done like a year, and then it's like we're going to figure out after a year what the -- how the use case really unfolded and how to snap it back to the kind of normal pricing model. But there's no -- it's not unlimited in the sense of time and volume. But I think that's just because it is an early market, and there are some uses and some environments where there is more experimentation that's needed, and they want to sign a deal, we want to work them, and so we'll do maybe not a multiyear deal, but a 1-year deal in that fashion.

Okay. Next up, we're going to go to Ben Bollin at Cleveland.

You referenced a bit of a return to fundamentals in relation to, I think it was Mr. [indiscernible] question on Mythos. Could you talk about how this is influencing the core workforce CIAM and CIAM pipelines and the opportunity, in particular around CIAM maybe disintermediate some of the DIY Frankenstein solutions?

Yes. I think the CIAM impact of this is it's not as big right now as the governance and privilege and access management. I think That's, call that core cyber, core cyber hygiene and identity infrastructure, identity security. I think that's getting more pull-through at this point than the CIAM side. But I think the CIAM side is coming because I think a lot of agents and agenetic workflows right now are internal automation opportunities. But you're going to see better customer experiences, you're going to see better support experience. So that one is actually further along than some of the others customer support. But I think it's going to be a big pull-through for CIAM as well. And it's like you said, it's the pace of change and the pace of innovation. Once -- before your competitors have a better agentic customer experience, you got to get your experience it quickly, and you're not going to have enough time to really you're on, you're going to have to use a packaged solution. I think that will happen eventually.

At the top of the hour, we're going to take one more question from Jonathan Ho at William Blair.

You mentioned multiple times the stability that you've seen in sort of your sales workforce with some of the transitions that have happened there with the lower it, higher productivity and pipeline build. I'm just trying to understand how you feel relative to where your go-to-market is today versus historically? And can we see more benefit from this over time?

Yes, we feel very positive on the state of go-to-market right now. We spent a lot of time last year explaining our expectations of the impact of specializing on our buyers for IT security with the Okta platform and developers with the Auth0 platform. You also heard us talk about the importance of continuity and giving people time territory and time with their accounts and time to ramp into productivity. And you've heard over the past few quarters, we've shared our positive view on the improving trends in sales productivity and an AE retention, the inverse of AE attrition. So we feel very strongly that, that engine is where it needs to be right now.

Because of that, we added some selling capacity in Q1. We spoke about that last quarter. And we're continuing to lean into the model that we believe is working. So we're optimistic we can continue to see increased retention and increased productivity as people get more and more time within their territories and with the expanding portfolio of products they can bring to their customers as well.

I think we have the right team and the right organization to convert the use pipeline. We're excited about doing that.

All right. That's all the time we have. I appreciate it. Before you go, I just want to let you know that in addition to hosting on-site and virtual bus tours this quarter, we'll be attending the Evercore TMT Conference on June 3 in San Francisco, the Nasdaq Conference on June 10 in London and the FBN Virtual Technology Conference on June 10. So we hope to see it one of those events. Thanks.

Thanks, everyone.

Thanks, everyone.

Please welcome Okta's Vice President of Federal, Amy Johanek.

Hello. Welcome to Okta Gov Identity Summit. Thank you for joining us today. This is our fifth year hosting the summit, but this year marks a deeper milestone. For the past decade, Okta has partnered with you to secure federal identities, evolving alongside the government's highest security standards. That's a decade of building together and a decade of earning your trust. What that decade has taught us is simple. The safest missions don't choose between being modern and being resilient. Modernization and cyber resiliency are deeply intertwined and the common thread is identity.

From advanced governance and threat detection to moving to the highest national security workloads, we are extending the identity security fabric to where your mission lives. You'll see these innovations in action throughout the day. And more importantly, you'll hear from government leaders and strategic partners on what identity-first security looks like in practice.

Before we look at the agenda, I want to recognize the sponsors who made today possible. Thank you so much. Now let's look at our day. We'll kick things off with Okta's Deputy Chief Security Officer, Charlotte Wylie. She'll detail how we are elevating your mission requirements into a truly secure operating model. Following that, I'll be hosting several conversations focused on reframing identity in Zero Trust posture as the foundation of mission agility. Later today, Okta's Director of Defense Intelligence program, Sabrina Lea, will explore identity and distributed environments. Then we'll have Okta's Senior Vice President and General Manager for Okta for AI Agents, Harish Peri, take a look at the future of agentic identity. And to close our day, former Commander of U.S. Cyber Command and former Director of the National Security Agency, General Paul Nakasone, will lead a deep dive into the wave of change driven by AI and other emerging technologies. It's a full day designed to give you actionable insights.

So to kick us off with a vision behind today's summit, please join me in welcoming to the stage, Charlotte Wylie.

Thank you, Amy. What a tremendous commitment to agency's modernization journey. In those 10 years, we've watched you expand across every identity, every use case and every resource. So whether you walked in today from a digital transformation office or fraud investigation unit or a cutting-edge lab, we've all been operating under the same principle. Identity is security. But here's the question that we now need to ask ourselves. How does your strategy hold now that your digital workers have shown up? For decades, identity was straightforward. You logged in, you have permissions, you did your job. Identity determines who access what, when and why. The control and visibility required were universally understood by the teams managing it.

Never trust, always verify. One entity permission enabled thousands of citizens to receive their benefits. One role certification meant that entire agencies could operate with confidence. Every mission-critical function was built around it, every decision, action and outcome traced back to identity. Then your new coworkers arrived. The access being requested isn't for a person. It's for AI agents with pervasive intentions. The permissions needed are no longer tied to a role but a purpose, unconstrained by title or department. The governance applied through periodic reviews can't be applied to unknown or known agents whose identities, access and privileges are inherently unmanaged. Managing agentic identity demands a blueprint. I'll come back to this in a minute.

Many of you in this room have been building towards this exact moment, applying Zero Trust principles, prioritizing phishing-resistant MFA and tightening data sharing controls. That work is the foundation. We're here to talk about what goes on top of it. As an identity company, Okta's concern starts before deployment. We see how agentic AI extends the attack surface, accelerating the buildup of identity debt. Every agent connected without governance, every unmanaged token, every over-permissioned bot, it all compounds the risk. But we're not asking you to chart this journey from scratch. And we see this reflected in your own directives.

The latest guidance on accelerating the federal use of AI rightly encourages agencies to scale the tools you already have for AI governance. All while organizations lean into agile acquisition to ensure secure cutting-edge tech reaches our war fighters faster than ever. We believe the identity security fabric already securing your human identities, workloads and applications, is the single control plane that can also be used for agentic identities. You get a unified approach while strengthening protection, end-to-end security needed to safely leverage AI across every use case and resource.

But let's be honest about where most organizations are right now. Instead of relying on enterprise-grade methods for securing AI agents, most organizations are using authentication protocols that expose highly privileged secrets. It's like using a residential lock on a federal building. It works but they're not fit for the job. These legacy approaches fail to provide standard centralized policy control, compromising the auditability and oversight required for enterprise security. And what makes it harder is agents don't just log in. They appear everywhere. They connect to everything and they act on their own. Which means that the strategy that you've relied on for identity doesn't hold. So you have to ask, where are my agents? What can they connect to and what can they do? Those 3 questions deserve a real answer. And this is a blueprint for secure agentic enterprise.

Instead of building a bespoke plugin or a one-off manifest, imagine a single standardized way for agents to connect to any system. So developers, the ones that are automating multi-step government service transactions for citizens or detecting payroll anomalies, helping workers process controlled and classified information, they spend their time building capabilities, not plumbing integrations. Instead of building a new physical key for every door, imagine a universal key system, one that every agent can use, every system can trust, and every admin can control. That's the principle behind a centralized approach to agent security, leveraging vaulted credentials to help ensure that an agent's identity is not exposed even whilst it's in use.

Even before we reach peak agentic where all software is inherently AI, we've already moved past that binary choice of whether to connect. The key question is control. When an agent is taking action, is it operating within its mission parameters? Or is it stepping beyond what it's been explicitly permitted to do. The consensus that we're hearing from you is that agents can't be fully autonomous. And this is where the governance kicks in. You want to treat agencies like first-class identities, not just connections. You need an automated kill switch that stops rogue agents in their tracks. And CISOs need the control and visibility that we are duty bound to protect. There's a lot within a single unified control plane, and you'll get a deeper dive on this later today.

In this era of escalating threats, the security provider that you choose must be as unshakable as the mission itself. You need to know that the fabric connecting your force is built around the same rigor that you expect of your own systems. And that difference matters because federal technology leaders and security innovators share the same mandate, impact at scale, sustain hardening, battle-tested. That's nonnegotiable. That is the duty that we have. The relentless pursuit of secure, scalable identity is exactly what we have been working towards for the last 2.5 years, the Okta Secure Identity Commitment.

The Okta Secure Identity Commitment is our pledge to secure identity in the age of AI and whatever comes next. It's built on 4 pillars: secure products, hardened infrastructure, customer best practices and industry leadership. This is our long-term promise to secure our enterprise and build secure products for you as AI reshapes the digital landscape. We've been solely dedicated to securing identity for almost 2 decades. And with your most critical use cases in mind, I want to zero in on how this promise mirrors how your missions operate. It is anchored on accountability because we believe security is an operational commitment. Our security is your security, and we can prove it. We hold our internal people, processes and technology to the same rigorous cyber threat profile as our customer-facing environment, holistic inside-out security.

Operational resiliency is the backbone of all of this, building corporate infrastructure that actually holds up to the pressure. Our Zero Trust approach to security is identity-first security. As Customer Zero, we secure our own global infrastructure with the same products that we deliver to you, from passwordless rollouts to self-service governance. Think about it as our own OIG audit. We stress test our solutions and find and close gaps, ensuring that the hardened result is what you receive. This isn't about just a testing ground for our products. It's forming a framework for your own Zero Trust implementation.

We've updated our Security Technical Information Guide to include specific hardened guidance for nonperson entities, providing a standardized framework to secure automated identities and deny adversaries a foothold in your network. We've launched our threat intelligence capability to produce advisory and in-depth research for the world's largest threat schemes. From exposing nation-state facilitators using AI-enhanced tools, to place operatives and engineering roles, to identifying illicit earnings that are being flowing back to hostile regimes.

And this is where it converges. The cost lever, preventing incidents before they happen and the risk lever, reducing the attack surface systematically. These aren't just security metrics. They merge into a single truth. Agencies that deliver identity-first security protect missions, and they accelerate them. But accelerating mission surfaces the real challenge that you're facing. It's not lack of innovation. Your teams are innovating at scale. The real pressure is interoperability, the friction of pulling autonomous systems, legacy infrastructure and compliance into a coherent operating model without slowing down.

That's the power of flexible SaaS. Flexible SaaS means identity adapts to your mission, not the other way around. It's one identity fabric governing everything: humans, agents and legacy systems without forcing you to rearchitect how you work or sacrifice security for speed. Flexible doesn't mean loose. It means configurable. It means a civilian benefits agency and a defense logistics command can both deploy the same identity fabric, but tuned to specific classification level, their compliance framework and their mission tempo. One configuration for citizen-facing passkeys and scoped agent tokens, the other for CAC-based authentication and air gap workflows. Same platform, same security commitment, different mission expressions. This flexibility is what allows your defense to evolve as quickly as the threat landscape. That's identity-first security and it's the vision that we're building together. An identity fabric as resilient, battle-tested and mission-focused as the agencies we serve.

I asked Okta's Federal Chief Security Officer, Sean Frazier, to join us and bring some of this to life. What you're about to see is a tool that can defend your Okta tenant from bad actors. We're talking about an adversary-in-the-middle phishing campaign, the kind likely targeting your admins today.

Sean, the floor is yours.

Thank you, Charlotte. Good morning, good morning. As you can see, I'm going to tell you something you don't already know. As you can see, identity attacks are on the rise, both from the perspective of being more sophisticated as well as being higher volume. Attackers are using AI the same way we're using AI to drive down cost and to increase capabilities. When Charlotte talked about the Okta Secure Identity Commitment, one of the core pillars of that was to help our customers with their security journey. And to that end, we've created a tool for our customers to navigate through this called the Threat Exposure Assessment, or TEA, because who doesn't love a good acronym.

The Threat Exposure Assessment is a security-focused health check that analyzes a tenant configuration from password policies to network controls to help ensure the customers are optimally protected against future attacks. Here are some examples of configurations that the Okta Identity Defense team have observed during real-world incidents to highlight some of the issues identified in the TEA report. Let's look at the demo. We grouped this example configuration into 3 phases of the authentication pipeline: before the login, during the login itself and after the login. Our TEA report recommends a defense in-depth approach across this entire life cycle. For before the login, in this scenario, ThreatInsight was enabled but stuck in audit mode. The admins wanted to observe the logs before putting into enforcing mode, but it fell off the priority list as things tend to do.

On the networking side, they're only blocking some IP address ranges for attackers networks that they've known because they saw it in the course of an event. They're not using some of the advanced features like geolocation. For the login itself, the user base was familiar with SMS, OTP, onetime passwords. So they enabled those initially, but these low assurance factors are easily phished. We often hear from Okta admins during an incident, they have a backlog or a road map item to migrate to phishing-resistant factors, but life got in the way and they just were never able to do it. For after the login, in the name of good user experience, the tenant had long configuration global session policy token issuance. To make matters worse, they never enabled end user notifications when end users would discover that something was going on with their account. So the end users were never able to let the Okta admins or the security team know that something was going on, and they're your first line of defense.

For tenants configured in this manner, there are multiple identity attacks that could cause headaches at a minimum or at a maximum lead to a security incident. There was a 61% increase in brute force attacks last year based on data that we've gotten from the Okta Threat Intelligence team. With these low assurance factors like SMS or e-mail OTP and when they're not enabled, there are a variety of attacks that can manifest themselves, things like account takeovers, credential harvesting, those types of attacks. It doesn't take a really sophisticated actor to launch a brute force password attack or a password guessing attack or credential stuffing attack.

And more advanced attacks, such an adversary-in-the-middle can be used to bypass the low assurance factors like SMS and e-mail onetime passcodes. In the adversary-in-the-middle attack, a proxy server intercepts a password and the OTP in real time to authenticate with the legitimate site. By stealing the resulting session cookie, the attacker bypasses all the MFA requirements to hijack the account. This has become a lot cheaper for attackers to implement. With phishing infrastructure, a threat actor can take over an account and change the password or reset the MFA factors, and they can block the legitimate user from access to their own account.

Let's look at what the TEA report might recommend for the previous list of misconfigurations we discussed in order to mitigate these potential threats. Again, back to the 3 examples of the authentication pipeline. The TEA report creates and provides a lot of guidance and a lot of information for you, but I'm going to only focus on a few of those today. Before the login, TEA would recommend putting ThreatInsights into blocking mode. On the network zone side, anonymizing proxies should be blocked and the combination of these 2 controls will help mitigate against credential stuffing attacks. For the login itself, TEA would advocate for phishing-resistant factors such as Okta FastPass, WebAuthn biometric or YubiKeys. This helps protect the end user from phishing and adversary-in-the-middle attacks.

For after the login, TEA recommends setting up the global session policy expiration that aligns with NIST standards. Notification should be enabled so that end users can report suspicious activity directly to their Okta admin and their security team right from the phishing e-mail. And Identity Threat Protection or ITP session protection and detection should be enabled. With ITP, you get Universal Logout. Universal Logout can automatically be triggered to terminate sessions and revoke tokens for various cases such an end user reporting suspicious activity on their account.

Threat actors are evolving. They're evolving their techniques and their tactics, frequently changing them to avoid detection. But the good news is that Okta has released a number of features like ITP, Identity Threat Protection, that will help protect against these kinds of attacks. And the TEA report will help protect against these kinds of attacks and let you know exactly what to do in your configurated tenant. So the call to action today, reach out to your customer success manager, ask for a TEA report. You can also request this directly from your support ticket by opening up in your tenant.

As Charlotte mentioned, we also released the updated version of our STIG 1.1, which includes nonhuman entity. So please make sure if you haven't downloaded that and applied that to your tenant, do that now. Be aware of the pitfall, set and forget it. Take advantage of cutting-edge features and security features specifically that we released in the Okta product all the time. And don't wait until you're dealing with a security incident, be proactive and start today. Thank you very much.

This presentation contains forward-looking statements. We reserve the right to change the information in this presentation. More information can be found in our securities filings. Please welcome Okta's Chief Executive Officer and Co-Founder, Todd McKinnon.

It's great to see you all showcase. We're going to talk about our industry, and we're going to talk about our products. And in November, we introduced Okta for AI agents to the world. And it's our most important product ever, our most important product ever. It's simple on the surface. It's in the name. Okta connects your people to your technology, your customers to the technology they need to interact with your organization. And so it's Okta for AI agents. AI agents are the future exciting foundational technology and Okta for AI agents makes that connections for agents. And the response from all of you and the industry at large has been unlike anything I've seen in my career. It's the interest and the relevance of this product. And it's -- we've had hundreds and hundreds of meetings to talk about this product. It's been purchased by dozens of companies, and it's in production by several companies at this early date, getting real value securing and managing their AI agents, which is incredible uptake.

And it's not surprising because if anyone that's paid attention to technology, we know that the future is agentic. The future is agentic. And there's different takes on this. And I think it's important to understand how we view this to put the broader context of what we're doing and frame it up for everyone. People talk about agentic as a new thing. It's a new layer. It's a new set of capabilities. I see it differently. I think it's the future of all of technology. By the way, all of -- not just enterprise technology, but all of technology. AI agents and autonomous behavior of technology is where the world is going. It's going to change how we seek and find information. It's going to change how products and services are delivered to customers. It's going to change how companies are getting productivity out of their workforces, how they're automating things, how they're getting insights, how they're fundamentally rethinking the core of what they do.

And it's not like it's going to be delivered by one company or a set of companies. Everything is going to be agentic. Your existing vendors are going to overhaul their software to have autonomous agentic capabilities or they're going to be disrupted. Start-ups are going to have new agentic services and solutions. There's going to be existing categories change, categories are going to merge. There's going to be whole new categories of true digital workers. that are going to push existing vendors. You're going to build your own agentic systems. You're going to have -- create much better customer experiences. So it's a profound change.

In fact, I think in 5 years or so, we're probably not going to refer to agentic technology. It's just going to be technology. So we're talking about the greatest transformation of technology in my career. I've been working professionally for 30 years now. So I've seen Internet, I've seen cloud, I've seen mobile. And this is by far the biggest change. It's changing at so many levels. It can be daunting and overwhelming, but it can also be very exciting. And the people gathered here today are the people at the forefront that have to make this all work. And hopefully, you share this excitement with us.

With this new era of technology comes a lot of risk. It's not a surprise to security professionals and cyber professionals that there's a lot of trade-offs. There's risk and there's opportunities. And this is no exception. This kind of autonomy, the kind of access these agents get, the connections they make can lead to bad things. In fact, you're starting to see this pop up in the industry already. Anthropic released a very good report last fall, talking about a massive cyber attack that was perpetuated using the Anthropic models and Claude Code. And so this is a massive scale agentic system. automating work, automating software development, and it was used for a massive cyber campaign. And this report details what they found and some lessons learned about how to prevent it. And I think the biggest takeaway here is that these systems, while they're powerful, can be used for bad things. So we have to have a good concept of risk management and put the right controls and governance processes and controls in place to make sure it's secure.

The threat actors in this case actually -- as you would expect, Anthropic has a ton of controls in their models and frameworks to make sure that they can't be used for bad things. And the attackers in this case, actually socially engineered the model. They socially engineered the model to trick it and say they were a respected threat research firm using this for research capabilities while they were really using it to actually prosecute this massive campaign. It wasn't -- it was using the normal tools and techniques available to the industry hooked up to the model. So they weren't using any novel times of -- novel types of zero days or types of tools to actually perpetuate the attacks. It was just the fact that it was all hooked up to the scalable agentic framework that was socially engineered that kind of made it all work.

The other interesting thing about this is that throughout the process Anthropic -- and Anthropic published this, by the way, so we could all learn from it, and they could share with the industry some of these risks. But they also noticed that during the execution of this attack, the model was actually overly confident about the targets it was finding to try to attack if the attacks would work or not. So it was tricked, it was overconfident, all while under the guise of being massively scalable and massively controllable. So it's quite interesting. I suggest you take a read.

There was another interesting survey by a small company called Gravity that did a great job surveying you all. Do you all participate in these surveys ever? Someone calls you up and get your professional opinion about IT. I see a lot of heads nodding. This was about 1,000 people, and it was VPs of IT, directors of technology, CPOs. And the survey asked them basically about how their agentic deployments were going. And they noticed a couple of interesting things. The first thing they noticed was that almost 9 out of 10 people said there was already a security issue in their agentic systems. So this could be something as simple as an agentic system was overprovisioned for access. It didn't have the right visibility and controls about what it could do, 9 out of 10, which is quite high. And then only 20%, roughly 20% treated these agents in their agentic system with complete identity control. So identity is a first-class thing for these agents.

In the vast majority of cases, the agents were using reused API tokens, common access to systems that were shared across multiple agents. So there's no tracking and control and accountability for these agents when they were actually doing their work. So this is a problem for the industry. So I think what we need to do collectively and what Okta is focused on is making sure that as we all build this future, as we all build this future that we all know is powerful and profound, this future of agentic enterprise, we make sure that at the same time, we make it the secure agentic enterprise. It sounds simple, but we have to do both. We have to do both. This technology wave has a tremendous amount of potential. It's inspiring. It's exciting to all of us, but we have to make sure we put the right controls and foundational groundwork in place to make it secure as well.

And if you think about the arc of Okta, Okta is 17 years old. And I feel personally and the company feels personally very blessed and very fortunate to be at the right place at the right time through multiple technology waves in those 17 years. Okta was born out of the cloud. The idea was cloud computing and the adoption of cloud for every layer in the IT stack would require a new kind of identity system. Everything was outside the firewall, you didn't control the servers and the resources. There are all these SaaS applications. You had to have the best identity ever created to secure and control that. And Okta's early success was really born on the back of the cloud adoption. We helped the cloud be adopted, and we were also benefited from it being adopted at scale.

Then came the mobile revolution. Again, more devices, identity gets more important. Then there was COVID and work from home, identity gets more important. So through the arc of our history, identity gets more and more important in every technology wave. And this agentic enterprise, where every AI agent that is working with your employees and performing digital work, identity is more important than ever. So we are perfectly positioned. I mean who spent 17 years connecting people to technology. And now as we try to supplement those people with agents, who is perfectly positioned to do that. We couldn't be more fortunate, and we are not going to waste this opportunity. We're pouring all of our energy and effort and resources into making this agentic enterprise a secure agentic enterprise.

And one of our fundamental things we're doing is we're working closely with all of you. All of our customers that are on the leading edge of this and that have taken this product, Okta for AI agents and are working with us to build out the next set of capabilities and features in a way that will most benefit you. There's -- what's the right way to put this? There's a lot of hype in AI. There's a lot of hype. And I think one of the key things we need to do is make sure that the product we build here is directly linked to the concrete value and the capabilities you need now. So we don't spend 4 years building a science experiment. We build something that you can use now. And we're very lucky here. We're very lucky. We know what problems you have and what solutions that we need to build for you. And they all kind of center around 3 really important questions.

The first one sounds simple. What agents do I have? Every vendor I've ever talked to has agents. I want to build my own agents. Do vendors are saying they have agents and my people around my organization are adopting them. Where are they? Where do they come from? The second question is what can they connect to because that's the keys to the kingdom. Just like people, what resources they can connect to, customers come into your mobile app or website, what can they connect to? What your agents can connect to is absolutely critical. And the third thing is what can they do? So once they use that access, what can they actually do with it? So those are the key questions informed by our conversations with amazing customers around the world.

And it's very confusing, especially some vendors propose to answer some of these questions. Some vendors say other questions are important. Some vendors say they have everything covered. And it's quite daunting. I think it was summarized nicely by a great customer of ours, S&P Global, Seth Fox is the CTO there. And I was sitting talking to Seth, and he said to me, he said, it's very -- there's a lot coming at us, Todd, and it's very overwhelming. So it's like what you need to do is just write down a reference architecture, like just summarize the landscape for us and tell me where you fit in, where the next vendor I'm going to see fits in. Compare what you're doing, what we have to what my friends company has, how does it all fit together? So that's what we've done, informed by hundreds and hundreds and hundreds of conversation along with work with our partners in the cyber ecosystem, partners in the application and technology ecosystem and most importantly, conversations with customers like you.

We're excited about this blueprint for the secure agentic enterprise. It is what it says. It's a blueprint. It's not a product. It's not a -- this is an Okta thing, it's an industry thing. We're putting forward and saying, this is the reference architecture. This is how the ecosystem together could build not only the agentic enterprise, but the secure agentic enterprise. And it answers these core 3 questions. Where are my agents? What can they connect to? And what can they do? And you can see in this blueprint, the capabilities on how you detect agents are broken down in logical categories, everyone from integrations with agentic systems to edge browser-based detections to endpoint network. We all have gateways and all the gateway vendors are helping out here. And then how do you assess risk of those agents. It's all -- the capabilities are outlined in this blueprint. And then one thing about -- I talked about Okta being perfectly positioned to help be the backbone of the secure agentic enterprise because we've spent 17 years connecting people to technology, and we're very good at that.

But we also know that agents are different. the protocols are different, how you build them is different, how they connect to things and how the interaction works. So that's all prescribed in the capabilities around what they can connect to. There's different capability. No person has ever logged into an MCP server, at least not that I know of. But agents do and agents also log into SaaS and how do you connect an agent to SaaS? Is it OAuth? Is it the API with a token? Is it -- how do you -- what is the catalog of things that are possible? What are the best practices? And how do you keep it secure? And then, of course, agents connect to agents, and that's a different set of protocols. And then you have legacy, you need to get these agents data from legacy systems and those legacy systems don't have OAuth, and they don't have these fancy rest APIs so that those are service accounts. And you have to vault credentials and it just orients the whole conversation in a way that makes sense of it all and lets us get to the business of making our -- not only our agentic enterprises, but our secure agentic enterprises.

And finally, we talk about what can they do? This is about fine-grained permissions. And this is about do you do the enforcement at run time? Or is it agent set up? And then what's the life cycle of an agent? When is an agent created? And how do you manage it? How -- people simplistically say, oh, it's like a person. And other people say, oh, no, it's like just a privileged account and a service account, but the answer is it's somewhere in the middle and the blueprint tries to lay that out. When do you get a human involved and how do you track and log things? So these are the capabilities. And there's a ton of details behind this and the flows and how they work together. I don't mean to gloss over the complexity. If you've ever looked at a blueprint, you know that on the first couple of pages, it's very -- it's like the site and like what materials are going to be used and who the contractor is and how it's definitely going to go over budget.

Not that I have any scarring about that. But then you flip through and it has other pages of all the details, the subsystems, the plumbing, the electrical, the foundation, the site details of the outside site plan. And it's the same thing true here. It's how these things fit together is prescribed in the blueprint because there is a lot of important capabilities here under the covers. Now this is a blueprint for the industry. And I don't purport to stand up here and say that Okta has a product that solves all of these things. It's definitely going to take a village to make this all work together.

But the reason I started my comments by saying I thought that Okta for AI agents is our most important product ever. It's because the potential of the agentic enterprise is so profound. And this Okta for AI agents has such a core place in this ecosystem, has such a core capability. It's connecting your agents to all of your technology and controlling how they connect and what they can do. So it plays a very important role. And now to talk a little bit more about that in details and the detailed capabilities here for Okta for AI agents is my amazing colleague, Shannon Duffy. Please welcome Shannon.

Thanks, Todd. So Todd just showed our amazing blueprint for the secure agentic enterprise, but I could just show you some product. And I am so excited about Okta for AI agents. This is the first and best implementation of the blueprint, and customers are already using it to see amazing success. And we're going to show you how that blueprint helps you answer those 3 questions. Where are my agents? What can they connect to? And what can they do? As we like to say in cybersecurity, you can't protect what you can't see. So let's jump into the demo and take a look and answer that first question, where are my agents? Okay.

So Okta helps you find agents in 2 ways, both the ones you know and the ones that you don't. Let's talk about the ones you know. So here we are in the Universal Directory, and this is your central system. This is your single source of truth. It's your agent inventory. And at Oktane, we showed you how you can register those AI agents. But we're taking it one step further. We're taking everything you love about the Okta Integration Network, the standards, the breadth, the flexibility, and we're extending it. We're essentially making it your agent integration network.

Now the thing about these agents is they can't live in silos, right? They need to be connected to the tools you use every day. That's going to make them more valuable and more powerful. So here, you can browse the agent catalog, and you can see all of the tools that your company is using. And as your team starts working with new platforms, those are going to be here as well. The point is we are focusing on identity, so you can focus on innovating with technology and you never have to worry about vendor lock-in. All right. But what about the apps you've already configured for your human users? Well, you can go right from the app integration page, and you can see a new tab, AI agent import. And with Okta for AI agents, you can import those agents and all the metadata with one click. So you're going to get the name, the title, the description. And the important thing to remember here is identity is managed separately. So if an app gets compromised, security is going to be centralized, right in Okta. Okay.

What about question number two? What about the agents you don't know about? Well, people in your company, I guarantee you, right now, as we sit here, People are spinning up agents in your company, and you need to know about them. So this is agent discovery. and agent discovery automatically flags OAuth grants. So when an agent is connected to an enterprise application, you are going to get notified. So you can see the scope and you can see the blast radius. But most importantly, you're going to get a remediation plan to take action. So you can go ahead, you can register the agent, assign a human owner and baseline security policies. Now the important thing to remember, this is not a onetime process. Discovery is running continuously in the background, so you can find all your agents, both the ones you know and the ones you don't. All right.

So now you know where your agents are, let's answer that second question. What can they connect to? Well, it starts with MCP servers. So you can model agents, but you can also model MCP servers, and you can search a catalog of all the ones you might want to use. But connecting the agents to MCP servers directly, that can be risky, which is why we're introducing agent gateway. And the first use case is managing access to the virtual MCP servers so that you can select exactly which tools and scopes can be accessed. And with Okta for agents, you can securely secure those third-party coding agents like Cursor and Cloud Code. But what about everything else your agents need to integrate with? Well, today, we have 3 ways to manage those connections, Okta Authorization server, API keys and service accounts. But now we're adding 3 more ways to integrate agents securely, Okta Virtual MCP servers, third-party MCP servers and ODIC accounts, OIDC apps. No custom code and no direct path from agent to MCP servers and security is centralized in Okta. Okay.

Question number three, what can they do? Well, you need to establish exactly what agents are accountable for and you have to cut off access if it goes wrong. So here's the governance dashboard. And you can see access on an ongoing basis to what these agents have access to down to the scope and tool level. And you can review their access to make sure they have access to everything they need, but nothing they don't. But if what if an agent goes rogue? Well, you need a kill switch. And with Okta for AI agents, you can trigger universal log out if an agent starts accessing things that shouldn't. It's automatically going to revoke the tokens and deactivate that agent access. So now you know what agents can do, but you can cut things off if something goes wrong.

And as your agent footprint changes, you are always secure. We are evolving right there with you. Okay. So you just saw Okta for AI agents in action and how it helps you answer those 3 questions. Where are my agents? What can they connect to? And what can they do? These are just a few of the ways we are helping you become a secure agentic enterprise, and this is how Okta secures AI.

Back to you, Todd.

Very cool. I love seeing that come together. Thank you all that have been involved in the early access of Okta for AI agents. As I said, it's really valuable to inform the product direction and help shape our view of the future based on substantive leading-edge conversations with real powerful organizations that are trying to build these agentic enterprises. And the team has made a ton of progress. And the most exciting thing at all -- the most exciting thing out of everything I'll talk about today is the fact that this product is going to be generally available to all of you on April 30. So that's amazing. You're all going to be able to get your hands on this. The world is going to be able to start going from agentic enterprises to secure agentic enterprises on April 30. So nice work, everyone that's worked with us on this and the teams at Okta that are building this together. So good job on that.

Okay. So we've talked about the blueprint for the secure agentic enterprise. We've talked about Okta for AI agents. And now we're going to ground it in one of those real concrete conversations with an amazing company, an amazing leader at an amazing Okta customer. And this is a conversation with John Roese from Dell. John, come on up here.

So let's start. Put the -- I want to put Dell in the AI context. So how do you think about the industry, the Dell's place in the industry, how the industry is changing? How do you -- where does Dell fit into there?

Yes, we're fairly central because you cannot do AI with the infrastructure of the past. And so our business is building out the IT infrastructure of the world, compute, storage networking and all things associated with it. And that's been good for business. We're doing very well. We are finding ourselves in an entirely new world. However, just building infrastructure for someone else would be difficult because you wouldn't know what to build. And so a couple of years ago, we made the decision to be customer zero that we would be the early aggressive adopter of this technology. And I took over -- I've been the CTO for quite a long time, but I took over as the Chief AI Officer about 2 years ago. And in that 2-year period.

Was there another person? Or is it a new position?

There was a person there for a very brief period of time that attempted to build consensus and didn't work, and then we decided to go top down. We tried bottom up, didn't work. We went top down when I took over, which fundamentally launched our journey, which was if we're going to build for this new space, we sure better understand what this space is as a firsthand participant in it. We could spend a long time talking about our journey, but the punchline is after 2 years of a very disciplined -- if you go look at my YouTube channel and listen to me talk, you'll understand we are somewhat militant and we are very focused on doing this thing in a very structured way that actually gets to outcome, gets to ROI.

But after 2 years of doing that, we just had our financial reports for the second year that we have done this more aggressive adoption of technology, but also changing our people and the process and redesigning our company for this era. Now we have 2 years in which something happened that hadn't happened in 41 years before that. And that was our revenue grew dramatically, first year, about $10 billion, second year, about $20 billion. And at the same time, our costs went down. We have never seen that happen. Every time revenue went up, costs went up with it. But when you redesign for the AI era, people, process, technology, funny enough, you decouple those 2 because the unit of work is no longer just a human being. It's an augmented human being or an agent. And that gives you tremendous leverage to grow your business and actually improve your cost structure at the same time.

Doing that is nontrivial. It required us to lean in to be as bleeding edge in terms of thinking as possible, but also very pragmatic about making sure that we didn't break the business that we did things that matter. And so one interesting statistic is for all that progress, we never used a single agent yet. where we built our first autonomous agents almost 2 years ago, but the ones in production are pretty minimal right now. However, given the fact that we've had that kind of impact without agents, we are extremely excited about this greater shift to autonomy, the kind of projects we can go after. In fact, we believe that AI can only be applied to a process and the only processes we could go after with first-generation tools are very simple processes that are very much tied to human work behavior.

When you move into the agentic world, you can go after the complex processes. You can go after composite processes, you can go after autonomous processes. And that opens up just a gigantic surface area that we're fairly comfortable is going to define productivity for the next -- probably the next decade at least.

When you think about the agentic technology stack, what are the key technologies? There's process, there's change management. There's strategic direction that has to be in line. And then there's the technology enablement. You mentioned a bunch of the stuff was done without even agentic. What are the key parts of the agentic?

Yes. You and I talked a while back, I think we -- I don't think we had published it yet, but at the end of last year, in October, we -- after working with these technologies and kind of thinking about what would we have to put in place to do this, we wrote it down, interesting enough. We have an internal set of agentic standards. And they're not high-level hand-waving stuff. They're very specific. And in fact, they included things like we decided all MCP servers would be centralized because at the time, MCP is just too risky to use without putting it in a safe space. That's a fairly straightforward decision. We now make that part of our architecture. We made decisions about having 2 kinds of agentic platforms, ones that we wholly own and operate, which we call inner ring, which are our control points and our ability to do things very specialized for Dell but then it would be surrounded by outer ring agentic platforms that existed within our partners and SaaS services, but we decided these would not be separate ships in the night.

They would be part of one topology under one architecture. And probably the single biggest decision we made, which is what we were talking about, which I kind of shared with you guys and maybe gave you some encouragement to go on the journey you're on is that we decided that every agent in the world that does work on behalf of Dell would carry a digital identity issued and operated by us. I don't care if the agent is a third party. I don't care if it's in a SaaS provider. I want control. I authorize it to exist. And the reason I wanted to do that is because I know agents will track where work goes on and work goes on in more than just my data centers and my core businesses, but yet I want to be able to have control over how that work is happening.

And what we realized is I can't control the underlying infrastructure decisions because those are third parties in many cases. I can't maybe even control the data APIs as well as I could. But if I control identity, I can do things like a kill switch. I can make an agent go away if it behaves badly, even if it isn't running on my infrastructure and fully under my control. And so that stack that has now formed, which is very much a modern AI factory underneath it to provide the engine to basically run it efficiently and scale it, what we call a knowledge layer, which are the knowledge graphs and the graph databases and the RAG systems that basically enumerate data that agents can use. And then on top of it, a control plane. And that control plane includes registries, but it fundamentally includes identity and access management and authorization.

And so that stack now is real. It is published. In fact, just recently, we started to provide it as a pseudo RFI to all of our partners to say, okay, you want to do business with us. This is our set of rules. And to my knowledge, we're the first ones to do that. We think the industry ought to take blueprints and use blueprints because everybody agrees on kind of the meta architecture. we can actually all line on getting it built because it doesn't fully exist yet.

Yes, it sounds simple. I'm an identity guy. You guys early on made the decision that agents have to have first-class identities. We saw the survey I mentioned earlier that 22% of -- only 22% of companies are managing agents as real identity things. And it's good to hear that you're seeing success there, but it's a subtle thing a lot of people don't get to. They try to treat them as more like software and their scripts and their service accounts, and it's a very profound thing that we can make it happen together. So when you talk about agents, you guys decided to -- the primary -- the platform and the use cases, a lot of them are internal. How do you think about agents operating internally for your enterprise versus agents outside your enterprise accessing your systems and the internal, external trade-off there?

Yes. I would say our first thoughts about agents over a year ago, we had this belief that we could build one platform and kind of run all the agents on it. By the way, we have a bias. We really protect our intellectual property and our data. I am very hesitant to let black boxes of magic touch my data. So I like doing things that I can control, whether they're in my data centers or in systems that I help design the architecture for a provider. But the bottom line is we very quickly realize, as I said, agents track. They are an entity that does work, and that work can exist in many places. Some of that exists in things I fully control and some I don't.

And so early on, we did pivot to have this 2 concentric ring model where there would be platforms that we fully controlled, and there would be platforms that we didn't control the platform, but we could control the agents on the platform. And that's where identity and access management became kind of this universal substrate. I think interestingly enough, I will tell you, just to give you some industry dirty laundry. We don't have full consensus in the industry about what even an agent is.

Stop, John. Stop. Breaking news.

Breaking news, agent washing, but it's even worse because some people believe agents are a feature of a model that's behind the black box of magic of the API, and you don't need to understand it. I completely disagree with that. We believe agents are software systems that can do autonomous work, and they do use large language models, but they also use knowledge graphs and other types of data expressions. They have a tool use interface today, primarily MCP. They have inter-agent communication with protocols like A2A. That is a system. And we're kind of -- the one thing we're struggling is we haven't quite got to consensus about which of those is the right answer? Is it a feature of a model? Or is it a software system that does work? I know where it's going to end up. I'm 100% confident the second is the right answer, but that creates tremendous confusion for people. It also makes it very difficult for me, interestingly enough, as I want to have ubiquitous identity and ubiquitous control, if you believe an agent is a black box of magic hidden behind a master account that is owned by a provider, it's very hard to reach into there and do authorization for what appears to be a knowledge graph that can I got to pull it out.

And so we are generally treating most of those companies, and they are our partners in this extended ecosystem, and we're deprecating them. They are not agents to us. They are just tools and the intelligence and the reasoning will happen on our side until they expose that underlying capability. So it's -- I would say, most of the enterprise ecosystem. We have 650 start-ups we're working with building enterprise AI stuff. They have all largely gravitated towards these have to be composable systems. They're software entities. They work together. They have this kind of composable architecture. That's good. Some of the bigger providers haven't quite got there yet. And so we have to figure out how to work with it, which is why it's so important in your framework that you don't just assume everything is a first-class agent. Some agents might not actually be expressable as agents because they're behind the firewall or unexposed to you. So treat them like a tool and then control the tool use access, which is another authorization tech.

It all blends together.

Exactly. Yes.

So you're the CTO, so your job is to predict the future. So tell us what's going to happen.

Well, here's the first thing. We have something in Dell called the 2-year rule -- sorry, Todd, we treat all AI decisions of having no more than a 2-year lifespan. And the reason for that.

It's good for us, we have to work our a** off to keep maintain your business.

You have to work in your business. You win, you get us for 2 years, and then we reevaluate because honestly, we can't predict that future. But what I will tell you is the one thing that is absolutely certain, and you kind of mentioned it in your keynote, we are in a period where autonomy is becoming the actual characteristic of these systems. It's not the technology by itself is that the technology can operate autonomously. It will operate in low-grade autonomy like a better tool or it can operate in high-grade autonomy like a full-on digital expert worker. It is inevitable that, that is coming and is happening. And so the biggest shift that we can see is we have to prepare for that. We have to rethink work. We have to rethink our infrastructure. The other thing that's interesting and an infrastructure guy is years and years ago, it's like 6 years ago, I'm on the record of saying something along the lines of there will come a time where the.majority of your IT infrastructure is actually in service of AI outcomes. And more importantly, when that happens, you will have to redesign your IT architecture to treat AI as the primary workload, not the secondary.

We are actually at that time right now. But I will tell you, the majority of the world's infrastructure was built before generative AI even existed. It was architected. We continue to apply architectural principles to it. So one of the biggest predictions is not only is this coming, but it is going to force a complete rethink of all the dimensionality of our IT environments, not just so that we can add a new capability, but so we can actually optimize the primary purpose of our infrastructures and IT systems to actually enable this autonomy. That is a big deal. If you read what I just said clearly, you're going to have to rethink everything. In fact, we encourage customers today that if you have an existing infrastructure and IT strategy, this is a very good time to pause because you probably made every decision in that list before generative AI ever happened. It's a great time to stop to get educated to rethink everything from identity to access control to telemetry to infrastructure choices to where the AI is run and where the data lives and what those data layers look like.

That is probably a terrifying prediction because it means we have a lot of work to do, but it's also incredibly exciting because if we optimize for autonomy, this thing accelerates. And when it accelerates, I will guarantee you the result is dramatic impact on GDP, on lifespan, on health care, the amazing things that can happen if we get this right by doing it securely will happen quicker, and that's a very good thing for all of us.

Yes, very well said. I'm very excited. The way I think about it is there are 1.1 billion knowledge workers in the world. We spend about $30 trillion, and they produce about $65 trillion, $70 trillion of wealth. So how about we cut the cost by 10% and produce twice the wealth.

Exactly.

That would be a pretty amazing future for everyone. So thank you so much, John, for being a customer and trusting us with helping you build this -- using Okta for AI agents to build this identity layer in your platform and be the foundation for the Dell Secure Agent enterprise.

Yes. No, thanks for having us, and we're super excited to see this go GA. We've been on the journey with you to build it. And I think if you haven't looked at it and see what's going on here, this is a pretty important kind of very early real example of how to do this stuff. So congratulations.

All right. John, thanks. I think this blueprint is really going to clarify a lot of things and make it easier for all of us, whether you're building technology as a vendor, whether you're implementing technology as a company, whether you're a cyber -- member of the cyber ecosystem to rationalize how it all fits together and more importantly, help us all move forward more safely and more quickly. And I'll show up a QR code in a minute. You can get a link to all the details behind this. We're really excited to work with the whole ecosystem and community to build this and keep working on it going forward.

And I think the big headline here is that Okta for AI agents is generally available on April 30. So if you're not using it already, make sure you reach out and learn about it and learn how it can help you build your secure agentic enterprise. And you can get all the information here. So we're very excited to help you secure AI. And again, thank you for being a customer. And if you're not a customer yet, I don't know what you're waiting for. We can take care of that. And thanks again to John for helping us out. And thanks again for Shannon and the whole product team and the marketing team for putting this on. And thank you very much, and enjoy the rest of the showcase.

Thank you for joining us today. Thank you for joining us today. Please join us in the foyer.

All right. Welcome, everybody. We are at the anchor spot of the conference and delighted to have Okta here with us today. I'm Meta Marshall. I cover networking and cybersecurity here at Morgan Stanley. We're delighted to have Todd McKinnon, CEO and Co-Founder here with us after a great quarter last night. So...

Thanks for having me. Nice to see everyone.

So Todd, it's great to have you here, not only after earnings that you reported last night, but just this is a critical time for the identity market, particularly as identity moves front and center in the AI enablement discussion. Just how are you thinking about what type of holistic identity solution the market needs in order to better secure agents? And just how are you designing towards that?

So first of all, when we talk about agents, I think some people I talk to think about them as a discrete thing that's going to be delivered in a certain way. When I think of agents, everything is going to be agents. I think every piece of what we think of SaaS now will be -- take agentic features, reinvented as agents, replaced by agents maybe. I think every piece of software built will have some agentic capabilities. So really -- we're really talking about the future of all of technology. Devices will have agentic capabilities, autonomous SQLs.

And so when we think about the potential of what we're doing with Okta for AI agents and Auth0 for AI agents, it's -- that's the long-term ambition. We want to be the identity layer, the identity infrastructure for everything. So what that means is simply put, it's -- a company would have use Okta as a system of record of how many agents they had, what they could do, how they're governed, how they perform. Right now, the product has a list of -- it's the key features that are resonating with customers is it has the ability -- it knows about what agents have been delivered by which platform.

So it can download agents and synchronize agents from Salesforce and Amazon and Microsoft, and it can give you a central view of all those agents. And then it can control what they can connect to and they can do that connection in a secure way, so you don't leak session tokens or leak API tokens. And the connections of these agents is really important because that's how they get all the context to make them super valuable. So that's -- it's a big opportunity. And we're really -- I'm blown away by the interest. And then in Q4, the actual sizable deals on the board was -- it was super interesting. Still early, a $3 billion run rate, product is still in early access. The Okta for AI agents is early access. Auth0 for AI agents is GA for about a quarter, but it's very exciting.

Yes. The identity market, maybe as we think of it more traditionally has been this best-of-breed market with distinct swim lanes. Does AI finally push us more towards the platform? And why do you guys think that you guys are in the best position to lead?

I think it does. I think -- but I think the linchpin of that is the, call it, the system of record or the registry. And that has -- if you can give that value to customers to give them this platform-agnostic independent neutral view of all their agents and let them control the connections, that's a very powerful position to deliver value. But that probably leads to more ability to cross-sell governance for people and agents and privilege for people and agents and core human identity probably makes it even having more. We're already seeing platform gravity with the multiple solutions we have with our identity products and this being a system of record for agents probably makes them more platform gravity. It's very early now.

I mean I think there's a lot of -- when I talk to hundreds of -- I've talked to hundreds of customers specifically about agentic and what their requirements are and what we're doing, big companies. And there is some spectrum of maturity from the most mature ones are -- have really thought through deeply how they can build an internal enterprise platform for agentic, including where it's going to run, how it's going to access models, how they're going to incorporate a system of record for identity into that, and they've really thought through strategically how that's going to all fit together.

But the other extreme is they're really -- it's really early and they're thinking about how can we control which prompts our employees are giving to the chatbot. So there's quite a spectrum of maturity. The early deals we've had with our agentic products have been with the companies in the former category. They've thought through the platform and they said, "Hey, we want to really holistically do this. We're going to do big time automation across our business. The future is agentic. What pieces do we have to invest internally to make this all work. And our approach really resonates there. So yes, it's -- we feel like it's early, but the signals are pretty compelling and clear that this could be a big deal.

Yes. And we had this discussion earlier in the year. But in the market, there's been kind of a lot of identity start-ups or acquisitions of kind of start-ups within the space. Just what do you think that people are missing about kind of what is necessary and what kind of others are doing with these smaller identity acquisitions?

You're talking about like CrowdStrike?

Or just...

CyberArk? CyberArk is not a small company. ServiceNow. Well, I think it's -- I think when you -- I think what's driving a lot of this is it's a big problem for customers. I think people don't -- Okta has a unique view of how messed up the identity world is out there for customers. So we've been living it for a long time. We see it. But I think people don't -- people underestimate how fragmented and confusing and the jargon, the vernacular and the acronyms, it's very complex for customers. And it's -- by its definition as an industry, it's in the middle of everything.

And so it's got this other dynamic of -- it's just -- it's very complex. And a lot of our success -- forget about AI for a second, a lot of our success is just bringing some simplicity and some sanity to that, which we've done a very good job of, which is like -- there's never been a company like Okta. There's never been an at-scale independent neutral identity company. They all got to a certain size and then some big platform scooped them up, happened back in client server days, happened in the web days, Oracle bought a bunch of them and then kind of killed them all. We're the only one ever. And it's because we've been able to make it simple and rational. And now we have multiple products across different categories, that's never existed before. So that's a powerful position.

So I think -- I'm sorry, it's a long-winded answer, but I think what -- I think people from these big companies, whether it's ServiceNow or Palo Alto or CrowdStrike, they talk to customers and they're getting a firsthand look into how messy it is. And then they're seeing all these breaches caused by identity. And so they're trying to react to customer demand and -- which is rational. But I think what they don't realize is that it's -- if you don't own and you don't operate the identity infrastructure, the directory, the connections, the core of what it is, it's much harder to do security around it.

If you own the infrastructure, you can make the infrastructure itself secure and you can build the detections and the monitoring and the posture management tightly coupled to that identity infrastructure, make it better versus if you're trying to do what some of the other folks are doing, which is trying to do identity security tooling across a broad range of complexity. I think we're in a better position to deliver that value.

Got it. It's great having you here just as a voice as a founder. We've seen kind of concerns of late of what AI can do to cyber. Just how do you see that discussion evolving? And how do you talk to your ongoing moats? And just do you think that the market is missing anything about that kind of AI eating software eating cyber?

Yes, everyone thinks about it. I think it's super interesting. I think there's so much -- I think that there's a lot of zero-sum thinking there, meaning that if someone builds something with cloud code or someone vibe code something, there's a zero-sum. It's going to replace something and that's -- companies are going to be cost cutting because they're going to take out some workflow tool or some infrastructure tool. I think in general, there's so much we can do with technology and so much power and automation and cost efficiencies and revenue -- I mean, the industry, technology industry.

I mean the technology industry, you all know this, you're conversant in the numbers, but the IT services, so the people doing IT work, implementing systems, designing systems, coding, it's $1.8 trillion. And so I think the zero-sum nature of it is people are getting that wrong. And then I think you get to -- when you're figuring out, there is definitely going to be -- like you heard me say it, I think everything is going to be a agentic. It's going to be what we think of as a SaaS app now will have to get agentic or it will get disrupted. Now -- but I think they will get agentic. Some will, some won't. Some will get more -- have the religion and get agentic faster.

There'll be more or less disruption. But I think what companies are going to have to do is figure out, okay, what am I going to try to build? What am I going to try to augment? What am I going to replace? And I think when you get down to this infrastructure layer that has to work, like identity infrastructure has to work. Like it's not optional. If it doesn't work, you can't log in, you can't go where you don't know your people, your agents are going to connect to. And then it has to be secure.

And so I think we're fortunate that we're at this -- we're in this infrastructure category that has a pretty high bar for -- I think the build your own bar has to be pretty high to cross over. But it's incumbent upon us to make sure that we make sure our R&D teams are using all the latest tools to build way more capabilities than we have in the past and get leverage from that and make it not only our reliability and our security top notch, but the capabilities we deliver is so good. It would really be hard to get to the decision that you would want to build it yourself.

Got it. You just mentioned Auth0 for AI agents, which has been out for a quarter. Okta for AI agents still kind of in testing. Can you just walk through...

It's dozens of customers. Yes. So when we say early access, it just -- it means it's still paid for so customers in production. It's just -- we haven't totally opened the floodgates on it yet.

Just what are kind of some early learnings just that have kind of helped inform either further developments as you look to roll it out to the broader suite?

I think it's -- I have -- the way we're organized is that we have a go-to-market tiger team that is working closely with customers to iterate the cycle of iteration and the feedback loops into the product team is very fast. This is a fast-evolving environment. So that's -- so stepping back, we set it up to learn a lot and learn a lot fast. And I think one of the most valuable things we're learning is that we can provide this central system of record I'm talking about, which is valuable. But we can also help in this category of agents that's broad across systems.

So what we see is that the companies that are building agents in their app, they tend to be more siloed. They tend to work on HR data or customer data or we can really help those flows spread across different silos, go to the data warehouse to different custom systems, different SaaS systems. And that's -- and I think the industry probably will start talking about that as a new kind of agent. It's broader, it's more capable. It can automate more things versus a stovepipe agent. And because we're so good at spanning different stacks, it's been an area that's really resonated with customers.

And then just how does what you learned from Auth0 for AI agents kind of inform what you've put into Okta for AI agents?

Well, I think the link -- so Auth0 is for people building agents, like if you're building a custom agent, whether you're a SaaS company that's trying to build agents into your product or you're a company that's building some of your own agentic software internally, you can use Auth0 for AI agents to do a bunch of things that are common that agents need to do. It handles the interchange between the system and the back-end systems that needs to talk to in a way that makes it really easy for developers. And the connection is that Okta for AI agents helps security and enterprise team have this authoritative system of record of what agents the customer has and what they can connect to.

So if you build an agent with Auth0 for -- Auth0 for AI agents seamlessly plugs in and goes into the registry and manage the life cycle. But Okta for AI agents also works with Salesforce agents and the agent core from Amazon and Microsoft Fabric and Google and the 50 other agent platforms that are coming up. And in this dynamic market, that's really valuable to be -- have the central registry and the source of truth of everything in your environment.

Got it.

I mean there's no way for these customers to even keep track of what all the stuff coming at them. It's probably another learning coming at them so fast, especially companies that aren't very far along on the maturity curve of thinking about what this means, just the visibility into like who has agents is valuable.

Yes. I mean we spoke earlier in the year and you talked about kind of the system of record. You are also talking about some of the protocols that you were going to have out there to get different stakeholders to ease the standardization. Just where are we on that? And how should we measure whether we're seeing traction there?

It's -- I feel like I keep saying it's early a lot, but it's early.

It's a common theme this week. Don't worry about it.

Yes. Yes, yes, which is -- I mean, it's very exciting, right? But I feel like there's a lot of work to do, which is invigorating. The -- this agentic world, whether -- and I've said a few times now, it's like everything is going to be agentic. There's no good standard way for how it plugs into a company and so the company can make sure it's secure, they have visibility in what it's doing. It's -- they can stop it if it starts doing things that they don't want to do.

That whole interface needs to be defined. And it's going to be defined as some kind of technical standard. There'll be de facto standards. There'll be people will get a bunch of traction and kind of set the default and other people will follow, but it needs to have some technical standards there. The best standard so far in agentic world is MCP. But MCP is not -- it is really how the models talk to the tools and the tools can share their data in a standard way -- discoverable way with the agents and models.

But it's not -- there's not a technical standard of how the agents are -- get visibility and are monitored and controlled. So we've done some things working with the folks on the MCP standard to add capabilities to MCP to make it more compatible with enterprises. I'm sure there'll be more of that. I'm sure there'll be more just technical standards in the industry to make it all plugged together, and we're going to be right in the middle of next year deployment.

Got it. So I want to turn to results from last night. You reported 12% cRPO growth, 11% overall growth. You noted 30% of bookings -- of Q4 bookings were from new products and that you were seeing 40% average uplift when they were part of deals. Just where are you seeing -- those are great stats. Where are you seeing the most traction with those new products?

Strength of our business has been larger enterprises. That's been consistent over the last few years. And which kind of makes sense because they have -- there's a lot of complexity. There's a lot of security. There's a potential to upgrade security with a great identity system. There's a lot of -- like I mentioned before, there's a lot of complexity. There's a lot of -- these companies have 20, 30, 40 identity systems, and it's just -- it's hard to manage and it's expensive, and they don't get a lot of the security outcomes that could be available to them if they standardize in something modern like Okta.

So large enterprise is a highlight. And our message with multiple products and our identity suite. And by the way, a lot of people say they have a suite. Ours is different in that's an identity suite. And you can -- you have to standardize on something and we'll save you costs and all your identity products. And then we also have the added benefit is you can choose the best cyber stack around that. You can use CrowdStrike, you can use Palo Alto, you can use any app you want, you can use any agentic world, you can use any agentic development platform, any model you want. So this neutrality, it's like pick something to standardize on. Our pitch is like, hey, pick identity, we'll handle all the identity use cases. We'll consolidate all the vendors. And then we'll give you the choice. We're not going to say, hey, it's any model you want as long as it's our model.

And then just on the new products, I think you mentioned that OIG was kind of where you had seen kind of the most strength in the new products.

2,000 customers now. It's awesome.

Okay. Perfect. In the outlook, there was a small step back on operating margins as you invest more in go-to-market and agentic solutions. Just what is giving you the thought that this is where you want to invest right now?

Well, the 2 -- I think the 2 areas of investment are -- incremental investment are go-to-market and then R&D. And I think there's the -- in terms of the go-to-market investment, I think there's -- we're seeing productivity. We're very comfortable where the productivity is now after it accelerated last year. And we feel like there's more market share to be gained with that investment. R&D side is mostly about making sure we're -- we continue to innovate, have this comprehensive set of products. The Agent investments are a good part of that.

We're also -- I think maybe something else that's maybe not obvious -- well, maybe it is obvious looking at the numbers, but we're -- I think is an advantage for us is the company is in a good spot in terms of being able to invest more at an efficient rate. So we can get more bang for the buck because of the way we have global R&D development centers now. We have -- of course, that's all being accelerated with AI tools. So just structurally, I think we're in a better place to get more bang for our dollar. And so we get -- it's almost like a more leverage when we do tick up the investment in these areas, which is something that's -- we're just in a much better position than we were 3 or 4 years ago in terms of that. It was all the hard work we've done last year.

Got it. Yes. One of the other announcements you made last night was just about this professional services business and moving that more towards the GSIs and the channel. Just why was now the time that, that made the most sense?

It's -- so I think the -- one of the things that is also maybe a little bit unique about Okta is that for an identity product set of products -- identity product and a set of products, we're pretty -- it's pretty low services, pretty -- like implementations are relatively easy. I mean it's not -- I would never say they're easy, especially in some of the large complex enterprises, they can be complex. But compared to other stacks, it's relatively easy. So I think we've gotten to a scale where maybe if it wasn't so easy, the global systems integrators would have been more aligned with us and really staffing up to do the services earlier in our life cycle.

But with the products getting more powerful with governance really hitting its stride, there's just more work in the large enterprises that these GSIs can do. So we kind of had to make a choice. Are we going to lean into that and lean into their interest because they see us as the leader. They see other vendors in the specific identity space as maybe not innovating and not pushing the boundaries forward. And then they see agentic and all the potential there, and they're leaning in on us, and we're at this point where our products are capable of really doing these transformations that require more GSI support or services dollars.

We had to make a decision. Are we going to -- do we want to grow our own services? Or do we really want to lean into this enabling GSIs and I always say that if you're going to make a decision, unless it hurts a little bit or unless it's a hard decision to make, it's probably not worth a lot. And so when you have to really forgo some services revenue, it means it's probably a decision that might hurt a little bit in the short term, but be something really good long term. So that's where we are.

Got it. As investors look towards -- are looking for reacceleration in the business on the back of some of these go-to-market investments and agentic, just how are you thinking about fiscal '27?

I think it's like a beginning of a new era for Okta. And I think it's maybe that there was the start-up era and then we went public and then there was the COVID era and the 0 interest rates, and we've kind of settled things down and normalized it. I think this is the beginning of a new era. And I think the platform approach we have just identity, this unique approach to an identity platform, no one else has it. No one else has a broad identity platform like we do that's not super tied into another stack. So it's unique in the industry.

And this -- the opportunity to be the foundational layer for agentic identity and agentic connections, that could be bigger than all of identity is now. That could be bigger than cyber. And that's a massive opportunity. You're talking about a tech stack that's going to -- this agent tech stack just for starters is going to have a huge impact on $1.8 trillion of IT services and not to mention the other -- what the leverage and the productivity and the effectiveness of 1 billion-plus knowledge workers, that's massive. And that's exciting to us. I mean we don't want to -- we're not here to build just an okay media and SaaS company. We want to build one of the best, great, impactful companies ever. And I think this could be the start of a -- this is the start of a new era, and it's up to us to make sure we capitalize that over the next several years to make it a reality.

Got it. It's almost like a great end, but now...

But I want to make sure it's clear. I did not guide to $1 trillion in revenue.

Let's talk about go-to-market for a second and just kind of how you go and sell that vision. You've implemented a number of go-to-market changes over the last year, focusing on some kind of specialized sellers and Okta and Auth0 teams. Just where do you feel like you're seeing kind of the most traction there? And yes, I guess.

I think -- so about change in go-to-market change, I think the notable thing this year is there wasn't much change. And we already saw that in the performance at the start of Q1. It's what you would expect. It's -- there wasn't a lot of cost to change so far. It's only a month end, but it's what you expect. And I think -- so if you go back a year ago, the main change was more specialization around Auth0 and Okta. And those platforms both have become so capable that it was really hard for one rep to get their head around it all. And so that's been working great. And I think what you're -- the new products is probably the best evidence of that. You don't -- if you're not specialized on all the innovation in the new products, it's hard to sell them. If you're spread across too many, hard to deliver that and know what they're talking about when they drill into the details of identity security posture management and what's the difference between that and identity threat protection and security center and Auth0. So we're seeing that pay off.

I mean as you think about AI as almost -- or -- I know you've mentioned everything will be agentic and so maybe this is the point. But do you need these special teams for AI sales versus this split between Auth0 and Okta?

Yes, that's -- well, I think right now, it's -- I think the operating principle right now at Okta is that it's a tiger team that is designed to iterate fast and get feedback from the customers of the product. And that tiger team by -- they basically are doing a lot of things, but they're also sitting with a bunch of reps through these deals. So the reps -- these AI deals still go through the reps. You basically have this tiger team that's the overlay or the specialist. We're thinking that it will be a generalized sales motion, but I think we're flexible on that as we scale it out. It might make sense that the products evolve in a way that they're more separable than the core platform. So we might do it separate.

But the way -- the plan now is that it will be like -- the AI products are horizontal across Auth0 and Okta, meaning that if you buy Okta for AI agents, you can -- your AI agent identity gets some connections with log-in, it gets some connections with universal log-out, some connections with governance and some kind of horizontal and same with Auth0. So we're trended now toward a more generalist model, but I think it's -- the reality is that this could change as we go down the path.

Okay. We've had this discussion before. But just in terms of as you move upmarket, as you have these bigger conversations, those can tend to lead to longer sales cycles. And so just how are you balancing the -- we have solutions we can give you day 1 and then progressing that conversation along?

I think it's a real thing. Like I think it leads -- part of this is why our years are so back-end loaded. As we move upmarket, we get a lot of deals that we could just do a smaller deal, but we wait until the end where it's a big platform deal. I think it's hard to -- when you're trying to deliver broad value across multiple use cases, sometimes it's hard to start small. The fact that it's relatively straightforward and possible from a technology perspective and packaging pricing perspective that has some kind of buffer to that. But it is a real thing. I don't think it's getting worse. I think it's been steady as we've moved upmarket.

I just -- I would say the biggest difference is that when the deals come, they're bigger. So the sales cycles are not any longer, but when they come, they're bigger. And when someone actually does delay them for a couple of quarters to get the big one at the end, it's actually bigger, which is what you want. You don't want people delaying for 2 quarters and then delivering the small one.

Right. But maybe -- you talked about this. You guys have built an incredible platform. You generate a fair amount of cash. You announced a $1 billion share repurchase program earlier in the year. Just how are you thinking about capital allocation?

The -- so I think we think the stock is undervalued. That's why we did the buyback. And then the other variable there is we were looking at ways to grow the business with M&A. And the -- when we've done M&A in the past, Auth0 is an exception for that strategic asset, but a lot of our M&A has been small tuck-ins, technology and teams. We had great success with that. And the at-scale acquisitions in our strategic zone of identity would have been legacy companies that are software companies. So we've never done anything like that. And I thought that's the right -- I think that's the right decision.

So basically, it's a long-winded way of saying is that the -- we keep looking for acquisitions, but they tend still to be tech even the things we're looking at around AI tend to be small teams that are innovating quickly, not something that would be a huge capital allocation. So with that, cash generation and trying to return some value to shareholders with buybacks we think the stock being undervalued makes sense. I think going forward, the -- we have -- we talked about a $1 billion pool for buybacks. We'll do that in a moderate way because we can't predict the price week-to-week, month-to-month, quarter-to-quarter. But the -- we're comfortable with that. And then going forward, I think beyond that, I think it will be -- the question will be really around like what M&A could move the needle in this -- as the company evolves into this infrastructure for AI agents and what that will mean there. That will probably be the next decision point.

Okay. Got it. Well, Todd, thank you so much for being here today, and congrats on the quarter.

Thanks for having me. Thanks, everyone.

[Presentation]

Hi, everyone. Welcome to Okta's Fourth Quarter Fiscal 2026 Earnings Webcast. I'm Dave Gennarelli, Senior Vice President of Investor Relations at Okta. Presenting in today's meeting will be Todd McKinnon, our Chief Executive Officer and Co-Founder; and Brett Tighe, our Chief Financial Officer. Eric Kelleher, our President and Chief Operating Officer, will join the Q&A portion of the meeting.

At around the same time that the earnings press release hit the wire, we posted supplemental commentary to the IR website.

Today's meeting will include forward-looking statements pursuant to the safe harbor provisions of the Private Securities Litigation Reform Act of 1995 including, but not limited to, statements regarding our financial outlook and market positioning. Forward-looking statements involve known and unknown risks and uncertainties that may cause our actual results, performance or achievements to be materially different from those expressed or implied by the forward-looking statements. Forward-looking statements represent our management's beliefs and assumptions only as of the date made. Information on factors that could affect our financial results is included in our filings with the SEC from time to time, including the section titled Risk Factors in our previously filed Form 10-Q.

In addition, during today's meeting, we will discuss non-GAAP financial measures. Though we may not state it explicitly during the meeting, all references to profitability are non-GAAP. These non-GAAP financial measures are in addition to and not a substitute for or superior to measures of financial performance prepared in accordance with GAAP. A reconciliation between GAAP and non-GAAP financial measures and a discussion of the limitations of using non-GAAP measures versus their closest GAAP equivalents are available in our earnings release. You can also find more detailed information in our supplemental financial materials, which include trended financial statements and key metrics posted on our Investor Relations website.

In today's meeting, we will quote a number of numeric or growth changes as we discuss our financial performance and unless otherwise noted, each such reference represents a year-over-year comparison.

And now I'd like to turn the meeting over to Todd McKinnon. Todd?

Thanks, Dave, and thank you, everyone, for joining us this afternoon. We're pleased with the strong finish to FY '26, which was highlighted by continued strength with large enterprises, partner engagement and contribution from our newer products. Identity is fast becoming the most important aspect of security with AI acting as a catalyst. In today's call, I'll cover the success we're having with our new products, how Okta secures AI, including some early success we're having in that new market enclosed with our top priorities for FY '27.

We continue to see strong performance from our portfolio of new products. This group consists of Okta Identity Governance, Okta Privileged Access, Identity Security Posture Management, Identity Threat Protection, Okta device access and fine grain authorization. And new to this group are our products Auth0 for AI Agents and Okta for AI Agents. The value of a unified identity system with a single control plane is resonating with customers. In aggregate, these new products represented approximately 30% of Q4 bookings, which is a meaningful increase from prior quarters. And when these new products are included in a deal, the average contract uplift is approximately 40%.

Okta Identity Governance continues to be the biggest of these new products and is building on its early success. OIG now has over 2,000 customers. That's remarkable progress in just over 3 years, and it underscores the market demand for a modern governance solution. Customers are choosing OIG because it's a full IGA cloud native solution built into our unified platform, not a siloed point solution.

I mentioned that our portfolio of new products now includes our AI products. Auth0 for AI Agents and Okta for AI Agents. It's still early for this developing market, but as the leading modern identity solution for workforce and customer identity, Okta is uniquely positioned to help organizations combat the growing security threat that AI agents represent. The reality is that the AI revolution has moved faster than today's security frameworks. According to Okta's AI @ Work Report, 91% of surveyed organizations are already using AI agents, but only 10% have a governance strategy in place.

In meetings that I've had with customers and prospects over the past 6 months, the vast majority of the conversations revolve around their AI initiatives and how Okta can help them build and manage agents securely. As AI becomes embedded in more workflows and automations, the growing number of exploitable entry points from nonhuman identities to unsecured integrations expand the attack service for threat actors. It's clear that in order to get AI right, you have to get identity right.

Okta was built to meet this challenge. Identity isn't just a feature for us. It's our foundation. AI agents are simply a new identity type, and protecting them as a natural extension of what we do best. Okta's neutral and independent identity solution is uniquely positioned to secure and govern the entire agentic life cycle and gives customers the freedom to deploy on any agent platform without ecosystem lock-in, all while strengthening their security posture.

Our twon-pronged solution with Auth0 and Okta for AI Agents treats AI agents with the same importance of humans and gives customers everything they need to secure this powerful new technology. We're still in the early stages, but we believe that in a few years, agents and agentic systems won't be the exception to how enterprise software is built and operated. They'll be the rule. We believe that AI agents represent nothing less than the future of software. That's why AI security is identity security.

I'd like to highlight a couple of AI deals we closed in Q4 that illustrate how we're addressing the AI market. An existing Auth0 customer is building AI agents as part of their leading financial services platform. These agents will help the firm's advisers make better and faster decisions. But to do so, the agents need access to sensitive customer information, which must be least privileged. And they need to work with existing systems and third-party services inside the financial institution. The customer picked Auth0 for AI agents as it met their stringent requirements for a secure, extensible platform to build and deploy a agentic systems. They needed a solution that offered enterprise-grade identity for humans and agents while providing secure access to third-party MCP servers, all while acting as a single source of truth.

Another notable deal that included Okta for AI Agents, which became available in early access in January, was with a top global business and technology services provider. They chose Okta for AI Agents to help them discover control and govern identities for their growing sprawl of agents. Rolling out AI agents across multiple agent platforms is key to their ongoing transformation, and centralizing agentic identities in an independent agent agnostic platform like Okta will strengthen their cybersecurity posture.

This is the very beginning of the AI opportunity. Building and protecting AI agents is inherent to Okta's position as the world's system of record for identity management. With our solutions, developers, administrators and IT teams can ensure that the entire life cycle of an AI agent from initial design through active deployment is observable, governable and secure. For more information on how Okta secures AI, be sure to register and join our showcase event on March 16. In this live streamed event, you'll hear from myself as well as our AI product leaders as we unveil our latest innovations for AI agents.

And finally, I always like to take time on the Q4 call to share our priorities for the new fiscal year. It shouldn't be surprising that all of these priorities are focused on driving growth. The first priority is Okta Secures AI, which is all about how we win, grow and become the standard for securing agentic AI. By building on our early success with Okta and Auth0 for AI agents, we will further our vision of freeing everyone to safely use any technology.

The second priority is increasing our focus on landing bigger and growing faster with large customers. We want these organizations so think of Okta first when it comes to identity security and securing AI. This is a global effort across both the Okta and Auth0 platforms.

And our third priority is becoming the default identity security solution for the U.S. federal vertical and highly regulated industries. The public sector has been one of our fastest-growing verticals over the past couple of years, but we've only begun to scratch the surface of the overall opportunity.

To wrap things up, we're pleased with the strong finish to FY '26. We're excited about the momentum we've built for the year ahead as we look to surpass $3 billion in revenue on our way to $5 billion and then $10 billion. Identity is security, and we're building on our position as the leading modern identity solution to win the emerging market for securing AI. It's an exciting opportunity, and we're going after it aggressively. I want to thank the entire Okta team for their tireless effort and also thank our loyal customers and partners who put their trust in us every day.

And now here is Brett to cover the financial commentary.

Thanks, Todd, and thank you, everyone, for joining us today. We're pleased to close out another fiscal year achieving Rule of 40, which we've done every year since going public. It's also satisfying to see our investments to drive growth paying off. These focus areas include new product innovation, go-to-market specialization, large customers and our partner network. My commentary will provide insights into our Q4 performance and then move into our outlook for Q1 and FY '27.

The increased go-to-market specialization that we implemented at the beginning of the fiscal year continues to make progress. Strong execution has led to positive go-to-market KPI improvements, including sales productivity. Our focus on large customers and large deals continues to drive our financial results. In Q4, we closed a record amount of total contract value of nearly $1.3 billion. We also surpassed a major milestone of $3 billion in annual contract value.

Another key aspect of our go-to-market motion is our channel partners. When our partners are involved, the average deal size is bigger and the close rates improve. Channel partners were engaged in 18 of our top 20 deals in Q4. Total contract value generated through our strategic go-to-market channel AWS marketplace, grew over 45% in FY '26 to approximately $750 million.

Moving on to our balance sheet and capital allocation. We had another strong quarter of cash flow in Q4 and ended the quarter with a very healthy balance sheet, consisting of over $2.5 billion in cash, cash equivalents and short-term investments. We continue to regularly evaluate Okta's capital allocation priorities to ensure we're well positioned to deliver sustainable long-term value to shareholders. Consistent with this focus, we announced a $1 billion share repurchase program in early January, taking advantage of what we believe to be an undervalued share price. Over the course of the remainder of January, we repurchased and retired over 875,000 shares for a total cost of $79 million.

We're proud to return value to our shareholders and are focused on capturing the clear opportunity in front of us. The investments Okta has been making to drive growth acceleration span all areas of our business. These disciplined areas remain investing in our go-to-market teams, relentless product innovation, further leveraging our channel partners and keeping Okta one of the most secure companies in the world. Our improved go-to-market execution, coupled with a healthy demand environment led us to begin adding quota-carrying sales capacity starting in Q2, and we continue to do so through the fourth quarter and now into the current Q1.

Now let's turn to our business outlook. Our guidance philosophy is unchanged as we continue to take a prudent approach to forward guidance that factors in current market conditions. For the first quarter of FY '27, we expect total revenue growth of 9%, current RPO growth of 10%, non-GAAP operating margin of 23% to 24% and free cash flow margin of 33% to 35%. For the full year FY '27, we expect total revenue growth of 9%, non-GAAP operating margin of 25% to 26% and a free cash flow margin of 27% to 28%.

I want to call out 3 important points pertaining to this guidance. First, reflected in the 9% FY '27 revenue guidance is about a 1 point impact related to a decision we made to shift more of our professional services business to our partners, specifically global system integrators. This change will result in lower professional services revenue. We believe this will lead to greater long-term benefits to fuel top line growth by deepening the relationship with these important partners and increasing our business with large enterprises.

The second point is that the FY '27 free cash flow margin guidance reflects about a 1 point headwind related to lower interest income relative to the combined impact from the stock repurchase program, our intent to settle the remainder of the 2026 notes in cash and the interest rate environment.

And finally, we've updated our non-GAAP tax rate assumption for Q1 and and FY '27 to 21% from 26% based on the recent changes to the federal tax laws.

To wrap things up, we're pleased with what we accomplished in FY '26 and are enthusiastic about the trends we're seeing in our business. The investments we're making are paying off and position Okta to extend its leadership in identity security. We've demonstrated exceptional leverage in our model and are positioned to deliver profitable growth for years to come.

With that, I'll turn it back to Dave for Q&A. Dave?

Thanks, Brett. I see there are already quite a few hands raised, and I'll take them in the order from the top of the hour -- through the top of the hour. And in the interest of time, please limit yourself to 1 question. And with that, we're going to go to Joe Gallo at Jefferies.

It was great to see the AI agent customer wins. Can you just talk more about pricing there? I wasn't sure if the 40% was referring to agentic. And then just any sense of when agentic will become meaningful to growth. Brett, I know you're really pragmatic. How should we think about what's reflected from agentic in your top line guide?

It's -- yes, the agentic products are really, really important to us. I'm not breaking any news there. Everyone knows this. But in Q4, it was really a story of all of our new products. The 30% of our new bookings were from new products. That's a very important strategic bucket of products we've been investing in for a long time. And then the agentic products are the newest bit of that. And they had an absolutely incredible quarter considering Okta for AI agents is not even generally available yet. And Auth0 for AI agents is just was generally available at the beginning of the quarter.

So talk to a huge start. Now the relative number is small compared to our $3 billion revenue run rate. But looking forward to next year, we're very, very excited about the potential of these products. What's happening is that every company is figuring out how they're going to absorb all this AI innovation, how they're going to build things themselves, how they're going to adopt SaaS innovation with agentic built in, how they're going to adopt all this change. And what you're seeing is the identity is becoming a critical infrastructural foundation for that. They have to have a system that can basically keep track of where all the agents are and who has agents and what kind of -- what can the agents do and what can they connect to, and that's what they're looking toward our products to do. So it's incredibly exciting.

But it's also the success of governance over 2,000 customers and our other new products set us up for a lot of, I think, success ahead. In terms of guidance, I'll let Brett talk about the specifics. But because the agentic products are so new, it's tough to pour too much into our assumptions about growth in terms of guidance, but I think those things could be a huge source of upside over and above the guidance in the years ahead.

Yes, Joe. I mean Todd nailed it right there, which is it's still fairly small at this point, but we are excited given the amount of demand that we're seeing. It's not just the amount of bookings that we did in Q4. It was -- it's also the pipeline we see that is out there for FY '27. And like Todd said, look, it's a $3 billion business. It takes a lot to move the needle in there. But we're not thinking about this as an opportunity just for FY '27. This is an opportunity to be accretive to growth for FY '28, '29. And we'll see the results. As you guys know, in current RPO first before we see it in revenue. So we are excited about it and I think it's a big opportunity for us. And you'll probably hear our bullish tone about it over the course of this call because of what we're seeing inside the business at this point.

Next up, we will go to Adam Borg at Stifel.

Awesome. Todd, maybe talk a little bit more about the go-to-market changes you're starting, you're doing this year, what you're seeing there and also on the international front. What's the opportunity to drive growth higher there and it still lags domestically?

Yes. I think the headline about go-to-market changes in Q4 and coming into Q1 is they're very limited. We have our go-to-market structure in place. We're very confident and comfortable with it. It's -- we're seeing productivity ramping. We're seeing attrition low. We're adding capacity. And if you just look at the plan for this year, we don't have the usual assumption about cost of change in the early quarters of this year, which is very exciting. We have a team that's psyched up and ready to go and they're armed with these new products, and they're organized by specialist domains across Auth0 and Okta and hunter and farmer, and they're ready to roll. And they're coming off a huge Q4 and they're excited.

And it's in -- and this partner is more qualitative, which is that what we can provide to the market and to customers is this infrastructural foundation for this agentic enterprise. And that's -- when a sales group of salespeople or salesperson goes out there and has that conversation with the customer and the customer clearly reflects back to them that this is a pressing urgent problem that they need help with and they see Okta as the entitled company to actually deliver that value, that's powerful. It's got everyone super excited, and now we just have to go out and deliver on it.

You got -- you don't get any points for conversations. You got to put wins on the board, and that's what we're focused on doing.

I think the transition coming into Q1 and this year, and we had our annual sales kickoff last year, our real focus is we delivered a strong year last year. We feel very strong about the results from Q4. We talked all throughout last year about how we were building specialization as the new lever. As Todd mentioned, our productivity has increased. Our rep attrition has decreased. So coming into this year, we are committed to that model, and we're not injecting a significant change.

With one area in particular, I do want to note, in addition to Todd's commentary, which is note Brett shared about our investments specifically in our channel and specifically in our relationships with global systems integrators. So the one significant change we have there is we very consciously chosen to better leverage our relationships with the global systems integrators because our customers need them more than ever for the change management associated with the transition to agentic, for the increase in cyber and the importance of securing identity for human, nonhuman and agentic. And so we're embracing that partnership.

Those partnerships have been very successful for us with some of our largest customers. and we're excited to be leaning into that this year as well, and you see that reflected in the guidance.

Yes. This is really exciting, and I'll just take a minute here to comment on this. What's happening in the market, there are some market forces going on, which is every customer, obviously, is interested in AI and agentic AI, and they're going to these GSIs and asking them about how to invest in the foundational elements and the security. And just like customers are coming to us, they're going to these GSIs and the GSIs see that we are the answer. We can help customers power this agentic enterprise and be the source of truth for identity and connections between agents and systems. And the GSIs see that is foundational as well. So the GSIs look at the identity market, and they see us as the clear independent and neutral leader. No one else has the scale. No one else has the capabilities. The other big identity companies are also trying to sell you a platform or to sell you a development kit or sell you other cyber tools.

So they're seeing we're the winner. So they're coming to us. And you're seeing a product suite that is more capable than ever that needs GSIs to help install it correctly and scale out of customers. So the GSIs can couple with the leader. They can help customers transition into this agentic future. So it's a win-win all around. What's left for us to do is really double down our investment by saying, hey, we're going to give up the professional services dollar as an investment to make this whole ecosystem bigger empower our long-term subscription growth. It's very exciting. I feel like we've been working on years and years to get here, and we're here, and it's incredibly exciting to me and the entire team.

Yes, we're really fired up. And just as one more indicator of the strength of that channel I mentioned we had our sales kick off last week. We had our GSIs in attendance that our sales kick off for the first time. And so our partners are really becoming part of our go-to-market engine. And their engagement was really high off the chart. So we're very excited about how this helps us reach more customers faster with the broader Okta platform solution.

Okay, we'll go to John DiFucci Gugen.

I think this question is for Todd and Eric. Again, listen, identity remains a high priority no matter when we speak to, right, IT purchasers, partners, so much so that others seem to be encroaching in the market even as Microsoft seems to have faded a little bit in conversations when you talk to people in the field, but you have names not usually associated with identity, like CrowdStrike and Rubrik talking about it or even things like One Password taking a different approach. I guess these names might not necessarily be competing with you directly. Is it causing confusion in the market? Or are more traditional names like Ping having a greater effect? Because, listen, you guys beat numbers, and it's always good to see that. But it wasn't quite what we thought it would be. And cRPO aside, the guide was a bit below where we thought you'd start and obviously, where the Street thought.

I think it is -- I mean the identity is at the center of traditionally -- in legacy technology, it was always at the center. And in this agentic world going forward, John, it's becoming clear to everyone it's even a bigger deal than it was before. But being at the center, there is some confusion about who's doing what. I think the biggest confusion people have is the distinction between identity infrastructure and identity security. And they hear the word identity, and they think if you're sitting on top of identity and detecting threats and blocking threats, you're also identity infrastructure. So that's one of the big confusions.

And when you look at the agentic market, they're both really important. It's the identity security, making sure the agents are monitored and checked that they can't go out of bounds but just the infrastructure, just the ability for the agents to connect and just for tracking and visibility, that's an infrastructure play. And we're the only company that really does both. It's at the security layer and the infrastructure layer. So I think that is maybe a little bit of a confusion and something that we're working hard to make sure everyone understands the advantage of that position as well.

Yes. And I would add. I think the examples you just described, they point to the fact that the world is understanding that identity security, in particular, agentic identity security is fundamental to the future. And so people are looking at how to invest there. But from an Okta standpoint, we're not seeing any material change in the competitive behavior in our transactions yet. Of course, we're keeping our eye on the landscape. And also, remember, we are -- we've been in this business for a really long time. And we have over 20,000 customers that count on us to protect their identity and over 7,000 integrations off the shelf. And we believe that neutrality and ability to integrate with everything is what our customers need. That's what we hear from our customers as well.

We think that positions us very well for the future. And the other note is agentic identity for us isn't a new product. It's an extension of the products we already have. We've already had human identities and nonhuman identities, and now we are simply expanding to also include agentic identities into our product stack.

So for us, we think we're very well positioned in this. We manage today over 45 billion authentication events a month and over -- we block over 8 billion threats a month as well. And those statistics are really meaningful to our customers. You know that we're the leader in the space.

One other comment for you, John. We're -- we'll try to keep them shorter on the next questions. I just want to make sure we're all on the same page around the mechanics of the revenue guide, which is it is a 10 point subscription revenue guide and a 9 point total revenue guide. So effectively, we're taking -- another way to think about it is professional services in FY '26 is roughly about 2% of total revenue. In FY '27, it will be about 1 point of revenue. So just keep that in mind because the subscription revenue is growing faster, and we talked about the investment while we're doing that earlier. I just want to make sure we're all crystal clear that subs revenue is growing faster than total revenue as a result of the good results we had in FY '26 and what we expect to produce in '27.

Yes. We don't want to disappoint anyone. We're going to make sure we work hard to exceed or -- meet or exceed the guidance. That's our mantra.

Okay. Next, we'll go to Josh Tilton at Wolfe.

Brett, you kind of stole my question right from me. I was going to be on that subscription guide. So maybe can you just -- I know you gave some of the puts and takes on the conservatism in the guide. But maybe just help us think about how conservative this guidance is versus the guidance you gave last year. And the reason I'm asking is because some quick math kind of suggests that this could be the year that subscription revenue growth accelerates. So maybe just walk us through some of the puts and takes there.

Yes. I mean it's real simple this year. We're not going to get into the details of this, that or the other. It's just we're taking into account market conditions we think we can produce. So guidance philosophy remains the same as what we've done in the last few quarters. So it's real simple. -- nothing too complicated.

Next, we'll go to Roger Boyd at UBS.

I wanted to come back to agentic and great to see the continued early traction there. I know it's early, but I wonder if you could provide any updated thoughts on how you're thinking about pricing in those products. I think in the past, you've talked about a per agent pricing model. How is that resonating with some of these early customers who are buying these offerings considering the potentially open-ended and rapid growth you could potentially see with agents?

That topic comes up all the time. And one of our advantages is as we have these conversations with our 20,000 customers, we get really rapid feedback on how we can capture value, what will be most valuable for them, easy for them to consume. So it's really a strategic advantage. We have this feedback loop, and we've actually structured the go-to-market team for AI agents to capture that feedback rapidly and feed it right back into the product teams.

And what we're seeing is that there's really 2 ways that we charge for agents. One is as like a multiplier on a person. So in the model where a human identity uses a number of agents to augment their work, there's a multiplier on that agent or on that -- what they pay for a person to what they pay for agents. And then also, there's -- if the agent is not coupled to a person, there's a -- we sell it based on the number of connections the agent makes because that's really the value. They want to secure those connections and filter on fine-grain access to all the back-end systems and the SaaS applications and the custom applications and data warehouses the agent connects to. As they get more -- the agent is more valuable as it has more fine-grain access to different things and it's more secure. So there's a multiple based on that.

The pricing we're working with these customers on is pretty early, so we're -- it's a nice step up. It's -- I mentioned earlier, by the way, I mentioned earlier, the 40% uplift. That was the uplift -- that specific number was the uplift on a specific deal that has new products in it. It wasn't broken out specifically for agents. We'll talk more about the actual specifics of agentic pricing in the quarters ahead, but we're not announcing that and talking about specific uplift or multiplier on human identities just as of yet, we want to settle down and get a little more consistent before we go broad and communicate that.

Next up, Matt Hedberg at RBC.

Todd, a question for you. I think we've all seen the highlights on competition from LLM vendors or vibe coding. And I think a lot of us on this call agree that like it's easier said than done. I guess from your perspective, when you look at what you've built over the years and the data that you're sitting on, can you talk about sort of the structural advantages that you see over maybe some upstarts or some vibe coding alternatives?

For sure, yes, something we -- the whole industry is thinking about. And I think what I've -- I can think about it hypothetically, and then I can tell you what customers talk about in my hundreds of conversations with customers. I'll just start with the hypothetical. I think if you want to build what any SaaS company has done or what Okta has done, it's years and years of hardening and making sure there's no vulnerabilities and making sure it scales and it's reliable. And it's -- if you -- I don't know what the inference cost to build that would be, but it would be pretty significant inference cost.

And then if you flip it around, you just think about what's the price of getting it wrong. And if getting it wrong, it's hard to validate. It's hard to prove you have it right. And if it's wrong, you have a major security breach or you're down. None of your agents or none of your people can access systems. So the cost of getting it wrong hypothetically and actually just the cost to do it theoretically, if it was even possible theoretically with an LLM or a tool would be pretty high. And that cost could change over time. We don't know.

But when I talk to customers, that's the hypothetical model. But when you talk to customers and you hear their challenges and their opportunities, they -- a lot of the same things are echoed. They want to identify key infrastructure pillars, and they want to standardize on them. And they see that as the unlock to hundreds of other decisions and hundreds of other build versus buy decisions they have to make. And they're putting foundational security, foundational identity in this bucket of things that they want to partner with a leader and trust it and go on top of that and figure everything else out. That's what they're telling me. And it kind of matches up with what I would think about hypothetically.

Now that all being said, we are paranoid, and we're making sure that we are using all the latest technologies, LLMs, coding tools to make sure we have not only something that's resilient and secure but has the best features and the best capabilities. And so we're making sure that we build things internally as fast as anyone could build them because we -- make no mistakes, the prize here that the whole industry is going after, which is this agentic future where digital labor is part of the TAM is a massive price. And everyone is, at some level, big picture is going to be going after this prize.

And it's exciting because it's greatly expanded the TAM of what Okta could be. Think about identity and what it's been in the past. It's roughly $20 billion TAM right now in terms of what people spend on the Vinda data we talk about an $80 billion TAM. I mean this could be bigger than -- this could be the biggest part of cyber in a few years for sure. And it could be even bigger than that if you really think about the infrastructure that stitches together the entire agentic enterprise and is the plumbing that makes it run.

So we're investing and we're paranoid, and we're working hard to make sure we capture that because the benefit to our customers and the benefit to our shareholders and the benefit to everyone involved is massive, and that's what's firing us up. We're working harder, and we're more excited than ever because that's what's at stake.

Next up is Todd Weller at Stephens.

A question on Auth0. It looks like growth decelerated a bit from 2Q when that was last disclosed. So the question is how do we think about the durable growth profile of that business relative to workforce. And then it would seem that AI could be a significant catalyst to accelerate that shift from the homegrown solutions to out of the box like Auth0. So any thoughts there would be great.

I think that it's -- we're very excited about Auth0. The think the deceleration a little bit is a tough compare. There's also -- we changed the go-to-market mix. Last year, as you know, to focus more on that, and there's probably some cost of change in that number as well. And those are maybe a little bit of puts and takes on it. I think we're bullish on it.

I think the big picture thing is what's happening in the CIAM. The CIAM market is transitioning to be not just a platform for logging in and doing authentication authorization, but it's a platform for customers building a agentic interfaces to their customers and to agents coming into their systems. So Auth0 for AI agents, that's what it is. It's a token vault. It helps agentic login. It helps customers hook other AI tools up to their customer login. And so I think over time, that's -- that market is evolving into something that's hugely impactful and value delivering for our customers.

I mentioned in my prepared remarks on the financial services firm that's using Auth0 for AI agents really to help deliver agents to their customers. And then you'll see those tools being used to deliver agent interfaces. And because like I think we talk about agentic, and I talked about agentic a lot of times on this call, but everything is going to be agentic. So the capability of software to do more things autonomously and seek goals and to do more unsupervised task is going to pervade into every layer of software, whether it's customer facing, whether it's employee facing, whether it's what an existing SaaS app does, whether it's the next generation of applications. It's all going to be agentic, and it all needs identity. And we're positioned to play in all of that, which is why it's so exciting.

And one thing I could add on around the tough compare that Todd was talking about, if you remember, Q4 of last year, Auth0 had a record quarter. And you guys know it was a really great quarter in general, but that's what's creating the tough compares, that Auth0 just had a fantastic Q4 last Q4.

Next up, we'll go to Brian Essex at JPMorgan.

Maybe to follow up on that topic. Just you've got Auth0, Todd, for AI agents and Okta for AI agents, and it seems like you've got a real competitive advantage on the Auth0 side. Could you maybe compare and contrast initial takes for sales cycles, competitive dynamics and velocity of each? I know it's still early stages, but is Okta for AI agents in a more competitive market? Or would love to just get your take on what kind of velocity you're seeing in each of those product segments.

Yes. I think it's maybe flipped. I think Okta for AI agents is more unique and more differentiated than maybe we would have expected. I think Auth0 for AI agents as unique and differentiated as well. But I think maybe the sentiment you're expressing is it's different than what we're seeing.

Customers need a solution that's pre-integrated to all these agentic systems. I mean there's no good way for customers to even understand what all these vendors are doing in agentic There's no catalog of systems that says Salesforce is doing this. ServiceNow is doing this. Agent Core is this. Google is doing this. Microsoft is doing this. And that's what Okta for AI agents does.

And then on top of that, it models connections and has policy for connections that connect users to different agents and agents to systems. So it's -- the reception of it is very positive, and now we have to turn that into continued momentum that we saw in Q4.

My customer conversations, I'm hearing urgency on both, but I would agree with Todd's comment that the -- we feel maybe slightly more urgency on the Okta for AI agent side. And if you think about that, the Okta for AI agents platform is the platform that helps customers find where they have rogue agents deployed. And that is often the top of mind, the top of mind for a corporate buyer for a CIO or a CISO is they know that employees are activating agents and they need a way to discover those agents and then to secure them, to manage them, to govern them to evolve their credentials and the Okta for AI agents platform solves that problem first.

But really, in parallel, we talked to a number of customers who are building agents and know that they need to build agents that can be discovered, they can be integrated, they can be authorized and the Auth0 for AI agents platform is what allows them to do that. So we said in the prior call and today as well, we are having a huge interest in both of these platforms across our customer base and with our prospective customers as well.

Go to Eric Heath at KeyBanc.

Maybe just extending on Brian's question and one follow-up question, clarification, if I may. So just on these AI agent deals that you are closing at this point, are customers evaluating alternatives at this point? Or are they solely just looking at Okta and choosing Okta? And then just a clarifying question for you, Brett. The uplift of 40% for the entirety of the emerging product portfolio, I believe previously, we were talking about OIG and OPA each being about a 33% uplift. So I was just a little surprised that the entirety of the portfolio on the emerging side is 40%. So any clarifying comments you could have there is great.

Yes. Before we break down the 40% on your first question, these are early adopters. But these are people that are thinking about for Okta for AI agents specifically, these are people that have seen the future of agentic and they're thinking about how they can get their foundational house in order. So they're early adopters. So they look at everything.

They've scoured every start-up, every big platform, and they're seeing a couple of things. One is that the vision of what we're delivering -- what we've delivered so far, even though it's an early access product and our vision of where it could be is very compelling. Two, they're seeing that they don't want to be -- they're reticent to trust a start-up with this critical piece of foundation because they know there's going to be M&A and they know there's going to be start-ups going away. There are so many startups playing in this space, that there's bound to be a lot of failure. And they don't want to build their whole foundation around something and have it be pulled out from under them.

And the other factor that is in their minds is that they don't want to be locked in. Think about -- what's happening in agentic and what's happening in this world, these foundational models are moving incredibly fast. And it's Anthropics foundational model that has the leap ahead, and then it's OpenAI. And then it's an open source model and then -- and that's going to continue for many years. And they don't want to be locked into a certain stack in a certain set of tools. So they're reticent to trust their foundational security with one provider, one platform. They want flexibility.

And back to the start-ups, they know that a bunch of these start-ups are going to be bought by the big players. So they're thinking, even if I go with a start-up now, it's going to get sold and then we'd be locked in to Microsoft and they don't really want that. So yes, it's -- our positioning is very compelling. And the exciting thing about Q4. I talked about last call, I said we had Oktane and everyone was super interested. And I've never seen interest in my life, in my career in a new product like this.

The great thing about Q4 is it actually translated into real dollars and real bookings. Now it's still small relative to our overall run rate, and it's up to us to continue that momentum through this year. And so it can really start driving the number on the top line and growth, et cetera. But we're on track. And it's like I said many times on this call, it's incredibly energizing.

Yes. And I would just add one thing to your comment, Todd, which is the deal size for these deals have been good-sized deals. They've been -- which is really nice to see because it has been more tilted toward larger companies. I think that's a general theme that we've seen at least in Q4, and we're seeing a little bit in the pipeline going forward. So going to your question, Eric, around the 50 -- the 40% versus the 33-ish, going to be very clear. Previously, we said there was a 50% uplift on governance of a workforce contract alone. The 40% is over the entire contract. So yes, the number was higher for 50%, but it was only a part of the business, the 59% of the business. If you take all 100%, it's a 40% uplift on the entire thing, which really shows that these new products are adding a tremendous amount of value to the top line for us, and that's why we're so excited about it.

Next, we'll go to Shrenik Kothari at Baird.

Great. So stay on topic of agentic. And Todd, you mentioned nonhuman identities could ultimately rival today, you mentioned can exceed. And just from a pricing standpoint, I agree it's still early to size, but incidents like the Salesloft breach or those compromised tokens, enable lateral access across SaaS. Can you tell us a little bit about like does this expand the nonhuman identity TAM beyond your early estimates and just overall strengthens your strategic positioning to lead this agentic category?

I think when I talk about agentic and being the identity foundation for the agentic enterprise, that really is a superset of what people call nonhuman. Nonhuman is like service accounts and sometimes they mean tracking machines. What I'm talking about is much bigger. It's a superset of all that stuff. And it's really -- it's going to -- it's the backbone of the agentic enterprise. It's incredibly valuable and mission-critical for our customers. And it's a massive TAM.

Anytime you're adding that much value to customers, you're going to be able to monetize it some way, whether that's just unique count of agents or that's agent connections that -- which is kind of how we're doing it now, whether that's -- that will evolve as we go forward. We'll figure that out. But it's the value we're potentially could generate or could provide to customers, is it's, I think, greatly increasing the TAM.

Great. Next, we'll go to Gray Powell at BTIG.

Great. Can you hear me, okay?

Yes, loud and clear, Greg.

Congratulations on the results. So I wanted to clarify an earlier question. So this is the third consecutive quarter where all the main KPIs have been clean. And then the forward revenue outlook, as far as I can tell, it was above the Street, not below. So I guess if you just -- if you had to point to 1 or 2 things that have been the biggest driver of your consistency, what would that be?

Large, large deals, large customers.

Okay. And then the follow-up would just be like how do you feel about your visibility on demand today versus 6 to 12 months ago?

The answer, like I said, large deals, large customers, people buying more of the products, more of the platform. And I feel more confident in it than I was a year ago. I was pretty confident a year ago, but we had a lot of change in specialization, and I think there was some cost of change there, and we had that in our guidance. And now that's not there anymore. So I'm more confident now.

Yes, I would just add -- I would add just, look, we've been focused on a few things for a while now, which is becoming one of the world's most secure companies, doing a good job there. New product introduction, you've seen the results there. Partners, you've heard us talk about it today and also in the remarks earlier. And then specialization. And all those things have been in this effort to continue to deliver consistent results and ultimately with the goal of growing faster than what we're doing today.

That's our goal. We think it's -- we've stated many, many times that we are not pleased with the growth levels at this level. we want to be able to grow faster, and that's why we're doing all these things and why we're excited about the opportunity because we see all of the fruits of our labor starting to pile up and produce solid results, and we think that's just going to parlay into better results going forward.

Next up is Kingsley Crane at Canaccord.

On agentic again, I don't think it's controversial to say that Auth at an OIDC weren't were originally designed for agentic across app access is a huge...

You know what they're designed for, right? You know what they are designed for, right? It was like sharing your Twitter feed, getting a third-party Twitter client access your Twitter.

Right. So yes, I mean, people centric, but I mean it seems like you're fighting a standards war as much as you are fighting a product war. Do you think that's fair? And then how critical is it for you to win that war? Or is the market sufficiently large where that doesn't matter?

I think standards are very important. I'm not sure that our standard has to win. I think we -- there really is nothing like cross app boxes out there. So I think in terms of like the ability for one agent to -- instead of asking a person to manually connect other services to that agent to delegate that to an enterprise IDP and let the IDP, ahead of time, set up that thing for per enterprise policy. There's nothing else like it. And it's like very universally accepted as a positive goal.

I think the the gate on how fast that will be adopted is every SaaS company and every technology vendor, they have, believe me, they're reading the headlines. They understand that they need to innovate in their products, and they're thinking about where supporting cross-app access is on their road map of priorities. So that's -- they're all trying to do a ton of things and make their services more agentic and more compelling and in security and the ability to have them be more enterprise-ready is on their list. But we have to convince them to get it higher on their list.

So it's not like a competing standard as is like a prioritization thing. But remember, we are -- we want to provide this identity infrastructure and make sure that we give people the solid foundation to build upon. And that's going to require standardization just because it's not going to -- you can't use a standard piece of foundation if everyone is doing their own things in a different way, which is why we're working with standards bodies in general. It's not just across boxes, but it's an important part of the equation. But I wouldn't say like the whole war rests on one specific standards body or standards battle. I think it will be an evolutionary thing over the next couple of years.

Great. Next up is Mike Cikos at Needham.

Great. Congrats on the strong finish and consistent execution here. On the Okta and Auth0 for AI agents, if I could just turn it on its head for a second, but do you receive pushback from organizations? Or what are some of the friction points you're here to adopt? And then secondly, I know you guys are obviously focused on this and investing aggressively. But what are current gating factors to driving faster success from an Okta operation standpoint?

I think it's specifically on agentic. I think it's really how fast companies are going to adopt AI, how fast they're going to -- most people are -- have chatbots now and copilots or things like that. I think the next wave is actually the autonomous goal-seeking agents. And there are some of those in the packaged applications, Agent Force and ServiceNow has some of them. Many companies are building their own internal platform to build these themselves. Some of them are using Google's Builder platform, Microsoft's or Agent Core from Amazon. But I think -- so I think the pace of adoption here, particularly on the foundational layer we're building is how fast they adopt agentic and then specifically, how much that means putting the cross-platform plumbing in that is required when you want to take an agent from one platform and have it work across platforms.

So I think it's -- they have a lot coming at them. They're trying to absorb innovation in different products. They're trying to figure out what they build. They're trying to figure out what they buy. And so I think our job is to make sure that they understand the foundation almonds what we do and how well it integrates and how seamless it is and how it gives them choice and flexibility, and the success we've had has followed that playbook. And so that's really something we'll keep doing so we catalyze a lot more momentum going forward.

There's no like -- a better -- sorry, I'm being a little rambly in my answer, but there's no -- we still don't have the reference architecture. There's no -- 1 million years ago, it was like you had a database, relational database and you had client server, and then it went to -- there's a reference architecture. You had cloud infrastructure and you had web middleware. There's -- that still hasn't been established for the agentic enterprise. But it will happen quickly. It's like you use this flexible LLM model. You use this identity layer. You use this maybe workflow layer. And so once that happens, everyone will kind of agree on that, and then you'll see it really start to crank. And that's why the stakes are so high to win this identity layer now, which could turn into the biggest market for us ever.

All right. Next up, we'll go to Rob Owens at Piper.

Would love to unpack the growth algorithm a little bit and focus on DBNRR. And it's been flat all year and I guess it's a little surprising. We think that you're through the headwinds of COVID as those have kind of anniversaried on a multiyear cycle. And the last couple of years have been really strong from a new product standpoint. I realize that retention rates are typically an output, not an input to a degree, and you're landing larger and that's all great. But as we've seen growth continually tick down, we just haven't seen improvement in this metric. And just curious why that's the case and when that might change.

Yes, I can take that one and then, Eric, if you want to add a little color. So one of the things that has been consistent has been that gross retention, Rob, it's the most important factor in there. That has been consistent and just a pillar or a foundation to that number for some time now -- actually several, several years. Just the upsell rate that we haven't seen as much to really keep it higher, right? And we think for the balance of FY '27, we do travel in this range, plus or minus a little bit. And what it's going to boil down to is how much new business do we do in the year and how much upsell do we do in the year because we've got confidence that, that pillar of strength, that gross retention will continue to be very healthy. So it really boils down to how much upsell versus new business we can generate in FY '27.

And that's one of the reasons why we have added this capacity into the system because regardless if you're looking at net retention, ultimately, what we really care about is that top line revenue growth number or really current RPO growth in front of that. In any given year, there's really only 2 variables that we can play with. One is the productivity per rep, which we -- which you've heard us talk about over the last several quarters of getting better and better. Actually, we talked about it in FY '25 as well. Good productivity improvement in '25. '26 was a good improvement enough to say, "Hey, let's add some more reps into the formula." So then that's the second piece of the formula, right? There's productive for rep and then how many reps do you have in there. And we've added a meaningful amount of reps into the system. You can see that in the sales and marketing expense line. I'd invite you to look at the year-over-year growth of Q2, Q3, Q4. That is going to lead to growth or at least our expect -- we expect to lead that to growth in the future.

So it's all part of a bigger plan there, Rob, to try to be able to accelerate top line growth, not just NRR. I mean we can talk about NRR, but it's not as exciting as really that top line current RPO growth that we're really targeting to go faster in the medium term. That's something we've talked to you guys about. We want to be faster than where we are.

Yes, the other -- the last thing I'll say on this is better understanding, Rob, is the RPO is growing faster than the cRPO, which means term lengths are getting longer, which means there's less to renew every year at an at-bat basis relatively speaking, which is another positive thing that's going to drive potential upside here.

Okay. We've got about 3 minutes left, so let's try to get through as many as possible. Next up, we have Peter Levin at Evercore.

I'll just give a quick. Most of my questions have been answered. Brett, the linearity around professional services, maybe just from a modeling perspective, help us understand how that plays out throughout the year? Is it more of an impact in the second half as partners ramp up on this new program? Just help us understand how we should model that out.

Should be a little bit more impact as the year goes on. That is correct, yes. That's about right.

We'll go to Patrick Colville at Scotiabank.

All right. I guess my one is for both Brett and Todd, please. In the prepared remarks, you talked of fiscal '27 the focus is on prioritizing growth. If I look at the fiscal '27 op margin guide, it's 25%, which is a great number. It's the same as the guide provided this time last year. So I guess just between the prepared remark comments and that guide, should the read be for us and investors that staying disciplined on cost, but it's all about pouring kerosene in the fire and capturing that TAM?

It is the latter of the 2. So we want to be disciplined, and we feel the margins are very healthy at this point. We've made tremendous progress over the last 3 years, and we've been able to reinvest into growth-oriented activities.

Just take a look at the results in '26, what I just said a couple of minutes ago, which is look at the growth in sales and marketing line in Q2, Q3 and Q4, and compare it to some of the other lines like G&A. We're trying to basically take money from one place and put it in another place so we can grow faster, whether it be in R&D or sales and marketing, that's ultimately our goal while still producing very healthy margins, but the goal is to grow faster.

Like we think the opportunity is there. You've heard it from us as a group today, and that's what we're going to continue to do, but also be keeping in mind we have very healthy margins, and we want to take a balanced approach.

Yes. It's a structurally more efficient and capable company than it was 3 years ago. So I think you'll see that going forward where we can balance things in a very strategic way that accomplishes both those goals.

We're fortunate to have the flexibility to be able to make these. We have a very good business model. That's something we're quite proud of, frankly.

Okay. We'll take the last question from Junaid at Truist.

Great. The sweet based pricing that you introduced over the past year, how has the reception been from customers? And is that contributing to these large deal sizes you were alluding to and helping drive broader platform adoption?

Yes. The sweet based pricing continues to resonate with customers. It does, in particular, help with larger transactions and larger customers. And the other thing it does is it helps us close those deals faster because customers can sign up and then determine where to allocate individual licenses over time. So it continues to resonate.

It's still a relatively early offer for us, so it's not yet a significant contributor to the run rate, as we talked about earlier, but customers have been very pleased with the offering and our field has as well. So we expect to continue success there this year.

All right. Appreciate that, guys. Apologies to those we didn't get to. And before we go, I just want to let you know that in addition to both on-site and virtual bus tours this quarter, we'll be attending the Morgan Stanley Conference in San Francisco tomorrow and also the Wells Fargo Software Symposium in Menlo Park on April 9. And we hope to see you at one of those events. Thanks.

Thanks, everyone.

Terrific. Thanks to everyone for joining Needham's Annual Growth Conference. I'm Mike Cikos, lead analyst here covering Cybersecurity and Infrastructure Software. And with me, I'm pleased to host Okta's Executive VP of CorpDev, Monty Gray; and Investor Relations, David Anhalt. Just for a few logistics, I plan to host a fireside chat with Monty and David here, but at any time if the audience has a question, feel free to send it through the Q&A function or via e-mail. You can reach me at [email protected]. I'll do my best to tackle the questions and subject matter while we have Monty and David here.

With that, Monty and David, thank you very much for joining us. We really do appreciate it.

No, welcome. Thank you.

Just to start, maybe for Monty for folks that may not have had the opportunity to engage with you before. Can you just do a quick overview of your role at the firm? And then also just double questions here for anyone who's either new to the story or revisiting the story, just a quick overview of who and what Okta is as far as customer value prop.

Sure. No, I appreciate it. So thanks again for having us over here, looking forward to the conversation. Monty Gray, I've been with Okta for about 7 years now. My role, responsible for corporate development covers a broad spectrum of things, anything from company strategy to M&A, technology partnerships, getting involved in some cross-functional initiatives that we might have that don't sit within a given silo. So it's a good role, I get to see things that are a couple of horizons out and things are happening immediately today. So it's pretty fun from that perspective.

To answer your question, what is Okta doing or our customer value proposition. The best way to think about us is we are the largest independent neutral identity vendor in the space today in the market? And what does that mean, right? And we'll get into it, I'm sure with some of these conversations. It's really about enabling organizations to adopt the technologies that they want to adopt, and that's part of our -- that's our tagline as a company to safely adopt any -- to enable a company to safely adopt any technology. And then also just securely do that as well. So security is a big part of what we do. And I'm sure we'll have plenty of time to get into what that means.

Okay. Excellent. Big picture question first. And I know the identity market has been around for a while now. But historically been viewed through different lenses, segments, if you will, whether it's IM, IGA, PAM, the cybersecurity industry loves acronyms. But there's always been a view that these swim lanes are or should converge which seems to be playing out here over the last 12 to 18 months. And so with where we are today and the convergence of what have historically been viewed as separate swim lanes, like -- the question that we often receive from investors is just the why now? Like why has this moment come to fruition today versus where we were 3, 5 years ago, et cetera?

Yes. And I think there's -- the best way to approach that question I think is to understand a little bit of the history of identity, right? The first iteration of identity would be thinking of identity is an enablement function. You're enabling the adoption of a certain piece of technology within the enterprise. And that -- if you go back 10, 15 years, that was really what was happening. You want to deploy Workday to the cloud. You want to deploy Salesforce to the cloud or some other systems of record to the cloud you quickly realize I needed an identity system to help me provision that, put users into that system to not only do for that system, but other systems I'm doing. So there's a big enablement phase that was happening within the industry.

Then that quickly maturated into a security phase, which is, okay, great. I have only users who have access to all the systems that I have now deployed within the organization, including my e-mail system, for example, how do I actually start to secure those? And then you start to get into the other acronyms, right? Whether it's IGA, which is governance, right? How do I provide governance meaning establishing the right entitlements, doing the right reporting to make sure people write -- that people have access to what they're supposed to have access to. The life cycle management, meaning if a company joins a company -- an employee joins a company through their different roles and responsibilities to lead the company, do the right access through that whole life cycle. That's what governance really encompasses.

And then privileged access management is as the name implies, is can I lock down those resources, resources meaning systems or applications that are of high value. So it could be an administrative function with any given area, it could be a critical piece of your infrastructure. And can the user have the right access at the right moment in time to actually do what they're supposed to do in those systems in an appropriate manner.

So a lot of complexity came with that, right, in that first phase. And what we're seeing now is like with a lot more security awareness, coupled with adoption to the cloud, people are saying, okay, this is great, but we would love to actually have this a little bit more simpler to have one system doing this versus multiple systems where you can actually have some gaps, have some leakage in terms of policies and access.

The main driver for that, candidly, is probably just adopting the cloud and having a cloud identity system be prevalent and be adopted within the organization. That enables companies to actually say, okay, great, I have a cloud identity system. I now want a cloud Privileged Access Management system, Cloud PAM system and a cloud governance system we're now seeing that convergence actually happen in real time, and that's what we've been investing in over the past couple of years.

Excellent. So that sets the table then you obviously have these offerings on the market today. How would you describe recent traction for your privileged access or Okta governance offerings? Where are we in terms of product maturity or even how the ecosystem, whether it's your own sellers or partners going out and rallying around these products to then go sell on behalf of you do to your customer base?

Yes. Yes. So as we mentioned in our call, and we've stated publicly, you've heard the comments from Todd and Brett, we've done extremely well with our governance -- there was a sequencing here, right? The first was identity management, which was a single sign-on, multifactor authentication, getting the directory into the cloud, governance was the next one that came on top of the next use case for us, the next product, which we call IGA, Identity Governance and Administration.

So our IGA product is doing exceptionally well. It's been in the market for a couple of years. It's been a material part of our new product contribution as a company. We're very pleased with that. That's been a really good cross-sell opportunity for us into our installed base of 20,000 customers. Right behind that would be Privileged Access. Privileged Access is probably -- in terms of maturity, in terms of nuance and deployment, it's behind the governance one, but we're very excited about how those two are now -- have gone from development to actually having meaningful contribution to our business going forward.

Great. And this is more like a procedural line of question here, but I was just trying to think through the sales organization itself, can you walk through how it's structurally built to cross-sell these newer offerings that you guys have to the customer base? And then secondarily, like when a customer gives you guys the green light and says, "Hey, we're on board, we're going to adopt what is required for that deployment on the customer's part from like a readiness standpoint?

Yes. So from a customer standpoint, it's really about -- the complexity lies in their environments. Is environment a hybrid environment, meaning is it cloud-based? Is it on-prem? And if you take a step back, what resources are being covered, right? When I talk about resources, I'm referring to the applications and organization applications, infrastructure, as well as databases, for example. There's a whole spectrum of resources. So there's a complexity of the customers' environment. That's one consideration.

The second consideration would be just their readiness from understanding -- think of all the change management aspects that come along with it, which is do they have a good grasp on the policies, entitlements, what they would like that to look like against their infrastructure? And that's where our partners can help, and that's where we -- there's really just kind of this maturity and readiness that we look at from our customers when they're looking to deploy.

And we've seen customers -- because we're cloud -- so the onus is less on the technology deployment itself, it's more on the change management and more on understanding what they want from the business output standpoint. Because of that, we're seeing deployments today that are in the cloud have been measured in weeks and months versus quarters, even years before when it was more like a heavy on-prem deployment. So we're seeing time to value happen much quicker. But it's really about is the customer -- have they gone through that maturity cycle of understanding what they want to do when it comes to best practice within their given environment?

Excellent. And just a cycle and -- I know I'm just asking too many questions at once.

No, this is great.

But for the sales force, can you talk about how they're structured to then go out? Like, is it Mike Cikos is selling the entire portfolio, can you talk through how we're getting that cross-sell?

Yes, we have -- and we specialize our sales force. This is something we've evolved our sales force over the past couple of years, depending on -- reacting to the complexity of our portfolio, reacting to the buying mechanics of our customers. And there's certain specialization that happens in verticals, for example, public sector, that's one. Another would be within certain segments, we have a traditional hunter-farmer model where it's like new business acquisition versus understanding what they have and then cross-selling across that. Specific to governance and privilege on top of identity, access management.

Governance is a natural. What we've observed, it's a natural cross-sell. So the same seller can actually do -- can both look at the identity suite and then also cross-sell governance on top of that, it's a natural extension of it. Privilege can be a little bit more nuanced depending on the environment. At that point, you're probably talking a little bit about resource coverage, meaning Kubernetes cluster or database, something else. And so we do have some specialists that actually support with that as well.

With the -- and sorry, just on that latter point, when thinking about the PAM or the Privileged Access offering, is that tapping into a different persona necessarily or no? Just to be clear on that one. Because it sounds...

This is what I mean by that. Because you can find some customers have matured and centralized their identity department. In that case, it's the same customer, right? If they're more sophisticated - and we like these customers who've gone through this maturation of different departments deploying different identity systems and then maturing into saying, "Hey, I have to rationalize this system." There's -- we're starting to see ourselves, even ourselves as like customer zero, as Okta as a company, we have one organization that covers all different identity use cases for us. We're seeing our largest customers actually do that. And that's a great way for us to have a single conversation with them, elevate the value proposition. And they get the single control plane narrative that happens there.