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?
We've recently launched a brand new in-browser editor for our browser check creation experience! Browser checks are Javascript-powered Playwright/Puppeteer scripts that run on deploy or on a schedule for testing and monitoring websites and web apps. While this new experience centers around an upgraded text editor, it is much more than just that.The new browser check creation experience builds on the popular Monaco editor from Microsoft, which also powers VS Code under the hood.
We just released a big change on how often you can schedule your API and Browser checks. Together with our launching customer RMS — a leading property management solution — we looked at how we can catch hiccups and errors of mission-critical apps as early as possible and get better insights on uptime across the board.
Our product & dev team has been cranking out so many small, medium and big updates the last ~2 months, we thought we'd do a comprehensive sum up. Grab some coffee ☕️ and strap yourself in: the list is quite long!
