StatOSS compared with Uptime Kuma
Uptime Kuma is the self-hosted monitor with ninety thousand stars and thirty monitor types. StatOSS is open source at the core too, and also runs as a hosted service with checks from four regions and nothing to keep up.
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
Side by side
| StatOSS | Uptime Kuma | |
|---|---|---|
| Price | 1 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 limits | Free, MIT licensed, sponsorship welcome |
| Hosted version | Yes, statoss.com, with accounts, billing and a dashboard | No official one; you run the Docker image on your own box, or pay a host such as PikaPods to run it |
| Where checks run | Aarhus 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 region | The one node it is installed on, plus a Globalping monitor type that sends a check through Globalping's public probes; if that box is down, the checks and the status page are down with it |
| Monitor types | HTTP with keyword, TCP, DNS, ping, certificate, domain expiry, heartbeat, component | HTTP, keyword, JSON query, gRPC, TCP, ping, DNS, Docker, push, databases, MQTT, Kafka, SNMP, game servers, a real browser, and more |
| Status page | Response-time bars with a mark for every failed check, failures with time and reason, incidents, maintenance, error budget, subscribers on Pro | Heartbeat bars and a 24-hour uptime figure per monitor, groups, pinned incidents, maintenance, RSS; no email subscribers |
| Accounts | Many accounts, each with its own pages and API keys; Pro includes 3 people, $5 a month for each one after | One admin account; multi-user has been an open request since 2021 |
| Operator alerts | Email on every plan; Slack, Discord, Microsoft Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy and a signed webhook on Hobby and Pro. No SMS | More than 90 providers, Apprise included |
| Backups, TLS, upgrades | Ours on the hosted service; yours on the standalone core | Yours |
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.
Hosting it yourself, either way
Both are open source, so the question is not whether you can self-host but whether you want to. The StatOSS standalone is one container configured with a YAML file: the same checks and the same page as the hosted service, unlimited pages and monitors, alerts through your own SMTP server. Uptime Kuma is one container with a web UI and SQLite or MariaDB behind it. Either way the box, the domain, the certificate, the backups and the upgrades are yours, and the status page goes down with the box. The hosted StatOSS is for when you do not want to run the box.
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 Uptime Kuma is the better pick
If you monitor things inside your own network, a database, a Docker container, an MQTT broker, Uptime Kuma runs next to them and has a type for each. If you want a hundred monitors for nothing and are happy to run a box, that is what it is for. If your alerts go somewhere exotic, one of its ninety providers is probably it. And it has been developed in the open since 2021.
Where StatOSS fits: a public page that must stay up when your infrastructure does not, failures checked again from every region, a page that shows the failed checks rather than a heartbeat bar, email subscribers, several people with their own logins, and nobody on the hook for the box.