Uptime Mate

An honest look at what it actually does, what it requires, and whether you need it.

TL;DR

• What it is: An iOS/watchOS companion app that surfaces your Uptime Kuma service status directly on your Apple Watch [1].
• Who it’s for: Self-hosters already running Uptime Kuma who want a glanceable wrist view of their infrastructure — no phone required [1][README].
• Key dependency: Uptime Kuma is a hard requirement. Without it, this app does nothing [README].
• Cost: Free to use for core features. Optional one-time “Pro” in-app purchase unlocks extras like latency charts and monitor grouping [1].
• Key strength: Version 2.0 eliminated the Docker backend that was previously required, making setup dramatically simpler — connect directly to your Uptime Kuma instance via its WebSocket API [1].
• Key weakness: Extremely narrow audience. Only useful if you have an Apple Watch, run Uptime Kuma, and want to check service status from your wrist [README][1]. Three App Store reviews at time of writing says everything about the addressable market.

---

What is Uptime Mate

Uptime Mate is not an uptime monitoring tool. That framing would be wrong. It’s a companion app for Uptime Kuma, the popular self-hosted monitoring dashboard. Uptime Kuma does the actual work — pinging your services, recording uptime history, sending alerts. Uptime Mate surfaces that data on your Apple Watch face [README].

The project started as “Uptime Buddy” in June 2024 and was renamed in October 2024. It’s built by a solo developer, Christoph Scherbeck, who describes himself as an app developer by trade [1][App Store]. The GitHub repository sits at 180 stars, which is small — but this is a niche tool solving a niche problem, and the star count reflects that rather than quality [merged profile].

The original architecture required deploying a separate Docker container as an API bridge between Uptime Kuma and the iOS app. That made the setup story awkward: you were running a monitoring tool to monitor another monitoring tool’s backend. Version 2.0.0 — released as a major update and announced in r/selfhosted in April 2025 — completely rewrote the data layer. The Docker backend is gone. The app now talks directly to Uptime Kuma’s WebSocket API [1].

The developer was transparent about using AI to speed up the WebSocket integration work, adding in the Reddit announcement: “AI was used to speed up things and help me to learn the websocket interface. The app isn’t vibecoded at all. I am aware about everything that’s happening in my app. I’m an app developer for a living and I know what I’m doing.” [1] That’s a reasonable posture — AI-assisted doesn’t mean abandoned.

App Store privacy disclosure: the developer collects no data from this app [App Store]. For an app that connects to your self-hosted infrastructure, that’s the right answer.

---

Why People Choose It

The use case is narrow enough that there isn’t a category of “people choosing Uptime Mate over competitors.” The decision tree looks like this:

1. You run Uptime Kuma for self-hosted monitoring (very common in the homelab/self-hosted community [3][5])
2. You own an Apple Watch
3. You want a watch-face glance at your service status without pulling out your phone

If all three are true, Uptime Mate is the only tool doing this. The r/selfhosted announcement thread [1] shows the reception to the v2.0.0 update was positive precisely because the old Docker backend was a friction point. One consistent complaint in the early version: why does an Apple Watch companion require running another container? The v2 rewrite addressed this directly.

The broader context for why Uptime Kuma users want this: Uptime Kuma itself is widely used in the homelab community [3][5], with a reputation as approachable but not polished enough for professional use. As one self-hoster noted in a WIP discussion, “Uptime Kuma [is] a bit amateur but does the job” [3]. For people in that camp — running it on a Raspberry Pi or home server to keep tabs on a handful of services — having a Watch complication that shows green/red at a glance is genuinely useful. Pulling out your phone and opening a dashboard to check if your Jellyfin is up is more friction than it needs to be.

The UptimeRobot roundup of uptime tools [5] puts the broader monitoring space in context: the average cost of unplanned downtime runs thousands of dollars per minute for businesses. For hobbyists and indie founders self-hosting their own stack, the stakes are lower — but the desire for instant visibility is the same.

---

Features

Core (free):

• Apple Watch app showing service status from Uptime Kuma [README]
• Watch face complications in multiple variants — circular, rectangular dashed, and others [App Store]
• Live list of monitors with up/down status [App Store]
• Error messages displayed for offline monitors [App Store]
• Complications count only active (non-paused) monitors [App Store]
• Last incident timestamp on the rectangular dashed complication [App Store]
• InfoView showing backend host system metrics: CPU temperature, RAM, disk usage [App Store]
• App and backend version comparison to check sync status [App Store]
• QR code scan from Docker logs for setup (legacy backend flow) [App Store]
• 2FA / MFA support for Uptime Kuma instances with 2-factor authentication [App Store][README]

Pro (one-time in-app purchase, price not disclosed in public data):

• Pause and resume monitors directly from the Watch [1]
• Display latency times in the monitor list [1]
• Latency chart per monitor [1]
• Group monitors by tags [1]
• Option to exclude paused monitors from the list [1]

