Konrad Niemiec

And that's how I got started. A little over two years ago, decided to venture out on my own at the time and try to solve this problem.

And that's how I got started. A little over two years ago, decided to venture out on my own at the time and try to solve this problem.

So we actually built two MVPs. So the thing we're launching right now, our free forever plan is actually the second iteration of their product. So first I'll talk about the first one. It took us around maybe six to nine months to build the initial iteration of the product. And we hosted most of the things on AWS. We used GitHub, of course.

So we actually built two MVPs. So the thing we're launching right now, our free forever plan is actually the second iteration of their product. So first I'll talk about the first one. It took us around maybe six to nine months to build the initial iteration of the product. And we hosted most of the things on AWS. We used GitHub, of course.

So we actually built two MVPs. So the thing we're launching right now, our free forever plan is actually the second iteration of their product. So first I'll talk about the first one. It took us around maybe six to nine months to build the initial iteration of the product. And we hosted most of the things on AWS. We used GitHub, of course.

And we were focused on a bunch of different problems and trying to figure out which frameworks should we focus on, which languages should people use. We first started with Go because that's what we were doing locally. But then we also wanted some front-end SDKs because we had a full-stack app. So we were really trying to figure out the breadth of things.

And we were focused on a bunch of different problems and trying to figure out which frameworks should we focus on, which languages should people use. We first started with Go because that's what we were doing locally. But then we also wanted some front-end SDKs because we had a full-stack app. So we were really trying to figure out the breadth of things.

And we were focused on a bunch of different problems and trying to figure out which frameworks should we focus on, which languages should people use. We first started with Go because that's what we were doing locally. But then we also wanted some front-end SDKs because we had a full-stack app. So we were really trying to figure out the breadth of things.

We ended up writing a component in Rust that helps users deploy things in their own infrastructure if they want some additional backup, which users can use now. And it took us around six to nine months for that first iteration of the product.

We ended up writing a component in Rust that helps users deploy things in their own infrastructure if they want some additional backup, which users can use now. And it took us around six to nine months for that first iteration of the product.

We ended up writing a component in Rust that helps users deploy things in their own infrastructure if they want some additional backup, which users can use now. And it took us around six to nine months for that first iteration of the product.

Yeah, so at first we were really trying to figure out, hey, how do we build a really scalable and usable system? Trying to unlock what is a good developer experience and what is something that appears simple, appears very intuitive, but is also obviously very difficult to build yourself and contains a lot of complexity under the hood was I think the biggest thing that we were struggling with.

Yeah, so at first we were really trying to figure out, hey, how do we build a really scalable and usable system? Trying to unlock what is a good developer experience and what is something that appears simple, appears very intuitive, but is also obviously very difficult to build yourself and contains a lot of complexity under the hood was I think the biggest thing that we were struggling with.

Yeah, so at first we were really trying to figure out, hey, how do we build a really scalable and usable system? Trying to unlock what is a good developer experience and what is something that appears simple, appears very intuitive, but is also obviously very difficult to build yourself and contains a lot of complexity under the hood was I think the biggest thing that we were struggling with.

How do you make something that checks all the boxes, has the features that a user expects, especially since we're coming in adjacent to an existing space?

How do you make something that checks all the boxes, has the features that a user expects, especially since we're coming in adjacent to an existing space?

How do you make something that checks all the boxes, has the features that a user expects, especially since we're coming in adjacent to an existing space?

Feature flagging tools and experimentation tools out there exist, so we needed to figure out which one of those existing requirements to pull into our current system, but then really focusing on how do we make this system simple and really easy to use for engineers.

Feature flagging tools and experimentation tools out there exist, so we needed to figure out which one of those existing requirements to pull into our current system, but then really focusing on how do we make this system simple and really easy to use for engineers.

Feature flagging tools and experimentation tools out there exist, so we needed to figure out which one of those existing requirements to pull into our current system, but then really focusing on how do we make this system simple and really easy to use for engineers.