Hosted Uptime Kuma, and StatOSS hosted
Uptime Kuma has no hosted version from its author. You run it on your own server, or pay a host such as PikaPods to run the container, from $3.30 a month. StatOSS is open source too, and its hosted service runs the same code.
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 on PikaPods | |
|---|---|---|
| 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 | From $3.30 a month for the pod, more with more CPU, memory or storage; $5 of credit at sign-up; at least $1 a month per pod, even when stopped |
| Updates | Ours | PikaPods applies stable releases after testing, usually within a week; security fixes within hours |
| Backups | Ours | Yours: PikaPods runs nightly encrypted backups into S3 storage you supply |
| 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 pod, in the EU region (Hetzner in Falkenstein and Finland) or the US region (Boston and Atlanta); if the pod is down, the checks and the page are down with it |
| Email alerts | Sent by StatOSS | Through an SMTP provider you bring; PikaPods sends no email |
| Your own domain | On Pro, certificate handled | One per pod, certificate handled |
| 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 |
| Support | StatOSS support for the whole product | PikaPods supports the hosting; questions about Uptime Kuma go to its community |
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.
Who does the upkeep
On your own VPS you pay for the server and do the rest: Docker or Node, a reverse proxy, the certificate, updates, backups, an SMTP account for email alerts, and something that tells you when the box itself is down. On PikaPods the container, the certificate and the updates are theirs; the backups, the SMTP account and the Uptime Kuma settings are yours. Either way the checks run from one place and the status page goes down with the box.
The hosted StatOSS runs the checks from Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia, checks every failure again from every region, sends the email itself, and keeps the backups. The standalone runs the same core on your own 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 hosted Uptime Kuma is the better pick
If you want Uptime Kuma itself, with its thirty monitor types and ninety notification providers, PikaPods runs it from $3.30 a month and the sign-up credit covers the first month; StatOSS Hobby is $4 a month for 10 monitors. If you monitor things inside a private network, Uptime Kuma on a server inside that network reaches them, and StatOSS refuses private addresses.
Where StatOSS fits: checks from more than one place, email sent for you, subscribers, several people with their own logins, and nothing to back up or upgrade. Any CSV with a URL column imports; the import page has the steps.