An alert nobody handled has to ring again.
OnCall takes the alerts from your monitoring, stores them per organization, notifies whoever is on call and escalates whatever stays unattended. It does not promise availability: it shows the real state of every alert and what action is still pending.
Alertmanager and CloudWatch, with a credential that identifies the organization.
There is no global token. The ingestion credential is what says whose alert this is, and it was the one door left open for writing into somebody else's organization.
- Deduplicates by fingerprint and keeps the full history.
- Normalizes source, state, severity, title, summary, labels and timestamps.
- Two organizations can hold the same alarm under the same name without mixing.
- A webhook without a valid secret is rejected. In production there is no permissive fallback.
Six actions, four places to take them from.
Acknowledge, resolve, snooze, assign, escalate and comment, from the web, the Android app, Telegram or Google Chat. Which actions are offered is decided by one shared function, so all four channels show the same thing at the same moment.
- Acknowledging creates the silence at the source; resolving expires it.
- Acknowledging and resolving stop the escalation. Snoozing moves it. Assigning does not touch it: handing something to someone who is asleep is not having handled it.
- Every action records who, when, and through which channel it arrived.
- Messages already posted in the team channel are rewritten with the new state instead of stacking one more.
Explicit rotations, a fallback phone, and tiers with their own timings.
Escalation goes from push to Telegram to SMS, with the timings each organization configures. The active rotation is resolved inside the organization, and a phone number is not enough to identify anyone.
- On Android a critical alert plays through the alarm audio channel, not the notification one, which is the channel silent mode turns off.
- Bypassing Do Not Disturb needs a permission granted in the system settings: if it is missing, the interface says so instead of failing quietly.
- Every delivery, and its result, stays in the history of the alert.
Three things we would rather say now.
- OnCall does not promise a notification reached the phone: it records what it knows. Today it knows the provider accepted it; the delivery receipt from the device is under construction and tracked in the open.
- We do not sell 24×7 support, because we cannot sustain it today. What each plan commits to is written on its card and not in a footnote.
- The service runs on a single node. Before charging for it there is a list of missing pieces — backups with a tested restore, replicas, a separate database — and that list is public.
Musubi OnCall
OnCall Free
To wire up your monitoring and find out whether the product helps, with no card.
Free
- Up to 3 responders
- Alertmanager and CloudWatch, with a credential per organization
- Browser and Android push, with a channel per severity
- Telegram and Google Chat, with the same six actions
- 30 days of alert history
OnCall Team
RecommendedFor a team with real on-call duty: rotations, escalation and SMS included.
$9per person per month
- No cap on responders
- Rotations, fallback phone and an on-call calendar
- Tiered escalation with per-organization timings
- 50 SMS per person per month
- 365 days of alert history
- Email support, answered within 2 business days
OnCall Business
For when being on call is a commitment to somebody else and the history has to be presentable.
$19per person per month
- Everything in OnCall Team
- 200 SMS per person per month
- 3 years of alert history
- History and event export
- No cap on ingestion credentials
- Email support, answered within 1 business day