Hosted vs self-hosted

The status page shouldn't be the thing that goes down.

Open-source tools like Uptime Kuma and Cachet are great — until you remember the status page has to survive the outage it's reporting. If it runs on the same infrastructure as your app, it goes dark exactly when users need it. And someone still has to patch it, renew its certificate, and keep it up.

A hosted status page sits off your infrastructure, so it stays up when you don't. UptimeClaw's updates automatically from your monitors — the page reflects reality without anyone touching it during an incident.

What you get

Everything a status page needs, nothing to maintain.

Automatic

Updates from your monitors

The page reflects monitor state in real time, with automatic incident creation and resolution — no manual posting during a fire.

History

90-day uptime & custom domain

Daily uptime bars over 90 days, on your own domain (status.yourdomain.com), so it looks like part of your product.

Control

Public, private, embeddable

Make it public, password-protect it, or embed a status badge in your docs and app.

Status page FAQ

Is the status page really free?

Yes — the free plan includes a status page alongside 5 monitors. Paid plans add more pages, custom domains, and private/password options.

How is this different from Uptime Kuma?

Uptime Kuma is self-hosted — you run and maintain the server, and it can go down with your infrastructure. UptimeClaw's status page is hosted off your stack and updates automatically, with nothing to patch.

Can I use my own domain?

Yes — point status.yourdomain.com at your UptimeClaw status page so it stays on-brand.

Do I have to update it manually during an outage?

No. Incidents are created and resolved automatically from monitor state — though you can post custom updates if you want to add context.

Give users a page
instead of a guess.

Free hosted status page, auto-updated from your monitors. No server to run.

Related

All monitoring features · Alert integrations · WhatsApp alerts