All docs

Integrations & API

Mobile app

The Opservo app puts your fleet in your pocket: see which server is unhealthy, ask why, acknowledge the alert and update the incident without opening a laptop. It is read-only by design and can never run a command on a server. Sign-in is approved from your normal web login.

What you can do in the app

  • •Fleet — every server with its health ring, open alerts and a 24-hour sparkline.
  • •Server detail — health, 24-hour trends, what to fix, and a Why is this server in this state? button that opens the AI chat pinned to that server with starter questions such as “What should I fix first?” and “What changed in the last 24 hours?”.
  • •AI chat — the same assistant as the web, streamed live, but read-only: it explains and recommends, it never executes.
  • •Alerts — read and Acknowledge open alerts.
  • •Incidents — acknowledge (“I’m on it”), Assign to me, Post update and Mark resolved. Post-mortems stay on the web.
  • •Settings — push preferences and the app lock.

Get the app

The app is not yet listed in the public app stores. It is distributed as a preview build for iPhone and Android. Email hello@getopservo.com from your workspace address and we will send you the install link.

Sign in

The app never asks for your password. Tap Sign in and it opens the Opservo website in your phone’s browser. Sign in there as usual, including two-factor authentication or a passkey if your account uses one, then tap Approve on the page that follows. The app switches back and is signed in.

Behind the scenes this is an OAuth 2 authorization-code flow with PKCE. The app receives a short-lived access token (15 minutes) and a refresh token that rotates on every use. A session is bound to the workspace you approved it in; to use another workspace, switch on the web and approve again.

Manage signed-in phones

Open Account → Security → Mobile app on the web. It lists each signed-in phone with its platform, when it signed in, when it was last used, and whether push is on. Click Sign out to revoke a phone; it must sign in again. If a phone is lost, revoke it here rather than relying on the app lock alone.

Push notifications

The app registers for push on first launch. Choose what reaches your phone in the app’s Settings or under What to push to my phone on the same web card:

  • •Critical alerts — a server down, a failing disk, a critical security finding, and on-call escalations.
  • •Incidents — when an incident is declared in the workspace.
  • •SLA budget warnings — a monitor has used 80% of its downtime budget, or breached its target.

All three are on by default. Tapping a notification opens the alert, incident or server it is about. If you uninstall the app, Opservo notices the push token is no longer valid and stops sending to that device.

App lock

The app has its own lock in place of the web screen lock: Face ID or fingerprint first, with a 4–8 digit PIN as fallback. Set how long the app may sit idle before it locks, from 1 minute to 1 hour. Five wrong PINs sign the app out, so a lost phone cannot be brute-forced into your fleet.

What the app cannot do

  • •Run commands, fleet runs or runbooks. The terminal and act-mode chat exist only on the web.
  • •Change servers, channels, team members or billing.
  • •Write post-mortems; it links you to the web for that.

Last updated 2026-10-01. Found a mistake? Email hello@getopservo.com.