Repository navigation
Home
AstorisTheBrave edited this page Oct 17, 2026
·
7 revisions
URSA is a native Android companion for Uptime Kuma. It puts every saved server on one attention-first Home screen, keeps the active server live, and delivers push through UnifiedPush without Firebase, a hosted relay, or a paid tier.
- Installation - choose the F-Droid, GitHub phone, or Wear APK
- Getting Started - connect, sign in, and learn the four main destinations
- Features and Workflows - practical examples for monitoring, incidents, exports, management, privacy, and multiple servers
- Push Notifications - managed Webhook setup and device alert policy
- Wear OS - public or privately paired watch setup
- Troubleshooting - connection, Android 17, push, and Wear fixes
- FAQ - short answers to common questions
- Home summarizes every saved Kuma server from live, refreshed, or encrypted cached data and puts affected or stale servers first.
- Monitors gives the active server a searchable, filterable inventory and an Overview, History, and Configuration workspace for each monitor.
- Incidents separates durable Kuma transition history from local Android alert groups, with reliability summaries, private notes, and redacted sharing.
- Browse makes secondary tools visible: maintenance, status pages, notifications, certificates, domains, event and aggregate views, exports, presets, imports, servers, and settings.
URSA supports all monitor types in the verified Uptime Kuma 2.5.6 catalogue through either a safe native editor or an explicit Kuma browser fallback. It is a focused client, not a second server: account, database, API-key, Docker-host, remote-browser, and other server administration stay in Kuma.
- Credentials, sessions, access headers, caches, private notes, and local alert policy are encrypted at rest.
- Custom per-server headers support Pangolin, Cloudflare Access, and similar gates.
- Screenshot protection can be Off, Sensitive screens only, or Always.
- No ads, analytics, paywalls, subscription, or premium tier.
- Architecture - data flow, ownership, and module boundaries
- Building and Testing - current toolchain and exact commands
- Network and Protocol - verified Kuma 2.4.0 through 2.5.6 contract
- Push Internals - the UnifiedPush receive and policy path
- Security - the user-facing security model
- Contributing - scope, conventions, and pull requests