One of our goals here at Checkly is to make it easier for developers to ship excellent software. But let’s face it, getting features out is only a tiny fraction of the story. Fast-moving development teams also break things. And the more things you build, the more things can go wrong. And trust me, they will. This is where API and end-to-end monitoring helps. Define automated test suites that check all your properties constantly and guarantee that everything’s up and running. All the time.

We’re heavy end-to-end monitoring users here at Checkly and always experiment with how to architect our tests the best way. Over the past months, we’ve settled on a few workflows that make it much easier to spin up new tests, avoid code duplication, and make the entire test setup easier to manage. One of those strategies is to strictly separate concerns in our tests.

The monitoring and testing of public applications and APIs is challenging by itself. What should you test? How often should you run your tests? And who should be alerted? A scalable monitoring setup includes many hidden details, but technically it’s straightforward. Call public APIs and see if they do what they’re supposed to.

Today, I'm excited to share the release of a long-planned and requested feature - our new Check Overview Page. Until now, Checkly enabled you to troubleshoot single alerts, but a deep dive into the long-term performance trends was limited. That is not the case anymore. In the new Check Overview, we’re introducing the enhanced analytics in four distinct categories: The update is focused on two important outcomes.

We all know that pay is just as hard as it is important. Having a team distributed over 11+ countries makes pay even harder than in a traditional setup. I joined Checkly in mid-2021 with the promise of a fair and transparent culture in a remote tech startup and my goal was clear: make Checkly one of the best employers in our industry. A topic that I wanted to tackle early on was pay. How can we make pay less nebulous and more transparent, fair, and predictable?

One of Checkly's strengths is the capability to monitor key transactions on your site. It'd be missed opportunity if we didn't reuse it to monitor our own product! But for some important flows that comes with a couple of pitfalls. In this post, we'll take a closer look at how we monitor one of our top key flows: signup.

Checkly has released a new runtime version 2021.10. This is great news for anyone creating browser checks in Checkly, as we have added some new features and brought everything up to date.

Checkly has released a change to the way API keys are created and managed. In the past, API keys were account-scoped. These account-scoped keys have full access rights to your Checkly account and no accountability to which user is using the key. When we originally built Checkly, we made it a tool to enable individual developers to quickly and easily set up browser and API checks. We help ensure your web applications are up and running and send alerts when something goes wrong.

Today, I'm super excited to announce our new Performance and Error tracing features for all Playwright-based browser checks. One of our key initiatives is supporting you with deeper insights into what is causing issues in the web apps you monitor with Checkly. With this new set of features we give you actionable data for easy debugging; Collected automatically with no extra code needed. Of course, fixing bugs in Production is great, but catching bugs before they go live is even better!

Today, we are super happy to announce the next chapter for Checkly with a $10M Series A round led by CRV, joined by existing investors Accel, Mango Capital and Guillermo Rauch. This investment allows us to double down on our prime goal: building the best monitoring and E2E-testing platform for developers. What does that mean?