FAQ

FAQ

Does URSA need Google Play Services or Firebase? No. Push uses UnifiedPush, so nothing routes through Google. The app is fully FOSS.

Does it work with a reverse proxy or Cloudflare Tunnel? Yes. URSA connects over standard HTTPS and WebSocket, so any transport your instance sits behind works the same way, as long as WebSockets are allowed.

Can I connect to more than one Uptime Kuma server? Yes. Add multiple servers and switch between them.

Does URSA store my password? No. After login it keeps only the session token, encrypted on the device with a key held in the Android Keystore. See Security.

Can I create or edit monitors from the app? Not currently. URSA focuses on watching and quick actions (like pause/resume). You configure monitors, notifications, and status pages in the Uptime Kuma web UI. This may expand later; see the roadmap.

Which Android version do I need? Android 8.0 (Oreo) or newer.

Is it on F-Droid or Google Play? Not yet. An F-Droid release is planned. For now, build from source or install a release APK when one is published.

Will push drain my battery? Push flows through your distributor (e.g. ntfy), not a constantly running URSA service, so the impact is small. If pushes are unreliable, exclude the distributor from battery optimization.

Which Uptime Kuma versions are supported? URSA is developed and verified against Uptime Kuma 2.4.x.

Something is wrong or missing. Open a Discussion or an issue.