Sanjay Nagaraj

They all come from varying degrees of experiences, but their single most in their mind is, are they solving a customer's problem?

They all come from varying degrees of experiences, but their single most in their mind is, are they solving a customer's problem?

They all come from varying degrees of experiences, but their single most in their mind is, are they solving a customer's problem?

As we started the company itself, the focus was a lot more on runtime protection from an API security perspective. But one thing that kept coming back to us was, hey, it's all nice that you're able to discover the APIs and able to identify the APIs in the data, give us visibility into it, but also protect it at runtime.

As we started the company itself, the focus was a lot more on runtime protection from an API security perspective. But one thing that kept coming back to us was, hey, it's all nice that you're able to discover the APIs and able to identify the APIs in the data, give us visibility into it, but also protect it at runtime.

As we started the company itself, the focus was a lot more on runtime protection from an API security perspective. But one thing that kept coming back to us was, hey, it's all nice that you're able to discover the APIs and able to identify the APIs in the data, give us visibility into it, but also protect it at runtime.

But we want to be able to identify these vulnerabilities that are getting exploited at runtime in our pre-production system, right? So the mistake that we did, if I were to wind the clock back a long time ago, was we maybe delayed enabling that functionality for some of the customers, maybe about six months to a year. I wish that we had acted on that a little bit sooner than what we did.

But we want to be able to identify these vulnerabilities that are getting exploited at runtime in our pre-production system, right? So the mistake that we did, if I were to wind the clock back a long time ago, was we maybe delayed enabling that functionality for some of the customers, maybe about six months to a year. I wish that we had acted on that a little bit sooner than what we did.

But we want to be able to identify these vulnerabilities that are getting exploited at runtime in our pre-production system, right? So the mistake that we did, if I were to wind the clock back a long time ago, was we maybe delayed enabling that functionality for some of the customers, maybe about six months to a year. I wish that we had acted on that a little bit sooner than what we did.

But the thing finally worked out as in the same, what I consider as a delay and a little bit of a failure on our end turned out to be a bit of a success. The reason is we did not go and build a me too.

But the thing finally worked out as in the same, what I consider as a delay and a little bit of a failure on our end turned out to be a bit of a success. The reason is we did not go and build a me too.

But the thing finally worked out as in the same, what I consider as a delay and a little bit of a failure on our end turned out to be a bit of a success. The reason is we did not go and build a me too.

When we realized that delay or the failure, but instead we doubled down and we said, let's go solve this the right way because customers would be benefited by us innovating on it, like going back to the minimum sellable product that way rather than just going and doing the table stakes. We took it to the next level to say, what should that differentiation be?

When we realized that delay or the failure, but instead we doubled down and we said, let's go solve this the right way because customers would be benefited by us innovating on it, like going back to the minimum sellable product that way rather than just going and doing the table stakes. We took it to the next level to say, what should that differentiation be?

When we realized that delay or the failure, but instead we doubled down and we said, let's go solve this the right way because customers would be benefited by us innovating on it, like going back to the minimum sellable product that way rather than just going and doing the table stakes. We took it to the next level to say, what should that differentiation be?

So eventually when we went and launched our testing product, it's getting used everywhere. For example, today, because of the innovation that's come with it, we were able to replace some of the DAS tooling that the customers have, which are really not getting used from when it comes to APIs. So yeah, some of these failures that we got converted into successes, but the key was success.

So eventually when we went and launched our testing product, it's getting used everywhere. For example, today, because of the innovation that's come with it, we were able to replace some of the DAS tooling that the customers have, which are really not getting used from when it comes to APIs. So yeah, some of these failures that we got converted into successes, but the key was success.

So eventually when we went and launched our testing product, it's getting used everywhere. For example, today, because of the innovation that's come with it, we were able to replace some of the DAS tooling that the customers have, which are really not getting used from when it comes to APIs. So yeah, some of these failures that we got converted into successes, but the key was success.

keeping our focus on executing and learning from some of those mistakes.

keeping our focus on executing and learning from some of those mistakes.