The developer is clear about the Pro tier philosophy: “Those features are purely optional and don’t really limit the functionality of the app. There will never be a paywall. Uptime Mate should stay free to use, without limiting its main purpose.” [1] That’s the right call for this kind of utility app.

What it doesn’t do:

• It does not create monitors. That’s Uptime Kuma’s job.
• It does not send alerts. That’s also Uptime Kuma’s job.
• It does not work without Uptime Kuma running somewhere accessible.
• Android is not supported and there’s no indication it will be [README].

---

Pricing: The Actual Cost Structure

This isn’t a SaaS vs. self-hosted comparison in the way that applies to most tools in this category. The cost breakdown is:

Uptime Mate app: Free download on the App Store, optional one-time Pro purchase (price not published in available data) [1][App Store].

What you need to already have running:

• Uptime Kuma instance (free, open source, self-hosted)
• A server or Raspberry Pi to run Uptime Kuma on — $5–15/month on a VPS, or effectively $0 if you’re running it on existing home hardware
• An iPhone (iOS 16.0 or newer) and Apple Watch (watchOS 10.0 or newer) [App Store]

Comparison to SaaS monitoring with mobile apps:

• UptimeRobot: free tier with 50 monitors, paid plans from ~$7/month. Has a mobile app [5].
• Better Stack: free tier with 10 monitors, paid from $20/month [5].
• Datadog: enterprise pricing, has a mobile app [5].

None of those have Apple Watch complications as a first-class feature. If Watch visibility is the goal, Uptime Mate solves a gap that paid SaaS tools haven’t prioritized.

The honest cost framing: if you’re already running Uptime Kuma, adding Uptime Mate costs you zero ongoing dollars. The Pro tier is cosmetically “extra,” and based on the feature list, the free tier covers the primary use case.

---

Deployment Reality Check

Pre-v2.0.0 (legacy): Required running a Docker container (schech1/uptime-buddy-api) alongside your Uptime Kuma instance. The compose file needed your Uptime Kuma URL, credentials, a generated token from the iOS app, and optional MFA flag. This added operational overhead that users complained about [1][README].

v2.0.0 and later (current): The Docker backend is gone. Setup is now:

1. Install the app from the App Store
2. Open the iOS companion app — it generates a token on first launch
3. Enter your Uptime Kuma address (the URL of your self-hosted instance)
4. Test the connection
5. Send settings to the Apple Watch [README]

That’s a meaningful improvement. You still need Uptime Kuma reachable from your phone and watch — which means either your Uptime Kuma is exposed to the internet (via reverse proxy with HTTPS) or you’re on the same local network. For remote monitoring, you’ll want a proper domain and SSL cert on your Uptime Kuma instance. That’s standard homelab territory, not specific to Uptime Mate.

Known issue in v2.0.0 at launch: 2FA was not supported in the initial 2.0.0 release. The developer acknowledged this and committed to adding it in 2.1.0, which they were testing at the time of the announcement [1]. Given the track record of shipping (14 version updates from June 2024 to December 2024 before the v2 rewrite), this seems like a real commitment rather than a vague “coming soon.”

Requirements:

• iPhone with iOS 16.0+
• Apple Watch with watchOS 10.0+
• Uptime Kuma instance (any reasonably recent version, including v2)
• Network access from your phone/watch to the Uptime Kuma URL

Not required (as of v2.0):

• The Docker companion container
• Any separate backend API layer

---

Pros and Cons

Pros

• Watch-native monitoring glance. No other open-source or self-hosted tool provides Apple Watch complications for Uptime Kuma status. This fills a genuine gap [1][README].
• v2.0 removed the biggest friction point. Eliminating the Docker backend dependency was the right call and the community asked for it explicitly [1].
• Actively maintained by a developer who knows what they’re doing. 14 updates in the first 6 months, a complete architectural rewrite when needed, and transparent communication about limitations [App Store][1].
• Honest free tier. The Pro features are genuinely additive (latency charts, tag grouping) rather than crippling the core experience behind a paywall [1].
• Zero data collection. Apple’s privacy disclosure confirms the app collects nothing [App Store].
• MIT licensed. The backend code (now largely deprecated by v2) was MIT, and the GitHub repo remains public for issue tracking [merged profile].
• ARM64 + AMD64 Docker support (relevant for Raspberry Pi users running legacy setup) [README].

Cons

