OpenKuma
Read-only viewer for your Uptime Kuma monitors. Private, no ads, no tracking.
新版本 0.1.4
- Fixed: the app closed itself instantly, with no error, when the server URL had no https:// in front. The scheme is now filled in for you, an unreadable address says so, and a failed sign-in can no longer take the app down.
- Fixed: a server that accepted the connection and then went silent left the Connect button spinning forever. Signing in now gives up after 30 seconds and says what to check.
- Fixed: the dashboard showed "No monitors yet" with 0/0/0 counters while it was still loading, whic
- Fixed: a server that accepted the connection and then went silent left the Connect button spinning forever. Signing in now gives up after 30 seconds and says what to check.
- Fixed: the dashboard showed "No monitors yet" with 0/0/0 counters while it was still loading, whic
OpenKuma is a private, read-only Android client for Uptime Kuma, the self-hosted monitoring tool. Check the health of your services from your phone, without ever changing anything on your instance.
OpenKuma is strictly read-only. It is 100% free and open source, sends no data to anyone, and has no ads, no tracking and no Google services.
Features:
* Connect to your Uptime Kuma servers over the Socket.IO API
* Dashboard with live counts (up, down, pending), active incidents and expiring certificates
* Monitor list with instant search, sorting and local favorites
* Monitor detail: status, 24h uptime, response times, general info, TLS certificate and recent checks
* Certificates screen sorted by soonest expiry, with a visual warning
* Events log of status changes
* Offline cache so the last known state is always available
* Light and dark themes, Material You on Android 12+, English and French
Privacy first: only your session token is kept on the device, encrypted with the Android Keystore. Your password is never written to disk.
OpenKuma is an unofficial client and is not affiliated with or endorsed by Uptime Kuma.
OpenKuma is strictly read-only. It is 100% free and open source, sends no data to anyone, and has no ads, no tracking and no Google services.
Features:
* Connect to your Uptime Kuma servers over the Socket.IO API
* Dashboard with live counts (up, down, pending), active incidents and expiring certificates
* Monitor list with instant search, sorting and local favorites
* Monitor detail: status, 24h uptime, response times, general info, TLS certificate and recent checks
* Certificates screen sorted by soonest expiry, with a visual warning
* Events log of status changes
* Offline cache so the last known state is always available
* Light and dark themes, Material You on Android 12+, English and French
Privacy first: only your session token is kept on the device, encrypted with the Android Keystore. Your password is never written to disk.
OpenKuma is an unofficial client and is not affiliated with or endorsed by Uptime Kuma.
- 作者: emon
- 授權條款: GNU General Public License v3.0 or later
- 問題追蹤系統
- 原始碼
- 建置詮釋資料
- 可重現建置狀態
捐助
版本
雖然在下方可選擇下載 APK 檔案，但要留意這樣的安裝方式將不會收到更新通知，是一種較不安全的下載方法。建議您先安裝 F-Droid 用戶端使用。
下載 F-Droid-
arm64-v8aarmeabi-v7ax86x86_64此版本需要 Android 8.0 或更高的版本。
此套件包由原開發者建置和簽署，並保證與此原始碼 Tarball 保持一致。
-
arm64-v8aarmeabi-v7ax86x86_64此版本需要 Android 8.0 或更高的版本。
此套件包由原開發者建置和簽署，並保證與此原始碼 Tarball 保持一致。
-
arm64-v8aarmeabi-v7ax86x86_64此版本需要 Android 8.0 或更高的版本。
此套件包由原開發者建置和簽署，並保證與此原始碼 Tarball 保持一致。
新版本 0.1.3
- New: optional real-time updates (Settings > Background updates). Notifies the moment a monitor changes state, at the cost of a permanent notification and more battery. The periodic options remain the default and the lighter choice.
- Fixed: the events log was always empty and per-monitor history was missing after connecting — OpenKuma was discarding data Uptime Kuma sends at login.
- Fixed: servers with a private/internal CA needed certificate checks turned off. CAs installed on the device are
- Fixed: the events log was always empty and per-monitor history was missing after connecting — OpenKuma was discarding data Uptime Kuma sends at login.
- Fixed: servers with a private/internal CA needed certificate checks turned off. CAs installed on the device are
新版本 0.1.2
- Fixed: accounts with two-factor authentication (2FA) could not reconnect after
the session expired — the re-login dialog now asks for the 2FA code, stays open
on failure, and shows a clear error.
- Fixed: refreshing could leave the dashboard stuck "connecting" with monitors
never updating; reconnection is now reliable.
the session expired — the re-login dialog now asks for the 2FA code, stays open
on failure, and shows a clear error.
- Fixed: refreshing could leave the dashboard stuck "connecting" with monitors
never updating; reconnection is now reliable.