I’m developing URSA, a native Android client for people who run their own Uptime Kuma server. Version 1.3.3 is available from GitHub; F-Droid is currently serving 1.2.3 and does not list the newer release yet.
The F-Droid build has no Google services, Firebase, advertising, analytics, developer-run backend, paid tier, or account requirement. It talks directly to the Kuma server you configure. Credentials, session data, and custom proxy-header values are encrypted at rest using Android Keystore-backed encryption.
Beyond viewing monitor status, URSA supports monitor and maintenance management, multiple servers, 2FA, Pangolin/Cloudflare Access-style custom headers, optional self-signed certificates, UnifiedPush alerts, encrypted offline state, widgets, a Quick Settings tile, app lock, and a separate Wear OS companion.
Recent releases added expanded incident/certificate/domain/event dashboards, slow-response alerts, managed Kuma webhook setup, native SFTP monitor creation, Tailscale-aware local-network handling, and broader Uptime Kuma 2.5 compatibility.
F-Droid: https://f-droid.org/packages/dev.astoris.ursa/
Source, screenshots, docs, current release artifacts, checksums, and SBOMs: https://github.com/greyfoundry/ursa-android
I’d welcome feedback from other F-Droid users, especially on whether the permissions and privacy explanations are clear before connection setup.
License: MIT
Source: r/fossdroid · by /u/spiferjoe