• Entirely dependent on Uptime Kuma. If Uptime Kuma goes down or changes its WebSocket API, Uptime Mate stops working. You’re one upstream breaking change away from a broken app [README][1].
• Tiny community. 180 GitHub stars and 3 App Store reviews means limited community support, few public troubleshooting resources, and a single point of failure in the developer [merged profile][App Store].
• Apple Watch only. No Android, no WearOS, no Garmin. If your team uses mixed hardware this helps exactly one person [README].
• 2FA gap in v2.0.0. If your Uptime Kuma uses 2FA, v2.0.0 doesn’t support it yet. Planned for 2.1.0 but not shipped as of the writing of the Reddit announcement [1].
• Not a monitoring tool. This catches people who find it searching for uptime monitoring. If you don’t already run Uptime Kuma, this app is useless to you.
• Small team risk. One developer. No funding disclosures, no company behind it. If Christoph stops maintaining it, the app stops getting updates. The MIT license means someone could fork it, but that’s cold comfort if the iOS app breaks with a future watchOS update.
• Website is the App Store page. There’s no marketing site, no documentation portal, no community forum. Everything is GitHub issues and the README [README].

---

Who Should Use This / Who Shouldn’t

Use Uptime Mate if:

• You already run Uptime Kuma and you own an Apple Watch.
• You want a glanceable, wrist-level status check without opening your phone.
• You’re a homelab person who has a few services running (Plex, Jellyfin, Nextcloud, etc.) and wants to see “everything green” at a glance while going about your day.
• You’re comfortable pointing the app at your self-hosted Uptime Kuma URL and doing the one-time setup.

Skip it if:

• You don’t run Uptime Kuma. The app requires it with no alternative data sources.
• You use Android or don’t own an Apple Watch. There is no other platform version.
• You’re looking for an uptime monitoring solution, not a monitoring viewer.
• You need enterprise-grade reliability from a vendor with an SLA. This is a hobby project.
• Your Uptime Kuma requires 2FA and you need this immediately — wait for 2.1.0.

Consider pairing it with:

• UptimeRobot or Better Stack for external monitoring (checks from outside your network) — Uptime Kuma is self-hosted, meaning it can’t detect if your whole home network or VPS goes dark [5].

---

Alternatives Worth Considering

There are no direct Apple Watch competitors for Uptime Kuma specifically. In the broader space:

• Uptime Kuma itself — the prerequisite. Has a web dashboard and PWA-style mobile access, but no native Watch app [3][5].
• UptimeRobot — SaaS, has a mobile app (iOS and Android), 50 monitors free, no self-hosted option, no Watch complications [5].
• Better Stack (formerly Uptime Better Stack) — more polished SaaS option with a mobile app, paid at meaningful scale [5].
• Checkmate — open-source self-hosted monitoring tool (3,300+ GitHub stars) with a broader feature set than Uptime Kuma. No Apple Watch app [2]. If you’re choosing a monitoring backend from scratch, worth evaluating alongside Uptime Kuma.
• Healthchecks.io — self-hostable, focused on cron job monitoring rather than service uptime. No Watch app.

If Watch integration specifically matters and you’re on Android: there is no equivalent open-source solution — the entire category gap on Android remains unfilled.

---

Bottom Line

Uptime Mate is exactly what it says it is: an Apple Watch face for your Uptime Kuma instance. It doesn’t overpromise. The v2.0.0 rewrite removed the most legitimate criticism (the required Docker backend), leaving a lightweight, zero-cost, well-maintained utility for a very specific audience. If you fit that audience — self-hosting Uptime Kuma, owning an Apple Watch, wanting wrist-level status visibility — there’s nothing to evaluate. You install it, point it at your Uptime Kuma URL, and it works. If you don’t already run Uptime Kuma, this review ends at step zero.

The risks are real but proportionate to the stakes: solo developer, 180 stars, three App Store reviews, no commercial backing. For a free Apple Watch utility checking your home lab, those are acceptable terms. For anything you’d put between yourself and a production outage, you want more than a solo project on a Sunday afternoon.

---

Sources

1. Saltibarciai / r/selfhosted — “Uptime Mate - Uptime Kuma Apple Watch app got a big update” (April 2025). https://www.reddit.com/r/selfhosted/comments/1s9cju2/uptime_mate_uptime_kuma_apple_watch_app_got_a_big/
2. Muhammad Khalilzadeh / DEV Community — “Why You Should Try Checkmate”. https://dev.to/muhammad_khalilzadeh/why-you-should-try-checkmate-41be
3. Kyrylo Silin / WIP.co — “What self-hosted tools do you use?” (discussion thread). https://wip.co/posts/what-self-hosted-tools-do-you-use-k9rm3w
4. Megha Goel / UptimeRobot Knowledge Hub — “11 Best Uptime Monitoring Tools in 2026 (Ranked & Compared)” (Feb 16, 2026). https://uptimerobot.com/knowledge-hub/monitoring/11-best-uptime-monitoring-tools-compared/

Primary sources:

• GitHub repository and README: https://github.com/schech1/uptime-buddy (180 stars, MIT license, Christoph Scherbeck)
• App Store page: https://apps.apple.com/de/app/uptime-mate/id6503297780
• Docker Hub: https://hub.docker.com/r/schech1/uptime-buddy-api