Uptime Kuma

Know it's down before your customers tell you

Uptime monitoring should be trivially cheap, yet SaaS providers meter it by the monitor: every extra endpoint, every shorter check interval, every status page nudges the subscription up a tier. Uptime Kuma is the open source alternative: a self-hosted monitoring tool with unlimited monitors, instant alerts to the channels you already use, and built-in status pages. Node deploys and manages it as a production service hosted in the UK, at a flat price however much you watch.

What Uptime Kuma is

Uptime Kuma is an open source uptime monitoring tool with a clean, modern interface that has made it one of the most popular self-hosted projects in the world. It repeatedly checks the things your business depends on, websites, APIs, TCP services, DNS records and hosts, and alerts you the moment something stops responding.

Checks go beyond a simple ping. HTTP monitors can assert status codes, keywords and JSON responses, so you know the page is not just up but correct. Push monitors invert the model for scheduled jobs and backups: the job checks in, and if it goes quiet, you hear about it. Certificate monitoring warns you before a TLS certificate expires, which is a category of outage nobody should still be having.

When something breaks, Uptime Kuma notifies you through the channels your team already watches, with support for dozens of services including Slack, Microsoft Teams, email, Telegram and generic webhooks. And its built-in status pages let you publish live service status on your own domain, branded as yours.

Why self-hosted Uptime Kuma instead of Pingdom, UptimeRobot or StatusCake

No per-monitor pricing: SaaS uptime services charge by monitor count and check frequency, and at the time of writing meaningful coverage on Pingdom, UptimeRobot or StatusCake climbs quickly past the entry price. Uptime Kuma has no monitor limit: watch every endpoint, internal and external, at the interval you actually want.

Monitor internal services too: a SaaS checker can only see what you expose to the internet. Self-hosted Uptime Kuma can sit inside your network and watch internal APIs, databases, intranet services and scheduled jobs that no external service could ever reach.

Status pages included: hosted status pages are often a separate product with its own subscription. Uptime Kuma includes them, on your domain, at no extra cost.

UK data residency and independence: your monitoring configuration and uptime history stay on UK infrastructure under an Article 28 data processing agreement, and your ability to see whether you are up does not depend on a third-party SaaS being up.

No lock-in: monitor definitions and history live in your own instance, exportable and yours, not trapped in a subscription that punishes you for leaving.

Status pages your customers can trust

Public status pages turn incidents from a support flood into a single authoritative message. Uptime Kuma lets you publish one or several status pages, each showing the services you choose with live state and incident notes, hosted on your own domain with your branding. For agencies and MSPs, per-client status pages from one instance are a genuinely useful deliverable that SaaS providers charge handsomely for.

Part of a proper monitoring stack

Uptime Kuma answers the outside-in question: is the service reachable and responding correctly right now. For depth behind that signal, Node also runs Zabbix for full infrastructure monitoring, hosts, services, metrics and thresholds from the inside, and Grafana for dashboards and alerting across every data source you have. Many customers run all three: Uptime Kuma tells you something is wrong, Zabbix and Grafana tell you why.

Keycloak and single sign-on

Every application in a Node tenant joins your organisation's own Keycloak realm on our platform. Your team signs in to Uptime Kuma with the same corporate credentials they use across all their Node-managed applications, MFA and session policies are enforced consistently, and admins control who can change monitors from one central place.

How Node runs Uptime Kuma for you

Deployment: we deploy Uptime Kuma in a production configuration with TLS, your domains for status pages, notification channels wired up, and your first monitors configured with you.

Upgrades and maintenance: we test and apply releases and keep the instance patched and current without gaps in your monitoring history.

Monitoring and support: we monitor the monitor, because an uptime checker that silently dies is worse than none, back up its configuration and history daily, and our UK team is on hand to help with checks, alerts and status pages.

Your infrastructure or ours: hosted on Node's UK infrastructure or deployed into your own environment, on-premises or in your cloud accounts, with the same managed service either way.