StatusCake vs Uptime Kuma

StatusCake Uptime plus SSL, domain, and DNS checks — a checker that takes the boring failures seriously. Uptime Kuma The open-source Docker monitor you run yourself. Free, flexible, and yours to keep online. StatusCake is hosted. Uptime Kuma is self-hosted. That is the first fork — who owns the checker when your own network is the thing on fire. If you only needed a public status page and a health check, neither may be the smallest tool — GreenCrew is built for that job.

Side by side

Topic	StatusCake	Uptime Kuma
Best for	Teams that want HTTP together with certificate and domain expiry, without an observability suite.	People who already self-host, want many monitor types, and accept that the checker is another box they own.
Not for	Browser-level journeys, log pipelines, or a tool you run on your own VPS.	Founders who did not want another container, or who need a status URL that stays up when their VPS does not.
Hosting	Hosted	Self-hosted
What it checks	HTTP, SSL, domain, DNS, and related tests. They write about Namecheap-class DNS incidents because they watch that layer.	HTTP, keyword, TCP, DNS, Docker, push/heartbeats, and more — depending on how you configure it.
Status page	Contact groups and public reporting; status pages are part of the uptime product.	You can expose a status page from the same instance. It lives where you deployed it.
Alerts	Email, SMS, Slack, and the usual webhook list.	Huge list of notification backends if you configure them.
Complexity	Simple	Simple software, operationally yours.
Pricing shape	Freemium uptime plans. SSL and domain tests sit beside HTTP, not behind APM.	Free software. You pay the VPS, the backups, and the time.

What StatusCake is

Uptime plus SSL, domain, and DNS checks — a checker that takes the boring failures seriously. Teams that want HTTP together with certificate and domain expiry, without an observability suite. Browser-level journeys, log pipelines, or a tool you run on your own VPS.

What Uptime Kuma is

The open-source Docker monitor you run yourself. Free, flexible, and yours to keep online. People who already self-host, want many monitor types, and accept that the checker is another box they own. Founders who did not want another container, or who need a status URL that stays up when their VPS does not.

The actual split

StatusCake is hosted. Uptime Kuma is self-hosted. That is the first fork — who owns the checker when your own network is the thing on fire.

Who should pick which

StatusCake: Teams that want HTTP together with certificate and domain expiry, without an observability suite.
Uptime Kuma: People who already self-host, want many monitor types, and accept that the checker is another box they own.