Sanjay Nagaraj

If you're creating a brand new product, something like what OpenAI came up with, then you're thinking about this as a totally green field in terms of where you can go and solve a brand new problem.

If you're creating a brand new product, something like what OpenAI came up with, then you're thinking about this as a totally green field in terms of where you can go and solve a brand new problem.

We had an interesting aspect where there were parallels in the application security world for us from building what could be looked at as a minimum sellable product, but also there was brand new where like API security as a market did not exist. So we drew from both places in terms of what is required for an existing. I'll give an example.

We had an interesting aspect where there were parallels in the application security world for us from building what could be looked at as a minimum sellable product, but also there was brand new where like API security as a market did not exist. So we drew from both places in terms of what is required for an existing. I'll give an example.

We had an interesting aspect where there were parallels in the application security world for us from building what could be looked at as a minimum sellable product, but also there was brand new where like API security as a market did not exist. So we drew from both places in terms of what is required for an existing. I'll give an example.

In the parallel side of it, Universe in the AppSec world and broader InfoSec world, there existed, always has existed, web application firewalls, which were built for protecting these legacy applications. So we drew some of the key features that are required to be in the API security product from that old world.

In the parallel side of it, Universe in the AppSec world and broader InfoSec world, there existed, always has existed, web application firewalls, which were built for protecting these legacy applications. So we drew some of the key features that are required to be in the API security product from that old world.

In the parallel side of it, Universe in the AppSec world and broader InfoSec world, there existed, always has existed, web application firewalls, which were built for protecting these legacy applications. So we drew some of the key features that are required to be in the API security product from that old world.

But we had to now go and say, on top of that, what is the differentiation that people need from a brand new market where they can go and say, this is the product that actually bridges that gap between legacy applications into your next generation of APIs. So we started to think about that in that terms and obviously approach that to build a V1.

But we had to now go and say, on top of that, what is the differentiation that people need from a brand new market where they can go and say, this is the product that actually bridges that gap between legacy applications into your next generation of APIs. So we started to think about that in that terms and obviously approach that to build a V1.

But we had to now go and say, on top of that, what is the differentiation that people need from a brand new market where they can go and say, this is the product that actually bridges that gap between legacy applications into your next generation of APIs. So we started to think about that in that terms and obviously approach that to build a V1.

with those key features that are needed from what would be from a runtime protection perspective, but key features that are needed from solving an API security as a new problem.

with those key features that are needed from what would be from a runtime protection perspective, but key features that are needed from solving an API security as a new problem.

with those key features that are needed from what would be from a runtime protection perspective, but key features that are needed from solving an API security as a new problem.

There is a concept that we use internally that comes out of actually one of the investors in the company, Unusual Ventures, is something which we look at it as a four lists as an approach. What I mean by that is typically when you go build anything as a roadmap, you're thinking about what are the sellers asking? What are the customers asking? What's the innovation that we want to build?

There is a concept that we use internally that comes out of actually one of the investors in the company, Unusual Ventures, is something which we look at it as a four lists as an approach. What I mean by that is typically when you go build anything as a roadmap, you're thinking about what are the sellers asking? What are the customers asking? What's the innovation that we want to build?

There is a concept that we use internally that comes out of actually one of the investors in the company, Unusual Ventures, is something which we look at it as a four lists as an approach. What I mean by that is typically when you go build anything as a roadmap, you're thinking about what are the sellers asking? What are the customers asking? What's the innovation that we want to build?

that exists. Anything that we do build out as a roadmap is always part of these four characteristics that way. The early versions of the product that we build is always vision and customer driven. It's not sales driven per se, right? And of course, the tech tech part of it would be less at that given point of time.

that exists. Anything that we do build out as a roadmap is always part of these four characteristics that way. The early versions of the product that we build is always vision and customer driven. It's not sales driven per se, right? And of course, the tech tech part of it would be less at that given point of time.

that exists. Anything that we do build out as a roadmap is always part of these four characteristics that way. The early versions of the product that we build is always vision and customer driven. It's not sales driven per se, right? And of course, the tech tech part of it would be less at that given point of time.