We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
On-call notification and escalation
AlertRoster takes events from the systems you already monitor, works out who is responsible from your schedule and escalation policy, and notifies those people — on their phone, at their desk, and out loud in the room — until one of them acknowledges.
Operational alerting from Cloud Bedrock. Not a life-safety system — read what that means .
Incident
DB-02 stopped checking in
Illustrative example. Timings come from the escalation policy you configure.
One roster, one escalation policy, and every channel that gets a person's attention.
Who is responsible, and when. Rotations, handoffs, and overrides live in one roster your team can read without asking anyone.
If nobody acknowledges, the alert moves to the next person on the policy. It keeps going until someone takes it.
Dead-man's-switch monitoring. When a system that should check in every minute goes quiet, that silence becomes the alert.
A native iOS app, desktop workstations, and on-premise audible and visual alerting hardware at the site itself.
Who was notified, on which channel, at what time, and who finally acknowledged — recorded per incident.
Each organization's data is separated by Postgres row-level security, enforced by the database itself rather than by application convention.
Four steps, and the fourth one repeats until it doesn't have to.
From your monitoring, or from a heartbeat that stopped arriving.
The schedule says who is on call right now. No group chat, no guessing.
On every channel you have configured for them, at once.
An acknowledgement ends it. Silence moves it to the next person on the policy.
A phone in a pocket, on a loud floor, in a Focus mode, is a single point of failure for getting someone's attention. AlertRoster can drive on-premise audible and visual alerting hardware at the site, so an unacknowledged alert becomes something people in the space can hear and see.
We supply the software that commands that hardware. We do not manufacture, install, or maintain it.
AlertRoster is an operational alerting tool. It is not a life-safety system, fire alarm, security alarm, or emergency notification system, and must not be relied upon as a substitute for one. Do not use AlertRoster where failure to receive an alert could result in injury or loss of life.
Alerting products are usually sold on promises nobody can keep. Here is the honest version.
Alerts are delivered on a best-effort basis over networks we do not own: Apple's push infrastructure, carrier networks, the public internet, and your own LAN and hardware.
Device settings — Do Not Disturb, Focus modes, silent mode, notification permissions, low power mode — can suppress or delay an alert. That is why the on-site channel exists.
The critical-alert capability on iOS, where available, requires an Apple entitlement and your explicit authorization. Where it is not available, alerts arrive as high-priority time-sensitive notifications, which do not bypass all device silencing.
We do not claim any alert is guaranteed to arrive, to arrive within a stated time, or to override a device's settings.
There is no uptime or delivery SLA today. When there is one, it will be a contractual number rather than a sentence on a marketing page.
We hold no security or privacy certification at this time, and will name the specific audit when we do.
Specifics, because "enterprise-grade" is not a specification.
AlertRoster is being rolled out with a small number of teams. If your operation has someone on call tonight, we would like to hear how it currently works.