Shashwat Sehgal

Nathan and I used to be peers at Meraki, Cisco Meraki, where we built and led the SD-WAN business unit. And then Greg and myself both worked at Splunk for a while where we were building up the observability platform. And in each of these spaces, what we realized was that the cloud native way of application development is extremely powerful.

It gives a lot of very sophisticated primitives in the hands of developers to build things quickly like never before. But it's also got its own pitfalls, which is that it can make application development very complicated. And this gives security teams a very hard time securing access. Securing access as a use case has been around for the longest time, right?

It gives a lot of very sophisticated primitives in the hands of developers to build things quickly like never before. But it's also got its own pitfalls, which is that it can make application development very complicated. And this gives security teams a very hard time securing access. Securing access as a use case has been around for the longest time, right?

It gives a lot of very sophisticated primitives in the hands of developers to build things quickly like never before. But it's also got its own pitfalls, which is that it can make application development very complicated. And this gives security teams a very hard time securing access. Securing access as a use case has been around for the longest time, right?

The only thing that's evolved over the last 20-30 years is what it is that organizations are interested in securing. Before internet, securing access mostly just meant you have your physical buildings and you need to secure access to the physical workspaces.

The only thing that's evolved over the last 20-30 years is what it is that organizations are interested in securing. Before internet, securing access mostly just meant you have your physical buildings and you need to secure access to the physical workspaces.

The only thing that's evolved over the last 20-30 years is what it is that organizations are interested in securing. Before internet, securing access mostly just meant you have your physical buildings and you need to secure access to the physical workspaces.

In the early days of computers, the early days of the internet, when the most prized possession of a company used to be a data center and specifically data and applications hosted within a data center. In that world, securing access really just meant securing access to the network perimeter of the data center.

In the early days of computers, the early days of the internet, when the most prized possession of a company used to be a data center and specifically data and applications hosted within a data center. In that world, securing access really just meant securing access to the network perimeter of the data center.

In the early days of computers, the early days of the internet, when the most prized possession of a company used to be a data center and specifically data and applications hosted within a data center. In that world, securing access really just meant securing access to the network perimeter of the data center.

And now, as the world has become more cloud-native, the prized jewels of a company are increasingly in SaaS and in the cloud. We are firmly tackling the problem of securing cloud access. That is what we do. Help secure access to a company's crown jewels in the cloud, no matter who's trying to access that infrastructure or that data.

And now, as the world has become more cloud-native, the prized jewels of a company are increasingly in SaaS and in the cloud. We are firmly tackling the problem of securing cloud access. That is what we do. Help secure access to a company's crown jewels in the cloud, no matter who's trying to access that infrastructure or that data.

And now, as the world has become more cloud-native, the prized jewels of a company are increasingly in SaaS and in the cloud. We are firmly tackling the problem of securing cloud access. That is what we do. Help secure access to a company's crown jewels in the cloud, no matter who's trying to access that infrastructure or that data.

It's a never-ending process, really. I wish I could say that there was a point in time when we knew we had nailed down the MVP. Our very first deployable version of a product which we put in the hands of an actual customer was probably within three months of when we started. We started the company in late 2022. We started building and by February of 2023, we had our first customer deployment

It's a never-ending process, really. I wish I could say that there was a point in time when we knew we had nailed down the MVP. Our very first deployable version of a product which we put in the hands of an actual customer was probably within three months of when we started. We started the company in late 2022. We started building and by February of 2023, we had our first customer deployment

It's a never-ending process, really. I wish I could say that there was a point in time when we knew we had nailed down the MVP. Our very first deployable version of a product which we put in the hands of an actual customer was probably within three months of when we started. We started the company in late 2022. We started building and by February of 2023, we had our first customer deployment

It worked, thankfully, and we were able to close that customer contract by March or April of 2023. And ever since then, it's been a stream of, okay, let's find another customer that looks like the last customer we closed and make sure the MVP works for their specific environment. That has been our philosophy ever since then.

It worked, thankfully, and we were able to close that customer contract by March or April of 2023. And ever since then, it's been a stream of, okay, let's find another customer that looks like the last customer we closed and make sure the MVP works for their specific environment. That has been our philosophy ever since then.

It worked, thankfully, and we were able to close that customer contract by March or April of 2023. And ever since then, it's been a stream of, okay, let's find another customer that looks like the last customer we closed and make sure the MVP works for their specific environment. That has been our philosophy ever since then.

Always keep shipping, keep building whatever is necessary, have very tight feedback loops between customers and between our engineering team so that we can iterate, get their feedback and if necessary, build the next feature that would help them gain even more value out of the product. In terms of what we used, I think we've been very nimble in using all kinds of tooling.