More reliable with a workflow developers love

Checkly helps developers to code, test, and scale their monitoring with a CLI-first workflow.

Start for freeRead the docs
acme.check.ts
new BrowserCheck('homepage-browser-check-1', {
  name: 'Browser Check #1',
  frequency: 10,
  regions: ['us-east-1', 'eu-west-1'],
  code: {
    entrypoint: './home.spec.js'
  }
})

new ApiCheck('product-api-check-1', {
  name: 'Product API - fetch products',
  degradedResponseTime: 10000,
  maxResponseTime: 20000,
  requests: {
    url: "https://api.acme.com/v1/products",
    method: "GET",
    assertions: [AssertionBuilder.statusCode().equals(200)]
  }
})

Trusted By Engineering Teams At

Deno logoVercel logo1Password logoRender logoLinkedIn logoCrowdstrike logoAutodesk logo

Every minute of downtime equals $5,600 to $9,000 in losses.

Easy Monitoring at Scale

Set up deep monitoring for your web apps and APIs.

Faster Problem Detection

Be the first to know when things break or go down.

Shorter Downtime

Immediately take action and shorten your time to recover.

Monitoring as code enables toolchain governance

Synthetic monitoring is driven by engineers (developers, SREs, DevOps engineers, …) to gain visibility into how their systems perform. Toolchain governance, on the other hand, is the core theme of directors, central tools teams, and CTOs.

Monitoring workflows that are not developer-first lead to fragmentation across teams, both tool- and process-wise, and make collaboration harder to ultimately result in worse outcomes for the users of the systems being monitored. Monitoring setups defined and configured outside of source control are proving increasingly unsustainable due to the lack of accountability and transparency. The more dysfunctional this feedback loop is, the more key metrics such as MTTD and MTTR will suffer over the medium to long term.

Monitoring as code and its developer-first workflow solves the governance issue.

Quality AssuranceEngineeringDevOpsTestingCodingMonitoring

The same tool for testing and monitoring

Programmatically define your monitoring setup and use the same resources for testing and monitoring to avoid yet another tool in your toolchain.

api.check.ts
new ApiCheck("public-stats-endpoint", {
  name: "API: Public stats",
  alertChannels: [],
  degradedResponseTime: 10000,
  maxResponseTime: 20000,
  frequency: Frequency.EVERY_30S,
  request: {
    url: "https://api.checklyhq.com/public-stats",
    method: "GET",
    followRedirects: true,
    skipSSL: false,
    assertions: [
      AssertionBuilder.statusCode().equals(200),
      AssertionBuilder.jsonBody("$.apiCheckResults").greaterThan(5000_000_000),
    ],
  },
  setupScript: {
    entrypoint: path.join(__dirname, "setup.ts"),
  },
  tearDownScript: {
    entrypoint: path.join(__dirname, "teardown.ts"),
  },
});

Monitoring has never been easier

Checkly's CLI-first workflow integrates seamlessly into existing development processes. From signup to running your first checks, it will only take you a few minutes.

Ship with confidence – monitoring as code explained in three minutes.

Integrates with your workflow

Checkly natively integrates with the tools you love. Trigger checks from Github and Vercel, manage checks with Terraform, and get alerts via Slack, Pagerduty, Discord, and more. Something is missing? Use our top-notch webhooks to build your own integration!

“The CLI has made the concept of monitoring as code a reality in our environment.

The Checkly CLI has enhanced our engineering team's ability to quickly build, validate and deploy an entire suite of checks from their local development environment. ”

Tavares Chambless

Manager, Quality Assurance, Loyal Health

Loyal x Checkly

Try out Checkly for free

Start monitoring your API endpoints and your vital site transactions.

Get started

*No credit card required