Omry Hay

We want to do infrastructure as code platform and not Terraform platform management. So we went on and built that and I think I don't know, maybe 30, 40% of our customers right now are using Terragrunt within the platform. And then we went to deploy more stuff and using more frameworks like Pulumi and CloudFormation and Helm. And I think that was like the first time that we heard it.

We said, okay, there's a lot of traction here. We need to go and build it. And it's aligned with our vision to be multi-framework. So that's how we prioritize that over other stuff.

We said, okay, there's a lot of traction here. We need to go and build it. And it's aligned with our vision to be multi-framework. So that's how we prioritize that over other stuff.

We said, okay, there's a lot of traction here. We need to go and build it. And it's aligned with our vision to be multi-framework. So that's how we prioritize that over other stuff.

Team and people is the most important piece of a company. And what we ended up doing, like firstly in the R&D, we didn't have teams, we didn't have, and we still don't have like teams and we don't have a single ownership. We don't have a front end team and a back end team.

Team and people is the most important piece of a company. And what we ended up doing, like firstly in the R&D, we didn't have teams, we didn't have, and we still don't have like teams and we don't have a single ownership. We don't have a front end team and a back end team.

Team and people is the most important piece of a company. And what we ended up doing, like firstly in the R&D, we didn't have teams, we didn't have, and we still don't have like teams and we don't have a single ownership. We don't have a front end team and a back end team.

and everybody's doing everything and we looked for very versatile people at first because you need people you know to do not their specific job but a lot of stuff around that because you're a small startup you don't have like tens or ten thousand people around you So you need people to not only do their specific job, but also do stuff that you don't have people to do that.

and everybody's doing everything and we looked for very versatile people at first because you need people you know to do not their specific job but a lot of stuff around that because you're a small startup you don't have like tens or ten thousand people around you So you need people to not only do their specific job, but also do stuff that you don't have people to do that.

and everybody's doing everything and we looked for very versatile people at first because you need people you know to do not their specific job but a lot of stuff around that because you're a small startup you don't have like tens or ten thousand people around you So you need people to not only do their specific job, but also do stuff that you don't have people to do that.

You need like engineers doing stuff that you usually don't get a lot of engineers doing. For example, if it's like blog posts and bargaining stuff, and maybe support. So we look for people that are versatile, that can help us grow and be in the position in order to grow themselves within the company as we scale.

You need like engineers doing stuff that you usually don't get a lot of engineers doing. For example, if it's like blog posts and bargaining stuff, and maybe support. So we look for people that are versatile, that can help us grow and be in the position in order to grow themselves within the company as we scale.

You need like engineers doing stuff that you usually don't get a lot of engineers doing. For example, if it's like blog posts and bargaining stuff, and maybe support. So we look for people that are versatile, that can help us grow and be in the position in order to grow themselves within the company as we scale.

So I think there's two terms of scale when you talk about the company. One is the application and the tech, and the other one is the team itself. And I think for the application part, as we're using mostly serverless and mostly AWS, most of the things that we did were scalable by nature. As I mentioned, we used Lambdas, and Lambda can furtherly scale as much as you want.

So I think there's two terms of scale when you talk about the company. One is the application and the tech, and the other one is the team itself. And I think for the application part, as we're using mostly serverless and mostly AWS, most of the things that we did were scalable by nature. As I mentioned, we used Lambdas, and Lambda can furtherly scale as much as you want.

So I think there's two terms of scale when you talk about the company. One is the application and the tech, and the other one is the team itself. And I think for the application part, as we're using mostly serverless and mostly AWS, most of the things that we did were scalable by nature. As I mentioned, we used Lambdas, and Lambda can furtherly scale as much as you want.

But then again, you have to tweak that a little bit. So Lambdas, for example, had a cold start and there's a lot of stuff around it in order to manage that in large scale that you needed to do. And there are a lot of features that weren't around when we started that helped you with that.

But then again, you have to tweak that a little bit. So Lambdas, for example, had a cold start and there's a lot of stuff around it in order to manage that in large scale that you needed to do. And there are a lot of features that weren't around when we started that helped you with that.

But then again, you have to tweak that a little bit. So Lambdas, for example, had a cold start and there's a lot of stuff around it in order to manage that in large scale that you needed to do. And there are a lot of features that weren't around when we started that helped you with that.

But overall, our thinking was how that scales both in terms of the application, both in terms of the infrastructure and the database. But sometimes you take some product or technical debt that you say, hey, nobody will reach a thousand or two thousand of something, but it ends up surprising you.