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. From Browser Checks to Check Suites: Our Evolution Our Browser Checks introduced Playwright to production monitoring, but they came with constraints. We provided curated runtime dependencies, a single test spec per check, and a managed environment that worked well for many use cases. Playwright Check Suites removes every limitation. You’re no longer adapting Playwright to fit our platform. You’re running it exactly as you do locally—with full control over: Your entire playwright.config.ts — Every setting, every configuration, exactly as written Complete dependency control — Private packages, custom registries, any npm module you need Full project support — Multi-browser configurations, device emulation, your exact setup tailored to your environments Granular test selection — Use tags (@critical, @smoke), projects, or any combination Your test organization — Multiple specs, test suites, however you structure your code This isn’t a wrapper. This isn’t an abstraction. This is native Playwright execution in production. What This Unlocks 1. Zero Rewrite Required Your existing E2E tests become production monitors immediately. The Playwright projects you’re already maintaining, the test suites you’ve invested hundreds of hours building—they run as-is. No translation layer. No compromises. No technical debt. 2. Future-Proof Your Monitoring When Playwright ships AI-powered test generation next month, you’ll have it. When self-healing locators arrive, you’ll have them. When the next breakthro…