ProductApps
Phone apppreview
Paging, incident acknowledgement and approvals; iOS first, Android in progress
The incident in your pocket: paged, read and acknowledged from the lock screen.
Monitors, incidents and RFC reviews on iPhone and Android. When an incident opens, the app pages the people on it on iPhone (paging on Android is not wired yet); acknowledge from its page or the lock screen, and a Live Activity and a widget follow it. It signs in with your InOrbit account and keeps its token in the phone's secure store. In early access on TestFlight, by invite.
In early access. A 30-minute call is the way in; there is no SLA during early access.
An incident arrives while you are away from your desk, and the tools to read it and say you have it are on a laptop.
The app is a client of the same public API as everyone else, signed in through your account's own sign-in in the system browser.
How it works
- 01
Where it runs
- On iPhone, with Android in progress. Paging works on iPhone; on Android it is not wired yet.
- 02
What it reads
- Your monitors, incidents and reviews, through the same public API as the console, signed in with your own account. The token stays in the phone's secure store.
- 03
What you approve
- Acknowledging an incident by name, and an agent's ask with Face ID, signed with a key kept on the phone. An approval runs nothing by itself.
Each line says how far it is built today. Live means anyone with an account uses it; preview means it runs in early access or as a pre-release; coming means it is written down and not built yet.
What you get
Paged when it matters
An opened incident pages the people on it, with Acknowledge and Open on the notification. Nothing more is sent once someone has it.
previewAcknowledged by name
From the incident's page or the lock screen. The timeline says who has it and since when; offline, the button stays and says why it cannot run.
previewMonitors, incidents and reviews
How your system stands on the home screen, the incidents list, a monitor's runs, and RFC reviews to read and answer. English and Croatian.
previewApprove with Face ID
An agent's ask shows exactly what would ship. Approving takes Face ID and is signed with a key kept on the phone. An approval runs nothing by itself, and an ask whose change moved on goes stale.
previewApprove a repair from bed
Approving a repair that your own agents run and prove, from the incident. Not built yet.
coming
An incident on the lock screen, as the app shows it.
In the console
09:41
InOrbit
orders-api is down
SEV2 · opened 2 min ago · 31 of 64 runs failed
Your system: 1 incident open, 23 monitors up
Example data
Drawn from the console's own layout. The services, times and numbers are made up for the example.
Every claim on this page has its evidence: the documents that define it, the docs that say how to use it, and the API it runs on.
Proof and links
Documents
- RFC 0074 The phone on call
- RFC 0074.1 Paging that wakes
- RFC 0058 Incidents and postmortems
Not on the public RFCs host yet, so named here without a link.
API
- RESTpreviewThe app speaks the same API as the SDKs, as a bearer client with its own sign-in.
The evidence rule: a model saying it succeeded is never evidence. What counts is what was measured, by what, and when.
Your data, your call
The token lives only in the phone's secure store, and sign-in is your account's own pages in the system browser. The Live Activity names only the phone's owner.
Logs record who did what and the outcome, never content. The platform's own models are self-hosted; a third-party model provider is one you connect with your own key, and it bills you directly, with no line or markup from InOrbit. Separately, our own DPAs with model providers are in progress, none signed yet. InOrbit is not certified: no auditor has attested its controls yet, and the known gaps are listed.
Questions, answered plainly
How do I get it?
In early access on TestFlight, by invite: book a 30-minute call and we send one. The App Store and Google Play listings come later.
Will it wake me through Do Not Disturb?
Waking through silent mode and Do Not Disturb is part of how paging is designed. Ask for the current state on your phone before you rely on it.
Android too?
Yes, both are previews. Paging and approvals signed with Face ID work on iPhone today; on Android the app signs in and shows your monitors and incidents, and paging is not wired yet.
Next step
See it on your own system
Book 30 minutes with an engineer. We look at your system together and, where it fits, open early access for your team.