Hannes Lenke

I founded one startup in 2010 in testing, mobile testing, and back then we helped test automation people and test automation engineers to ensure that their mobile apps are working on production and on staging. We sold that business to Source Labs end of 2016.

And what we've seen there, what I've seen there is lots of companies that are developing end-to-end tests are using these tests to really understand how their applications are doing from production, right? So really making sure that they capture problems there. Realizing that in 2019, I thought, okay, the world is changing towards cross-functional teams, DevOps teams, et cetera.

And what we've seen there, what I've seen there is lots of companies that are developing end-to-end tests are using these tests to really understand how their applications are doing from production, right? So really making sure that they capture problems there. Realizing that in 2019, I thought, okay, the world is changing towards cross-functional teams, DevOps teams, et cetera.

And what we've seen there, what I've seen there is lots of companies that are developing end-to-end tests are using these tests to really understand how their applications are doing from production, right? So really making sure that they capture problems there. Realizing that in 2019, I thought, okay, the world is changing towards cross-functional teams, DevOps teams, et cetera.

On the other side, you already have companies realizing what we do in production monitoring doesn't fit our processes. We need to use end-to-end tests to really understand if our website, APIs, etc. are up or down. I figured, okay, we need a new tool that is really made for developers, made for that use case, because there wasn't a tool back then.

On the other side, you already have companies realizing what we do in production monitoring doesn't fit our processes. We need to use end-to-end tests to really understand if our website, APIs, etc. are up or down. I figured, okay, we need a new tool that is really made for developers, made for that use case, because there wasn't a tool back then.

On the other side, you already have companies realizing what we do in production monitoring doesn't fit our processes. We need to use end-to-end tests to really understand if our website, APIs, etc. are up or down. I figured, okay, we need a new tool that is really made for developers, made for that use case, because there wasn't a tool back then.

I tried to find solutions on the internet that are really solving that kind of problem. I recognized that there was a Dutch guy living in Berlin, like two kilometers away from me, creating a side project called Checkly back then. Tim became a co-founder in 2020.

I tried to find solutions on the internet that are really solving that kind of problem. I recognized that there was a Dutch guy living in Berlin, like two kilometers away from me, creating a side project called Checkly back then. Tim became a co-founder in 2020.

I tried to find solutions on the internet that are really solving that kind of problem. I recognized that there was a Dutch guy living in Berlin, like two kilometers away from me, creating a side project called Checkly back then. Tim became a co-founder in 2020.

Long story short, we took that side project, made it a real company beginning of 2020, and since then grew to thousands of users, thousand paying customers, etc.

Long story short, we took that side project, made it a real company beginning of 2020, and since then grew to thousands of users, thousand paying customers, etc.

Long story short, we took that side project, made it a real company beginning of 2020, and since then grew to thousands of users, thousand paying customers, etc.

Tim, my co-founder, he started to write the first code in 2018, end of 2018, and really built Checkly in public. He built it as an indie hacker project or project aimed to help indie hackers to really to understand how their applications are doing and then started to talk about it, right? He started to talk about numbers, so revenue numbers, etc.,

Tim, my co-founder, he started to write the first code in 2018, end of 2018, and really built Checkly in public. He built it as an indie hacker project or project aimed to help indie hackers to really to understand how their applications are doing and then started to talk about it, right? He started to talk about numbers, so revenue numbers, etc.,

Tim, my co-founder, he started to write the first code in 2018, end of 2018, and really built Checkly in public. He built it as an indie hacker project or project aimed to help indie hackers to really to understand how their applications are doing and then started to talk about it, right? He started to talk about numbers, so revenue numbers, etc.,

but also about the technology that he applied to develop Checkneon, right? And the first version was a very simple version posted on Heroku, right? So it was a Postgres DB. It was a very simple UI and enabled you to monitor APIs. and later on also UIs, so websites, with a framework back then called Puppeteer.

but also about the technology that he applied to develop Checkneon, right? And the first version was a very simple version posted on Heroku, right? So it was a Postgres DB. It was a very simple UI and enabled you to monitor APIs. and later on also UIs, so websites, with a framework back then called Puppeteer.

but also about the technology that he applied to develop Checkneon, right? And the first version was a very simple version posted on Heroku, right? So it was a Postgres DB. It was a very simple UI and enabled you to monitor APIs. and later on also UIs, so websites, with a framework back then called Puppeteer.

Tim was very vocal on Twitter about what he did and that attracted the first users really. And then we started beginning of 2020 to iterate very quickly on the user feedback that we got. and adding more features, adding a framework that is called Playwright for test automation, which is now our prime framework that we're using to enable our users really to create tests.