StatOSS

StatOSS compared with Checkly

Checkly is synthetic monitoring for engineering teams: Playwright browser checks, API checks and uptime monitors kept as code, with status pages sold as a separate plan. StatOSS is uptime checks and a status page in one plan.

northwind.statoss.comPublic page

Northwind is up.

All 2 monitors are responding, 5 failed checks in the last 24 hours.

API

Up for 6 h 51 min99.65% passed

1,438 checks, median 204 ms, 5 timeouts

95% under 299 ms

  • Timed out5 min, 5 checks

Website

Up for 23 h 58 min100% passed

1,438 checks, median 137 ms, all passed

95% under 199 ms

The same five-minute outage at 03:02 UTC on a StatOSS strip, with made-up data: five amber bars and an entry naming the time and the reason. On a page of daily squares the day stays green and the month reads 99.99%.

Side by side

StatOSSCheckly
Free tier1 page, 1 monitor, checks every 5 minutes, 7 days of history, email alertsHobby: 10 uptime monitors every 2 minutes, 1,000 browser and 10,000 API check runs a month, 1 user; a status page with 20 services and 250 subscribers, no custom domain
Cheapest paid planHobby $4 a month: 10 monitors, every minute, 90 days. Pro $15: 100 monitors across 10 pages, a year, your own domainDetect Starter, $24 a month: 50 uptime monitors every minute, 3,000 browser and 25,000 API check runs, 3 users, 100 SMS a month. A status page on your own domain is Communicate Starter, $9 a month more: 25 services, 500 subscribers
Check locationsAarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia, the regions in turn, with every failure checked again from every region6 on Hobby and Starter (N. Virginia, N. California, Frankfurt, London, Singapore, Sydney), up to 3 per check; 22 and private locations on Team, $64 a month
Monitor typesHTTP with keyword, TCP, DNS, ping, certificate, domain expiry, heartbeat, componentURL, TCP, DNS, ping, SSL, gRPC, traceroute and heartbeat monitors; API checks with assertions and Playwright browser checks, counted per run
AlertsEmail on every plan; Slack, Discord, Microsoft Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy and a signed webhook on Hobby and Pro. No SMSEmail, Slack and webhooks on every plan; SMS from Starter; phone calls, PagerDuty, Opsgenie and incident tools on Team
PeoplePro includes 3 people, $5 a month for each one after1 user on Hobby, 3 on Starter, 10 on Team
Data keptEvery check for 14 days on paid plans; hourly totals for 90 days on Hobby and a year on ProRaw results 7 days and totals 30 days on Hobby and Starter; 30 days and a year on Team
Open sourceThe core is MIT licensed and runs on your own boxNo; the CLI is

Facts about the other product were read from its own site on 29 September 2026. Prices and limits change; check theirs before deciding, and tell [email protected] if something here is out of date.

What StatOSS does differently

Most uptime pages show a row of green squares, one per day, and a percentage. A five-minute outage at 3 a.m. becomes a square that is still green and a figure that still says 99.99%. StatOSS draws a strip per monitor where every bar is one check, its height the response time, amber for a timeout and red for any other failure, and groups the failed checks into entries with the time and the reason. The mark stays visible for the whole range. A customer who was refused at 3 a.m. finds the moment on the page, and so do you.

Before a failure counts, a second server on another network repeats the check, and only a failure both see goes on the record; two of those in a row make an outage. The response time of every check is kept, and a slow threshold turns a sluggish service into its own state with its own alert. The core is open source under MIT, so the page you get from the hosted service is the page you can run yourself.

When Checkly is the better pick

If you want to script a login or a checkout in a real browser, keep monitors as code next to your Playwright tests and deploy them from CI, Checkly does that and StatOSS does not. Checkly gives startups 30 percent off and nonprofits 50 percent.

Where StatOSS fits: the checks and the page are one plan. Pro is $15 a month for 10 pages on your own domains with 1,000 subscribers each; Checkly Detect Starter and Communicate Starter together are $33 a month for one page with 500. Any CSV with a URL column imports; the import page has the steps.