comparing self-hosted
Uptime Kuma vs Kener: monitoring first, or the status page first?
Both tools are self-hosted, both are MIT licensed, and both show a status page. But they do not agree on which part matters most. Kuma is a monitoring dashboard for you, and it can also publish a page. Kener is a page for your users, and it can also run checks. So ask yourself first: who will look at it?
the facts, side by side
| Uptime Kuma | Kener | Uptimepage | |
|---|---|---|---|
| license | MIT | MIT | AGPL-3.0 |
| built for | a monitoring dashboard | the status page first | monitoring + status page |
| configuration | UI only | UI + REST API | UI + Terraform + REST + MCP |
| deploy footprint | one container (Node) | app + Redis | 1 binary + 2 DBs |
| check types | 31 incl. DBs · MQTT · browser | 8 incl. SQL · heartbeat · GameDig | HTTP · TCP · DNS · TLS · ping · domain |
| alert channels | 94 services | email · webhook · Slack · Discord | Slack · Telegram · PagerDuty · SMS + more |
| page branding | yes, custom domains | logo · colors · CSS · themes · i18n | branded, own subdomain |
| pages per instance | many | many | many |
| REST API for monitors | none official | yes | yes |
| teams & roles | single login | role-based collaboration | orgs + roles |
| community (GitHub stars) | ~89k | ~5.1k | young |
Kener's check and alert lists come from its README. Its check interval and page subscriptions are not documented, so no row claims either.
Star counts rounded from GitHub, July 2026.
Verified July 2026 against both repositories. Refresh when a project releases a new version.
The main difference
Uptime Kuma puts monitoring first. The dashboard is the main product, and it is where you spend your time. The status page is an extra that it can also produce. Kener starts from the other side, and it says so clearly: it is a status page system built with SvelteKit and Node. Its goal is a good-looking page that takes little effort to set up, with monitoring added to keep the page correct. Neither tool is worse than the other. They answer different questions.
What Kener does better
The page itself, and the people who work on it. You can brand the page with your logo, colors, custom CSS and themes. It has light and dark mode, translations, and times shown in the reader's timezone. You can embed status widgets and badges in other sites. One install can run several status pages. It has roles for team members, API keys, and a full REST API for incidents, monitors and reports. It also has maintenance windows and incident timelines with acknowledgements. And it connects to analytics tools you may already use, including Plausible, Umami, GA, Mixpanel and Clarity.
What Uptime Kuma does better
The checks, by a long way. Kuma supports 31 monitor types, including databases, MQTT, SNMP and a real Chromium browser check. Kener supports eight: API, ping, TCP, DNS, SSL, SQL, heartbeat and GameDig. Kuma sends alerts to 94 services. Kener sends email, webhook, Slack and Discord. Kuma 2.x checks every second, and its community is much larger. If the checks matter more to you than the page, choose Kuma.
The limits of both
Kener's official compose setup runs Redis next to the app, so you run two parts, not one. Its check list is short, so an unusual protocol may be missing. Uptime Kuma's limits come from how it is built. It has one shared login and no user roles. It has no official REST API to manage monitors, and no Terraform provider. Its status pages take no subscribers, and it checks from the server where you installed it, unless you add its Globalping monitor type.
Where Uptimepage fits
Kener already handles branding well, so Uptimepage's advantages here are narrow. Uptimepage is one binary, with no second service to run. Its probes check from several regions, not one. You can declare monitors with a Terraform provider, a REST API and an MCP server. Its status pages take email and webhook subscribers once they confirm. And incidents open on their own when checks fail, so nobody has to write them by hand. Host it free with no card, or self-host it under AGPL.