StatOSS

StatOSS compared with Better Stack

Better Stack bundles uptime, on-call and logs for engineering teams, priced by add-on and by responder seat. StatOSS is one product with three plans and an open source core; Pro includes 3 people, $5 a month for each one after.

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

StatOSSBetter Stack
Free tier1 page, 1 monitor, checks every 5 minutes, 7 days of history, email alerts10 monitors and 10 heartbeats, checks every 3 minutes, 1 status page, email and Slack alerts
PaidHobby $4 a month: 10 monitors, every minute, 90 days. Pro $15: 100 monitors across 10 pages, a year, your own domainAdd-ons on top of free: 50 more monitors $25 a month, 10 more heartbeats $20, another status page $15, a responder seat (anyone who can be paged) $34, each cheaper billed annually
Check intervalEvery minute on paid plans, every 5 minutes on FreeEvery 3 minutes free, down to 30 seconds paid
Failure confirmationA second server on another network repeats every failed checkAt least 4 locations per monitor; an incident after failures from at least 3
What the status page showsResponse-time bars with a mark for every failed check, each failure with its time and reasonDaily bars over 7 to 365 days, intraday proportions, response-time charts; 1,000 subscribers included
Monitor typesHTTP with keyword, TCP, DNS, ping, certificate, domain expiry, heartbeat, componentHTTP with keyword, TCP and UDP, ping, SSL, domain expiry, DNS, mail protocols, heartbeat, browser transactions (metered)
AlertsEmail on every plan; Slack, Discord, Microsoft Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy and a signed webhook on Hobby and Pro. No SMSEmail, Slack, Teams, push, webhooks, Zapier; phone and SMS with a responder seat
Open sourceThe core is MIT licensed and runs on your own boxNo

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 Better Stack is the better pick

If you want on-call schedules, escalation, phone calls and logs in the same place as the monitors, Better Stack is that place and StatOSS is not; StatOSS hands paging to PagerDuty or Opsgenie. If you need 30-second checks, Better Stack has them. If ten free monitors cover you, Better Stack's free tier holds more than ours.

Where StatOSS fits: a team that wants a status page and alerts for $4 or $15 a month (Pro includes 3 people, $5 a month for each one after), a status page that shows the failed checks rather than daily bars, and a core it could run itself if the hosted service ever went away.

Moving over

The import screen under Monitors reads a Better Stack export. The import page has the steps; monitors come over, history starts fresh.