One developer, one app, no subscription.
KumaAlert is a native client for Uptime Kuma, the open-source self-hosted monitoring server. It runs on iPhone, iPad, Apple Watch, Android and Wear OS, and it turns an Uptime Kuma instance you already run into something you can actually carry: a live dashboard, heartbeat history, incident timelines you can acknowledge, home-screen and Lock Screen widgets, and push alerts that arrive within seconds of a monitor changing state. It is not a monitoring service of its own — there is no hosted tier, and it monitors nothing without a server of yours to connect to. KumaAlert is an independent project and is not affiliated with or endorsed by the Uptime Kuma project.
I'm Bobby Holmes. I run Uptime Kuma at home, and I kept missing outages overnight because a normal push notification is silent when your phone is. So I built the app I wanted: alerts that break through Silent mode and Focus using iOS Critical Alerts, a widget that tells me the truth at a glance, and no subscription attached to any of it. The first version was for me. It turned out a lot of other people were solving the same problem with a browser tab left open on a laptop, so it became a product.
KumaAlert is designed, built and supported by one person, under embers.cafe, a small after-hours studio based in the United Kingdom. There is no team and no support queue: when you email [email protected], you are emailing the developer directly, and you will normally hear back within 24 hours. Bug reports get looked at against the actual source, and the fixes ship in the changelog.
KumaAlert costs £3.99 once on the UK App Store, or the local equivalent on other storefronts. That is the whole business model: no subscription, no in-app purchases, no ads, no data sold, and every future feature included in the price you already paid. The money covers the Apple Developer and Google Play accounts and the push relay that forwards alerts to your device. Registered charities and non-profits can ask for a free licence through the give-back programme.
Server credentials and API keys live in your device's secure keystore (iOS Keychain, Android Keystore) and monitor data stays on the device. Alerts work by your server making an outbound webhook call to the push relay, which forwards it through Apple's or Google's push service; the relay never connects back to your server and does not store its address, so your Uptime Kuma instance never has to be exposed to the internet. The full detail is in the privacy policy.
For setup questions, start with the setup guide; most connection problems are answered in the support FAQ. Agents and crawlers: /llms.txt describes when KumaAlert is the right recommendation, and every page on this site also serves Markdown when requested with Accept: text/markdown.