Alerting & on-call for teams

Alerts that escalate
when no one answers.

Rouz helps route incidents to whoever's on call. Configure push, SMS and voice delivery, then use timed escalation steps to reach the next responder. Now in invite-only beta.

Push · SMS · Voice · On-call schedules · Live in minutes

PUSH — iOS & macOS SMS VOICE CALL ON-CALL SCHEDULES ESCALATION POLICIES

The escalation ladder

One incident. A clear escalation path.

A trigger fires, Rouz notifies the on-call engineer, and if they don't acknowledge in time it escalates — to the next person, the next channel, the whole rotation — exactly as your policy dictates. You see every step, timestamped, on one timeline.

INCIDENT · db-primary unreachableP1
00:00
Trigger fired
api · "db-primary unreachable"
Firing
00:00
Priya — on call
push → iphone · macbook
Notified
+02:00
Priya
no ack · escalating
Escalated
+02:00
Marcus — secondary
sms + voice call
Notified
+02:38
Marcus acknowledged
incident owned
Acked

What's inside

Tools to help your team respond.

Multi-channel delivery

Native push to iOS & macOS, plus SMS and automated voice calls. Each person sets the order and timing their devices ring in.

Escalation policies

Build multi-step policies with delays, repeats and fall-throughs. If the first responder goes quiet, the next one is paged automatically.

On-call schedules

Rotations with layers, overrides and a live calendar. Everyone sees who's on point now — and when they're up next.

Voicemail & optional transcripts

Keep voicemail recordings alongside incident timelines. Transcription is optional, requires a configured provider, and may not be available for every recording.

Multi-tenant & access control

Organizations, roles, per-topic permissions and API tokens. MFA and passkeys built in. Isolation by default.

Publish from anything

A simple HTTP API and bearer tokens. Wire up alertmanager, cron jobs, webhooks or your own services in minutes.

Reliability you can page

Built to recover from failures.

Notification requests are stored before processing. Retry handling and your escalation policy help recover from failures. Rouz is in beta; delivery can be delayed or fail, and depends on configured channels and notification providers.

Use your organization and topic slugs with a token that can publish to the topic. A 202 response confirms acceptance, not delivery. Escalation requires a configured topic policy.

Invite-only beta

Get the right person on it.

Rouz is rolling out by invitation. Tell us about your team and we'll send you an invite link to set up your organization.