Compare · RealUptime Monitor
RealUptime Monitor vs Checkly
Checkly is a code-first monitoring platform built natively on Playwright: browser checks, multistep checks, and imported Playwright test suites all run as production monitors, priced by monthly check-run volume across four tiers. RealUptime Monitor checks uptime, TLS/domain expiry, DNS, TCP ports, cron heartbeats, and (Scale plan) a closed seven-action browser check, priced by monitor count with on-call rotations and a status page in the same account.
Real-browser (Playwright) checks
Partial
Scale plan, up to 10 per account: a closed seven-action step vocabulary (goto/click/fill/waitForSelector/assertText/assertVisible/screenshot) run in headless Chromium from one region (iad), no raw scripts or imported Playwright test suites, no per-run bill
Have
native Playwright engine runs actual Chromium, Firefox, or WebKit; existing Playwright test suites import directly as monitors, per Checkly's own product page
Free tier
Have
10 monitors, 4 regions, $0/mo
Have
Hobby plan: 10 uptime monitors, 1,000 browser check runs and 10,000 API check runs a month, 6 locations, 1 user, $0/mo
Pricing model
Have
flat monthly price per tier by monitor count: Free, Growth ($28.99/mo), Scale ($78.99/mo)
Partial
priced by monthly check-run volume, not a flat per-monitor count: Starter $24/mo (3,000 browser, 25,000 API runs), Team $64/mo (12,000 browser, 100,000 API runs), both usage-capped
Check interval minimum
Have
1 minute on Free and Growth, 30 seconds on Scale
Partial
2 minutes on Hobby; 1 minute on Starter ($24/mo); 30 seconds on Team ($64/mo); 1 second only on Enterprise
Regions checked per run
Have
every region the plan includes checked and shown together on every run (four regions on Free, eight on Growth, all ten on Scale)
Partial
6 public locations on Hobby and Starter; the full 22+ location pool is Team and above, and simultaneous multi-region checks specifically require Checkly's parallel-scheduling option rather than its round-robin default, per Checkly's own blog announcement
Monitor types beyond HTTP(S)
Partial
TCP and TLS port checks, DNS record checks, and heartbeat/cron push monitoring, plus HTTP(S) endpoints
Partial
API and browser checks with Playwright, plus multistep checks and heartbeat monitoring; no DNS or TCP port checks named on its product pages
On-call rotations and escalation policies
Have
rotations, escalation policies, and acknowledgement on Growth and Scale; pages by email, Slack, webhook, or your PagerDuty, with no phone or SMS paging of its own
Partial
SMS and phone-call alerting are included from the Team plan ($64/mo); no rotation scheduling or escalation-policy builder is named on its pricing or feature pages
Public status page
Have
unlimited status pages, custom domain, on Growth and Scale
Have
1 status page with 25 services on Starter ($24/mo); 10 status pages with 50 services on Team ($64/mo); none on the free Hobby plan
Status-page subscriber notifications
Have
every tier including Free
Partial
50 status page subscribers on Starter; not offered on the free Hobby plan
Team access
Have
owner, admin and responder roles
Partial
1 user on Hobby; 3 users on Starter ($24/mo); 10 users on Team ($64/mo)
Data retention
Not published
retention window is not published as a marketed tier feature
Partial
7 days on Hobby and Starter; 30 to 180 days on Team and Enterprise, per Checkly's pricing page
Is there a free tier?
RealUptime is free to start and never asks for a card. One signup turns on the free rung of every product: 10 monitors with a public status page, 5 server-agent slots, and 10,000 error events a month kept for 14 days. RealUptime Outages is free to read with no account at all.
Checkly: the Hobby plan: 10 uptime monitors, 1,000 browser check runs and 10,000 API check runs a month, 6 locations and 1 user, at $0/mo.
Is it open source or self-hosted?
RealUptime's core is a hosted service and its source is not published, so there is no self-hosted edition of the platform itself. The parts that run on your side are open source at github.com/RealUptimeHQ: the CLI and the RealUptime Errors SDKs for JavaScript, Python, Go, PHP and Ruby are MIT-licensed, and the Grafana data source is Apache 2.0.
Checkly: a hosted product that publishes no source and no self-hosted edition.
If self-hosting is a hard requirement, these are the open-source options in this category: Uptime Kuma (MIT), OpenStatus (AGPL-3.0), Healthchecks.io (BSD 3-Clause) and OneUptime (Apache 2.0).
Looking for a Checkly alternative?
For the reasoning behind checking from more than one region at all, see why a status page can show all green during a real outage. Comparing more than just this one alternative? The status page tool checklist covers what to test before committing to any of them.