Guy Guzner

And one thing that I realized is that even if we were isolating people and the technology was great, it was never breached, we still didn't prevent breaches entirely from happening because people were still misusing their identities. Savvy was about taking this to the next level and moving from the network to the application, to the user level and to the identities.

We actually took our time building our MVP. I think that one of the lessons that we learned when you build enterprise software, you don't get that many chances with customers, so you need to be more ready. And we've taken the time to consider different architectures. We went and we visited 10 companies and saw what was the latest and greatest developments.

We actually took our time building our MVP. I think that one of the lessons that we learned when you build enterprise software, you don't get that many chances with customers, so you need to be more ready. And we've taken the time to consider different architectures. We went and we visited 10 companies and saw what was the latest and greatest developments.

We actually took our time building our MVP. I think that one of the lessons that we learned when you build enterprise software, you don't get that many chances with customers, so you need to be more ready. And we've taken the time to consider different architectures. We went and we visited 10 companies and saw what was the latest and greatest developments.

And it was a big change because in Fireglass, when I started it in 2014, the cloud, it was there. AWS and Microsoft started with Azure, but actually really developing Cloud Native applications wasn't that easy. We started trying to use containers and dockers and ran into a lot of issues. And 10 years later, it's completely different. The ecosystem has matured.

And it was a big change because in Fireglass, when I started it in 2014, the cloud, it was there. AWS and Microsoft started with Azure, but actually really developing Cloud Native applications wasn't that easy. We started trying to use containers and dockers and ran into a lot of issues. And 10 years later, it's completely different. The ecosystem has matured.

And it was a big change because in Fireglass, when I started it in 2014, the cloud, it was there. AWS and Microsoft started with Azure, but actually really developing Cloud Native applications wasn't that easy. We started trying to use containers and dockers and ran into a lot of issues. And 10 years later, it's completely different. The ecosystem has matured.

We were able to make going to Cloud Native right from the beginning, have a microservices architecture, build our backend on top of Golang, use GraphQL for management, implement a CI-CD pipeline. I think that in every point we needed to make a technology decision, there were new solutions out there that have evolved just in the last few years. And it's just amazing.

We were able to make going to Cloud Native right from the beginning, have a microservices architecture, build our backend on top of Golang, use GraphQL for management, implement a CI-CD pipeline. I think that in every point we needed to make a technology decision, there were new solutions out there that have evolved just in the last few years. And it's just amazing.

We were able to make going to Cloud Native right from the beginning, have a microservices architecture, build our backend on top of Golang, use GraphQL for management, implement a CI-CD pipeline. I think that in every point we needed to make a technology decision, there were new solutions out there that have evolved just in the last few years. And it's just amazing.

So overall, it took us a little bit over a year to to get to an MVP, but the architecture that we've built, we've built it for scale and resilience, and we hardly had to change that architecture since that first release.

So overall, it took us a little bit over a year to to get to an MVP, but the architecture that we've built, we've built it for scale and resilience, and we hardly had to change that architecture since that first release.

So overall, it took us a little bit over a year to to get to an MVP, but the architecture that we've built, we've built it for scale and resilience, and we hardly had to change that architecture since that first release.

That's a good question because it's hard. I think it's a combination of talking with customers and understanding their pain points, but that doesn't give you everything. Because customers will not necessarily tell you about... what to build or if there's a new way to solve something that they will be looking mostly for kind of the same solutions.

That's a good question because it's hard. I think it's a combination of talking with customers and understanding their pain points, but that doesn't give you everything. Because customers will not necessarily tell you about... what to build or if there's a new way to solve something that they will be looking mostly for kind of the same solutions.

That's a good question because it's hard. I think it's a combination of talking with customers and understanding their pain points, but that doesn't give you everything. Because customers will not necessarily tell you about... what to build or if there's a new way to solve something that they will be looking mostly for kind of the same solutions.

So it's looking at what customers are dealing with. It's looking at what is developing in terms of technology in the market. the whole ai transition and transformation and a lot of it in the end it's just based on years of experience of building products of understanding trends in cyber security and taking some guesses or gambles and then the thing is to

So it's looking at what customers are dealing with. It's looking at what is developing in terms of technology in the market. the whole ai transition and transformation and a lot of it in the end it's just based on years of experience of building products of understanding trends in cyber security and taking some guesses or gambles and then the thing is to

So it's looking at what customers are dealing with. It's looking at what is developing in terms of technology in the market. the whole ai transition and transformation and a lot of it in the end it's just based on years of experience of building products of understanding trends in cyber security and taking some guesses or gambles and then the thing is to

to have some experiments with the product, create some prototype, create some specific features, run them by customers, collect the feedback, have those short loops of deployment and then see what works and take it from there.