StatOSS

StatOSS compared with Gatus

Gatus is a health dashboard in one Go binary, configured in YAML, under Apache 2.0, with a hosted service at gatus.io from $10 a month. StatOSS is a status page with the checks built in, under MIT, hosted from free.

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

StatOSSGatus
Price1 page, 1 monitor, checks every 5 minutes, 7 days of history, email alerts; Hobby $4 a month: 10 monitors, every minute, 90 days. Pro $15: 100 monitors across 10 pages, a year, your own domain. The standalone core is free with no limitsFree to run yourself. Hosted at gatus.io: Standard $10 a month or $108 a year, 1 status page, 30 endpoints checked every 2 minutes; Premium $20, 2 pages, 50 endpoints every minute
ConfigurationA dashboard and an API on the hosted service; a YAML file on the standaloneA YAML file
Where checks runAarhus 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 regionThe one instance it runs on; remote instances are experimental
Monitor typesHTTP with keyword, TCP, DNS, ping, certificate, domain expiry, heartbeat, componentHTTP, TCP, UDP, ping, DNS, SSH, STARTTLS, TLS, WebSocket, gRPC, domain expiry and pushed external endpoints, with conditions on status, body, response time and certificate expiry
Status pageResponse-time bars with a mark for every failed check, failures with time and reason, incidents, maintenance, error budget, subscribers on ProResults per endpoint, uptime and response-time badges, announcements, maintenance windows; no subscribers
Operator alertsEmail on every plan; Slack, Discord, Microsoft Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy and a signed webhook on Hobby and Pro. No SMSMore than 40 providers, SMS through Twilio, Vonage and others among them
StorageOne SQLite fileMemory, SQLite or PostgreSQL
LicenceMITApache 2.0

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

If your monitors live in Git next to the services they watch, Gatus reads them from one YAML file and needs nothing else. If you need SSH, WebSocket or UDP checks, conditions on JSON fields, or SMS through your own Twilio account, Gatus has them. It runs as one small binary inside the network it watches, so it reaches internal services.

Where StatOSS fits: a hosted page that stays up when your network does not, failures checked again from every region, email and webhook subscribers, incidents and post-mortems written on the page, and a free plan. The standalone is one container configured with a YAML file too.