Operations | Monitoring | ITSM | DevOps | Cloud

Rocky AI — Checkly’s AI agent — is now Generally Available. We developed Rocky AI over the last ~6 to 8 months. This is an aeon in AI-years. During this period, we learned a ton. About AI, but mostly about how to fit them into an existing SaaS product, not just another chat widget. This is my ramble…

The web was built for humans, but now the agents are taking over. Humans look at a web page and see content rendered by their browser. AI agents see 180,000 tokens of nav bars, footers, and div soup — burning through their context window on junk that makes them slower and stupider. The web needs to evolve, and we as developers are driving the shift. AI agents like Claude Code, Cursor, Codex, and Gemini are how we interact with documentation, CLIs, and products today.

AI coding agents are excellent at writing code. Ask Claude Code, Codex, or Cursor to add a feature, and it just works. At Checkly, we were ready for the new agentic world from the start! Monitoring as Code means your entire monitoring setup lives in your repository. API Checks, Browser Checks, alert channels, status pages; everything is defined in code, managed with the Checkly CLI, and version-controlled like any other part of your stack.

Cover letters are supposed to help you shine, but most of them blur together into the same polite, forgettable paragraphs. The intention is good (“I want them to notice me!”), but the execution… not so much. So, here’s a simple, honest guide to writing a cover letter that actually works, especially if you’re applying to Checkly. Spoiler: shorter is better. And authenticity in this AI era is better than perfect polished perfection.

There are only a few companies that successfully invest in actively monitoring real user flows in production. I’ve been puzzled by the state of the art for many years, because I’m an anxious developer that always needs to know that production is “all right”. How can it be okay for all of us to wait for error logs, thrown exceptions or customer complains to learn about production issues?

We've been running Playwright in production since the beginning. Today, we're going all in. When we first launched Browser Checks with Playwright support, we proved something critical: the most popular test automation framework since Selenium isn't just for testing—it's the foundation of modern production monitoring. But that was just the beginning. Today, we're announcing Playwright Check Suites—our bet on the future of monitoring and the most significant evolution in Checkly's history.

A great status page does more than show uptime—it builds trust, communicates clearly during incidents, and empowers users to stay informed. Here are 10 standout examples of public status pages, with a quick breakdown of what they do well—and where there’s room for improvement.

If your team runs on AWS, getting new tools into your workflow isn’t just about functionality. It’s about how quickly you can procure, integrate, and see value. With Checkly now available on AWS Marketplace, monitoring doesn’t have to be an exception. This launch means Checkly fits into your procurement flow the same way it fits into your CI/CD: seamlessly. No vendor approval bottlenecks, no procurement delays, just faster access to the tools your developers already want to use.

When I started using Playwright, there was a single command that blew me away. I immediately became (and still am) a huge Playwright Codegen fanboy. Playwright's codegen command opens up a browser window, and whatever you do in this window will be recorded. Navigating URLs, clicking links, and filling out form elements—the Playwright inspector records all your actions and generates a Playwright test for you. Magic!

In cybersecurity, defense-in-depth is a fundamental principle – you never rely on a single security measure to protect your systems. The same philosophy applies to application monitoring. No single monitoring approach, no matter how sophisticated, can capture every possible failure mode of your application. This is why layered monitoring isn't just a best practice – it's essential risk mitigation.