# Checkly — Uptime Monitoring & Status Pages

Checkly by Checkly Inc. holds a panel rating of 3.5/5 from 6 AI judges (category median 3/5), as of 2026-11-02. Provenance: Rest of world; sovereignty: 1 of 6 dimensions proven.

- Vendor: Checkly Inc. (https://www.checklyhq.com)
- Category: [Uptime Monitoring & Status Pages](https://whats-best.ai/software/uptime-monitoring.md)
- Provenance (editorial classification): Rest of world
- Canonical page: https://whats-best.ai/software/uptime-monitoring/checkly
- Alternatives: https://whats-best.ai/software/uptime-monitoring/checkly/alternatives ([markdown](https://whats-best.ai/software/uptime-monitoring/checkly/alternatives.md))
- Data as of: 2026-11-06 · evaluated 2026-11-02 · oldest source captured 2026-11-01

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: Checkly Inc.
- Headquarters: Incorporated in United States [S9]
- Data hosting: Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan: Not stated on the vendor’s pages as of 1 Nov 2026

## The panel's verdict

Checkly scores highest on checks and locations and pricing transparency (8 flat), with automation and teams close behind; persona-weighted totals range 6.4 to 7.5. Judges repeatedly name monitoring-as-code the strongest part: TypeScript constructs, Terraform and Pulumi providers, with CI gating. Eight monitor types plus Playwright browser checks run from 22 public locations, failures retried and confirmed from a second location before alerting. Weakest is sovereignty: the contracting party is Checkly Inc. of Boston under New York law, the security page states all data is stored in the European Union on AWS eu-west-1 (Ireland), check-result data possibly stored where the check ran, the disaster-recovery fallback is us-east-1, subprocessor locations are largely unstated, with no public information on an EU contracting entity. flagged splits flagged nothing; status pages spread widest, lower scores citing no public information on SMS or webhook subscribers or multiple languages, higher ones crediting tag-based incident automation and the published uptime formula. Reports and reliability reflects the terms' commercially reasonable efforts commitment and no public information on the vendor's own status page.

**Speaks for it:**
- Checks, alert channels, escalation policies and status pages deploy as version-controlled TypeScript or Terraform with CI gating
- Eight monitor types plus Playwright browser checks run from 22 public locations, each failure confirmed from a second location before alerting
- Pricing pages state tier prices, extra monitors at $8 per 25, run overages, SMS and phone quotas per plan, and discounts up to 20% annual, 30% startup and 50% nonprofit
- Status-page automation rules open an incident from a tagged failing check, post the first update and auto-resolve on recovery
- Reporting covers P50, P95 and P99 percentiles, saved views, CSV export and an Analytics API, with retention stated per plan

**Held against it:**
- On-call schedules, rotations, acknowledge-and-resolve and incident timelines show no public information and are delegated to PagerDuty or Opsgenie
- Contracting party is Checkly Inc. of Boston under New York law, disaster-recovery fallback is us-east-1, and subprocessor locations are largely unstated
- The terms commit only to commercially reasonable efforts to maintain availability, with no public information on an SLA with credits
- We found no public information on SCIM provisioning, exportable audit logs, granular per-resource roles or client sub-accounts with their own logins
- Status pages show no public information on SMS or webhook subscribers, per-component subscriptions, multiple languages or embeddable widgets

**Best for:**
- Your team keeps infrastructure in Git and wants checks, alert channels and status pages deployed and gated as code
- You already run PagerDuty or Opsgenie for on-call rotations and want broad alert channels with run-based and time-based escalation feeding them
- You need to budget a year of monitoring from public prices: Starter at $24 per month and Team at $64 per month billed annually, extra monitors at $8 per 25, and a $0 Hobby tier with no credit card required
- You already use Playwright and want to port an existing test suite into scheduled production monitoring

**Avoid if:**
- Your procurement requires an EU contracting party: the terms name Checkly Inc. of Boston under New York law
- You need the monitoring tool itself to run on-call schedules and rotations rather than forwarding to a separate tool
- Your contract requires an availability SLA with credits: the terms commit to commercially reasonable efforts to maintain availability

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Agency Developer | The SaaS Platform Engineer | The Customer Support Lead | The E-Commerce Operations Manager | The Information Security Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Checks, locations & failure confirmation | 4/5 | 4.5/5 | 4.5/5 | 4/5 | 4.5/5 | 4/5 |
| Alerting, escalation & on-call | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3/5 | 3/5 |
| Status pages & incident communication | 3/5 | 3.5/5 | 3.5/5 | 3/5 | 3/5 | 2.5/5 |
| API, monitoring as code & team administration | 3.5/5 | 4/5 | 4/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Uptime reports, data & the vendor's own reliability | 3/5 | 3.5/5 | 3.5/5 | 3/5 | 3/5 | 3/5 |
| European sovereignty | 2/5 | 2.5/5 | 2/5 | 2.5/5 | 2.5/5 | 2.5/5 |
| Pricing transparency | 4/5 | 4/5 | 4/5 | 4/5 | 4/5 | 4/5 |
| **Weighted verdict** | **3.5/5** | **4/5** | **3.5/5** | **3.5/5** | **3/5** | **3/5** |

### The judges

- **The Agency Developer** (v1.0): Runs hosting and maintenance at a fifteen-person web agency with sixty client sites on WordPress, TYPO3 and Shopware. Has learned about an expired certificate from a client's angry phone call once and does not want a second time. Wants HTTP, keyword, SSL and domain expiry checks set up in bulk, client groups with their own status pages and monthly uptime reports, and a price per monitor that still works at two hundred monitors.
- **The SaaS Platform Engineer** (v1.0): Platform engineer at a forty-person B2B SaaS in Berlin, one of four people on the on-call rotation. Wants multi-step API checks with assertions, kept in Terraform next to the services they test, failures confirmed from a second location before anyone is woken, phone calls and escalation when an alert is not acknowledged, and a status page that updates without someone logging in at 3 a.m.
- **The Customer Support Lead** (v1.0): Leads a support team of nine at a software company whose customers are tax advisers and payroll offices. During the last outage the team answered three hundred tickets that all asked the same question. Wants a status page on the company's own domain with components customers recognise, incident templates, subscribers notified by email, a private page for the largest accounts, and an uptime history they can point to in a contract renewal.
- **The E-Commerce Operations Manager** (v1.0): Runs operations for an online shop selling garden furniture in Germany, Austria and Switzerland, with half the year's revenue between March and June. The homepage once answered 200 while the checkout threw an error for six hours. Wants the checkout and the payment page checked, not only the homepage, an SMS or call to whoever is on duty that night, and a report that shows the agency what the downtime cost.
- **The Information Security Officer** (v1.0): Information security officer at a mid-sized logistics company that falls under NIS2 and is working towards ISO 27001. Needs every outage recorded with detection time, response and resolution, in a form an auditor accepts. Reads the subprocessor list before the feature page, because the on-call staff's mobile numbers and the status page subscribers are personal data, and wants single sign-on and an audit log before anyone gets a login.
- **The Skeptic** (v1.0): Has seen "30-second checks from 20 locations" that paged the whole team for a single probe's network glitch, a status page that went down with the product it reported on, and "unlimited SMS" with a fair-use clause on page nine. Asks how a failure is confirmed, how long the history is kept and whether it can be exported, where the monitor itself publishes its own outages — and what leaving would cost.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 1 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Incorporated in US | 0/2 | [S9] |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Access controls: yes · yes · no [S11]
- Admin monitoring: yes · yes [S11]
- Auth0 certifications: Auth0 · SOC 2 Type 2 · ISO 27001 · ISO 27018 [S11]
- Aws certifications: AWS · PCI · HIPAA · ISO · SOC [S11]
- DPA: https://www.checklyhq.com/privacy · yes · EEA · UK · California [S9]
- Encryption: AES256 · encrypted · HTTPS [S11]
- GDPR: yes [S11]
- MFA: yes [S8]
- MFA production: yes [S11]
- Privacy laws: GDPR (2016/679) · EU member state implementations · California Consumer Privacy Act [S9]
- Security measures: reasonably appropriate administrative, physical and technical measures [S9]
- SOC 2: security · availability · confidentiality · privacy · processing integrity · yes [S11]
- SOC 2: yes [S8]
- White hat program: https://www.checklyhq.com/security-response/ · yes [S11]

**Data**
- Account deletion: yes [S11]
- Aggregated retention: 1 year · 30 days · 30 days · 25 months [S8]
- Backup encryption: AWS S3 · AES256 [S11]
- Backup retention: 4 [S11]
- Check results storage: S3 (redundant) · 30 [S11]
- Log systems: 1 · 12 · 1 [S11]
- Post termination deletion: yes · yes · yes [S9]
- Raw retention: 30 · 7 · 7 · 180 [S8]
- Retention check results: 1 · yes [S11]
- Retention log data: 1 [S11]

**Hosting**
- Data region: AWS eu-west-1 (Ireland) · check result data may be stored at region where check was executed [S11]
- Ddos protection: Cloudflare · dedicated DDoS mitigation service · yes [S11]
- Providers: AWS · Vercel [S11]

**Integrations**
- Additional channels: GitLab Alerts · ilert · Spike.sh · Splunk On-Call · StatusPage [S6]
- AI skills: yes [S7]
- Alert channels: Slack · PagerDuty · email · webhook [S3]
- Alert channels: Slack · PagerDuty · Opsgenie · SMS · phone · webhooks [S13]
- Analytics API: An Analytics API is listed under Platform/Reporting [S20]
- Analytics auth: Bearer API key · Authorization · X-Checkly-Account [S21]
- Analytics endpoints: /v1/analytics/metrics/ · /v1/analytics/api-checks/{checkId} · /v1/analytics/browser-checks/{checkId} · /v1/analytics/multistep-checks/{id} · /v1/analytics/playwright-checks/{id} · /v1/analytics/dns/{id} · /v1/analytics/url-monitors/{id} ·… [S21]
- Analytics response format: JSON · check attributes · period · grouped series · metadata [S21]
- API: yes [S18]
- Cicd: GitHub Actions · GitLab · Vercel · Jenkins [S7]
- Cli alternative: yes [S19]
- Cli management: StatusPageV3 · checkly import status-page:<id> [S16]
- Datadog: Datadog · metrics forwarding [S1]
- Datadog: yes [S3]
- Datadog: yes [S12]
- Discord: yes [S6]
- Firehydrant: yes [S3]
- Firehydrant: yes [S6]
- Firehydrant: yes [S12]
- Github actions: GitHub Actions · CI gating [S1]
- Grafana: Grafana · dashboards [S1]
- Grafana: yes [S3]
- Grafana: yes [S12]
- Grafana: Grafana JSON API plugin data source consuming the Analytics API · yes [S21]
- Honeycomb: Honeycomb · observability [S1]
- Honeycomb: yes [S3]
- Honeycomb: yes [S12]
- Iac providers: Terraform · Pulumi [S7]
- Incident io: yes [S6]
- Infrastructure as code: Checkly CLI · Agent Skills · Terraform Provider · Pulumi Provider [S9]
- Microsoft teams: yes [S6]
- Monitoring as code: Checkly CLI · Terraform · Pulumi [S12]
- Ms teams: MS Teams · alerts [S1]
- Ms teams: yes [S3]
- Ms teams: yes [S12]
- Ops genie: yes [S12]
- Opsgenie: OpsGenie · alert routing [S1]
- Opsgenie: yes [S3]
- Opsgenie: yes [S6]

**Legal**
- Assignment: yes · yes [S9]
- Contracting entity: Checkly Inc. · One Boston Place, suite 2600, Boston, MA, U.S.A., 02108 [S9]
- Copyright entity: Checkly Inc. [S11]
- Copyright entity: 2026 · Checkly Inc. [S8]
- Entity: Checkly Inc. [S1]
- Entity: Checkly Inc. · Checkly GmbH [S10]
- Governing law: New York · U.S.A. [S9]
- Jurisdiction: United States [S10]
- Jurisdiction: courts located in New York, New York · yes · yes [S9]
- Last modified: 2026-10-28 [S9]
- Modification notice: support@checklyhq.com · 30 [S9]
- Publicity: yes [S9]

**Pricing**
- Additional API runs: Starter · Team · 1.8 [S8]
- Additional browser runs: Starter · Team · 4 [S8]
- Additional monitors: Starter · Team · 8 [S8]
- Annual discount: 20 [S8]
- Automation plan availability: Team · Enterprise [S16]
- Billed annually plans: annual · 24 [S8]
- Communicate starter: 25 · 500 · yes [S5]
- Communicate team: 50 · 1000 · yes · yes · yes · yes [S5]
- Downgrade effective: end of billing cycle [S8]
- Enterprise custom quote: Enterprise · custom quote [S8]
- Enterprise tier: 100 · 2000 · yes · yes [S5]
- Feature gating: Communicate Starter · Team · Enterprise · Team · Enterprise · Team · Enterprise [S5]
- Fee change notice: publication on the Site permitted · 30 [S9]
- Fees nonrefundable: yes · yes [S9]
- Free signup: yes · GitHub · GitLab · email · no [S1]
- Free subscriber limit: 250 [S17]
- Hobby detect price: Hobby · 0 [S8]
- Hobby free no credit card: no [S8]
- Hobby limits: 1 · 20 · 250 [S5]
- Incident automation plans: Communicate Team · Enterprise [S5]
- Late charge: 1.5 [S9]
- Payment methods: Visa · Mastercard · American Express · Stripe · yes [S8]
- Payment provider: Stripe · yes [S11]
- Per monitor model: 75 · 10 · 50 · monitor · custom · 25 [S13]
- Positioning: flat plan-based [S3]
- Prepaid billing: prepaid upfront [S8]
- Price lock: yes [S8]
- Retention enterprise: 180 · 25 [S10]
- Retention hobby: 7 · 30 [S10]
- Retention starter: 7 · 30 [S10]
- Retention team: 30 · 1 [S10]
- Self serve upgrade downgrade: Hobby · Starter · Team [S8]
- Starter browser overage: 2.6 · 6.5 [S8]
- Starter detect price: Starter · 24 [S8]
- Startup discount: 30 · 50 [S8]
- Subscriber overages: Communicate Starter · Communicate Team · yes [S17]
- Taxes: yes · yes · yes [S9]
- Team browser overage: 2.5 · 6.25 [S8]
- Team detect price: Team · 64 [S8]

**Product**
- Agent skills: yes [S1]
- AI agent integration: yes [S1]
- AI agents: yes [S3]
- AI assistant mcp: yes [S7]
- AI features: yes [S10]
- AI root cause: Rocky AI · yes [S3]
- AI root cause: yes [S7]
- AI root cause analysis: yes [S11]
- Alert channel configuration steps: Create alert channel · Configure Alert Types · Subscribe Checks · Test Integration [S14]
- Alert channel promote to secret: Values can be promoted to encrypted account secrets from the channel UI [S14]
- Alert channel variables secrets: Secret fields accept environment variable or secret references via {{NAME}} syntax [S14]
- Alert channels: Slack · PagerDuty · Opsgenie · Microsoft Teams · email · SMS · phone calls · Discord · Telegram · incident.io · Rootly · FireHydrant · webhooks · 18 [S4]
- Alert channels customizable types: yes [S4]
- Alert channels list: Email · Slack · Discord · Telegram · SMS · Phone Call · Microsoft Teams · GitLab Alerts [S14]
- Alert channels purpose: Alert channels determine how alert notifications reach the team when checks fail, degrade, or recover [S14]
- Alert custom integrations: Webhooks [S14]
- Alert escalation purpose: Alert escalation policies control when and how often alerts are received when checks start failing, degrade, or recover [S15]
- Alert incident management channels: PagerDuty · Opsgenie · FireHydrant · Incident.io · Rootly · ilert · Splunk On-Call · Spike.sh · StatusPage [S14]
- Alert open close behavior: yes [S4]
- Alert routing scope: yes · yes · yes [S6]
- Alert types: failure · degradation · recovery · ssl_expiry [S6]
- Alerting as code: yes [S6]
- Alerts: yes [S11]
- Analytics aggregations: p99 · sum · standard deviation [S21]
- Analytics API: yes · Analytics API returns aggregated or raw check metrics grouped by location or time window for external reporting tools [S21]
- Analytics checks endpoint: POST · yes [S21]
- Analytics quickrange: quickRange · groupBy=runLocation · groupBy=pageIndex · aggregationInterval [S21]
- API check frequency: on request · 10 [S8]
- Authentication options: Google · Github · username and password · SAML 2.0 · Microsoft AD [S11]
- Automatic repair: yes · yes [S7]
- Automation cool down: 5 [S5]
- Automation rule behavior: Rules match checks by tag; auto-open, first update, auto-resolve [S5]
- Automation rules: yes · yes [S16]
- Availability commitment: commercially reasonable efforts · yes [S9]
- Browser check playwright: Node.js · Playwright [S8]
- Browser checks playwright: yes [S12]
- Browsers: Chromium · Firefox · WebKit [S3]
- Brute force protection: auth0.com/docs/attack-protection/brute-force-protection · yes [S11]

**Subprocessors**
- Anthropic: Anthropic · enrich signup data with business information [S10]
- Auth0: Auth0 · identity provider, stores passwords [S10]
- Aws: Amazon Web Services · email and SMS alerts [S10]
- Clay: Clay · CRM data enrichment · yes [S10]
- Google: Google · GSuite email and Drive storage [S10]
- Knock: Knock · product announcements [S10]
- Loops: Loops · marketing emails [S10]
- Mixpanel: Mixpanel · product analytics [S10]
- Openai: OpenAI · AI analysis of test result data · no [S10]
- Segment: Segment · product usage analytics [S10]
- Stripe: Stripe · payment processing [S10]

**Support**
- Alert notification log: Alert notification log tracks delivery success rates per channel [S14]
- Community: Slack · GitHub · YouTube [S7]
- Enterprise options: Premium Support · Onboarding Support · Dedicated Customer Success Engineer · 24x7 Phone Escalation [S8]
- Policy: yes · yes [S9]
- Sms alerts quota: 200 · 0 · 100 · Custom [S8]

247 more facts on the canonical page: https://whats-best.ai/software/uptime-monitoring/checkly

## Questions

### Is Checkly European?

No. whats-best.ai classifies Checkly as Rest of world. Its vendor, Checkly Inc., is incorporated in United States, per [the vendor’s page captured 1 Nov 2026](https://whats-best.ai/evidence/15363).

### Where does Checkly store data?

Not stated on the vendor’s pages as of 1 Nov 2026.

### Does Checkly have a free plan?

Not stated on the vendor’s pages as of 1 Nov 2026.

### What are the best alternatives to Checkly?

As of 2 Nov 2026, the panel rates [Hyperping (3.5/5)](https://whats-best.ai/software/uptime-monitoring/hyperping), [openstatus (3.5/5)](https://whats-best.ai/software/uptime-monitoring/openstatus) and [Oh Dear (3.5/5)](https://whats-best.ai/software/uptime-monitoring/oh-dear) highest among the other 14 Uptime Monitoring & Status Pages products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is [Hyperping](https://whats-best.ai/software/uptime-monitoring/hyperping) (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Checkly alternatives](https://whats-best.ai/software/uptime-monitoring/checkly/alternatives).

## What this page leaves out

- 19 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 17 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown.

## Sources

- [S1] Vendor homepage: https://www.checklyhq.com/ (checked 2026-11-01)
- [S2] Features page (API monitoring): https://www.checklyhq.com/product/api-monitoring/ (checked 2026-11-01)
- [S3] Features page (browser and synthetic monitoring): https://www.checklyhq.com/product/synthetic-monitoring/ (checked 2026-11-01)
- [S4] Features page (heartbeat monitoring): https://www.checklyhq.com/product/heartbeat-monitoring/ (checked 2026-11-01)
- [S5] Features page (status pages): https://www.checklyhq.com/product/status-pages/ (checked 2026-11-01)
- [S6] Features page (alerting): https://www.checklyhq.com/product/alerting/ (checked 2026-11-01)
- [S7] Documentation: https://www.checklyhq.com/docs/ (checked 2026-11-01)
- [S8] Pricing page: https://www.checklyhq.com/pricing/ (checked 2026-11-01)
- [S9] Terms of service: https://www.checklyhq.com/terms/ (checked 2026-11-01)
- [S10] Privacy policy: https://www.checklyhq.com/privacy/ (checked 2026-11-01)
- [S11] Security / trust page: https://www.checklyhq.com/security/ (checked 2026-11-01)
- [S12] Checks, locations & failure confirmation — found from sitemap: https://www.checklyhq.com/product/uptime-monitoring/ (checked 2026-11-01)
- [S13] Checks, locations & failure confirmation — found from sitemap: https://www.checklyhq.com/product/tcp-monitoring/ (checked 2026-11-01)
- [S14] Alerting, escalation & on-call — found from sitemap: https://www.checklyhq.com/docs/communicate/alerts/channels/ (checked 2026-11-01)
- [S15] Alerting, escalation & on-call — found from sitemap: https://www.checklyhq.com/docs/constructs/alert-escalation-policy/ (checked 2026-11-01)
- [S16] Status pages & incident communication — found from sitemap: https://www.checklyhq.com/docs/communicate/status-pages/overview/ (checked 2026-11-01)
- [S17] Status pages & incident communication — found from sitemap: https://www.checklyhq.com/docs/communicate/status-pages/subscriber-notifications/ (checked 2026-11-01)
- [S18] API, monitoring as code & team administration — found from sitemap: https://www.checklyhq.com/docs/concepts/monitoring-as-code/ (checked 2026-11-01)
- [S19] API, monitoring as code & team administration — found from sitemap: https://www.checklyhq.com/docs/integrations/iac/terraform/overview/ (checked 2026-11-01)
- [S20] Uptime reports, data & the vendor's own reliability — found from sitemap: https://www.checklyhq.com/docs/platform/reporting/overview/ (checked 2026-11-01)
- [S21] Uptime reports, data & the vendor's own reliability — found from sitemap: https://www.checklyhq.com/docs/platform/reporting/analytics-api/ (checked 2026-11-01)

---

Cite as: whats-best.ai, "Checkly — Uptime Monitoring & Status Pages", AI panel analysis, as of 2026-11-06. https://whats-best.ai/software/uptime-monitoring/checkly

Corrections: https://whats-best.ai/correct/1353?target=page