Support

Uptime Kuma is a free, open-source, self-hosted monitoring tool. You can monitor HTTP, TCP, DNS, and other services. KumaAlert connects to your Uptime Kuma instance to show monitor status on your iPhone, iPad, and Android device. Learn more at github.com/louislam/uptime-kuma

Not at this time. KumaAlert is £3.99 on the UK App Store (the local equivalent on other storefronts) — paid once, with no subscription, no in-app purchases, no recurring fees, and everything unlocked forever, including future features. Most apps of this kind lock features behind monthly plans, but that felt at odds with the self-hosted spirit of Uptime Kuma. That said, running the push notification infrastructure and maintaining an Apple Developer account does have a real cost, which is why there's a small one-time charge rather than a free tier. See how that compares to the other Uptime Kuma apps.

Check that: your Uptime Kuma server URL is correct, your phone can actually reach that address from where it is right now, your username and password are correct, and your server is running Uptime Kuma v1.23.0 or later. That middle one catches most cases — a 192.168.x.x address works at home but not on mobile data. Either expose the server on a public hostname, or reach it over a VPN or Tailscale (KumaAlert can talk to LAN and Tailscale addresses over plain HTTP as well as HTTPS). Note this affects the live dashboard and the widget only — push alerts arrive either way, see below.

You add a notification provider in your Uptime Kuma dashboard pointing at KumaAlert's push relay. When a monitor changes state, your server sends an outbound webhook to the relay, and the relay forwards it to your device through Apple's Push Notification service or Firebase. The important consequence: the relay only ever receives from your server, it never connects back to it, and it does not store your server's address. Your server does not need to be reachable from the internet for alerts to work — it only needs to be able to make outbound HTTPS requests. See the Setup Guide for the exact steps.

No. There is nothing extra to self-host and nothing to maintain. KumaAlert talks to your existing Uptime Kuma instance directly, and alerts go through our hosted relay, which you do not run or configure beyond pasting a webhook URL into Uptime Kuma.

It shouldn't. Alerts are true push notifications — the app is not running in the background polling your server, it is woken by the system only when an alert actually arrives. The live dashboard holds a connection only while the app is open on screen. The one piece of recurring background work is the widget refresh, which uses your API key and is scheduled by the operating system, not by us; iOS and Android decide how often it runs and will back it off if you rarely open the app. If you don't add an API key, there is no background refresh at all.

Yes! KumaAlert supports connecting to multiple Uptime Kuma instances. Add additional servers from the Manage tab in the app.

The API key lets KumaAlert check your monitors' status in the background, while the app isn't open. This is what keeps the Home Screen widget up to date. Without a key, the widget only refreshes when you open the app. Generate an API key in your Uptime Kuma dashboard under Settings > API Keys, then add it in the app under Settings > your server > API Key.

The widget refreshes in the background using an API key. If you haven't added one, it can only update when you open the app. Add a key under Settings > your server > API Key (generate it in Uptime Kuma under Settings > API Keys). Note that the operating system decides exactly when background refreshes run, so updates are periodic rather than instant.

Yes. All credentials are stored in your device's secure keystore (iOS Keychain / Android Keystore), and monitor data stays on your device. See our Privacy Policy for full details.