KumaAlert - Big upgrades and roadmap feedback wanted!
Hey everyone 👋
Something has been running under KumaAlert since August that I haven't properly announced yet: Core v2, a ground-up rebuild of how the iOS app talks to your Uptime Kuma servers. It shipped quietly so it could prove itself on real fleets before I made noise about it. Several releases later, it's now the only engine, and 4.5.0 builds on it.
So here's the full story: what Core v2 is, what's new in 4.5.0, and where things go next.
Website: Click Here!
⚡ Introducing Core v2
The original app was built around one connection streaming live into the screen. It worked, but it was fragile with several servers, slow to open, and it worked out your outage history from whatever it happened to see while open.
Core v2 replaces all of that:
- Opens instantly onto your last known state. Every monitor is kept on the device, so you never stare at a blank screen while it connects.
- Each server gets its own independent connection. One slow, down or unreachable server no longer holds up the rest.
- Recovers by itself. Dropped connections reconnect without a Retry tap, half-open sockets after a network change are caught and rebuilt, and two-factor servers stop asking for a code on every launch.
- Incidents are tracked on our servers, not pieced together on your phone. Your outage history is identical on every device, survives a reinstall, and no longer depends on the app being open when something breaks. Duplicate, split and phantom "still down" incidents are gone.
- Smoother with big fleets. Heartbeat bursts no longer redraw the Monitors tab several times a second, and cold start does a fraction of the work.
- Lighter on battery and data. It syncs when something actually changes, not on every heartbeat.
- Every screen runs on it: Overview, Monitors, Manage, Incidents, widgets, Apple Watch, Live Activities and Kiosk mode on iPad.
🔔 New in 4.5.0: your alerts follow you
Swapped phones? Uptime Kuma knows and will prompt you to fix...
Now it can:
- Overview warns you if Uptime Kuma is sending a server's alerts to another device, such as your previous phone. One tap points them back at the phone you're holding.
- If you're signed in, KumaAlert moves each server's webhook to your account, so alerts keep arriving after a phone swap or a reinstall with nothing for you to do.
- iOS: rotating a server's webhook secret updates Uptime Kuma again, instead of leaving that server's alerts paused.
🧰 In recent updates...
- Sync between iPhone and Android. Pair the two with a short code. It's end-to-end encrypted, so we can't read your servers.
- Acknowledge, add notes and resolve incidents on one device, and every other device picks it up.
- Stale outages are clearly marked instead of a downtime counter that never stops.
- Recovery alerts no longer report silly downtimes like "1628 hours" for a five-minute blip.
- Connects through more proxies and tunnels, and you can long-press maintenance schedules for quick actions.
- Polish: new accent colours, Overview banner styles, TLS expiry on HTTPS monitors, and widget fixes.
Full changelog: kumaalert.app/changelog
🗺️ Roadmap
With Core v2 in place, the foundations are ready for the bigger features:
- 📅 On-call scheduling. Set who's on call and when, with rotations and handovers. Alerts go to whoever is on duty instead of everyone at once.
- 👥 Teams. Share servers and monitors with other people, each with their own devices and alert preferences, and acknowledgements that everyone can see.
💬 What should come next?
What would make KumaAlert more useful for your setup? Feature ideas, rough edges, things that annoy you every day, how you'd want on-call or teams to work: all of it shapes what gets built first.
Drop a comment, or come say hi on Discord. And thank you to everyone who has sent bug reports and diagnostic codes. A lot of Core v2's polish, and all of 4.5.0, came straight from those. 🙏
Bobby
