Oncall

What it does

• See who is on call now and who is next
• Build rotations in named time zones with overrides
• Download a private calendar feed of the schedule
• Declare an incident, record notes and decisions, and follow its runbook
• Assign follow-up tasks and complete a review afterwards
• Record alerts from monitoring, route them to services and replay routing safely
• Preview a move-in from Opsgenie or PagerDuty before anything is saved
• Export and restore your data

What it promises

• OC-012Paging is off. Oncall sends no texts, calls or push alerts, and your existing pager stays in charge.
• OC-006Oncall sends nothing outward during an incident; any email it sends is for sign-in links only.
• OC-005A runbook is copied into the incident when it is declared, so later edits never rewrite instructions mid-incident.
• OC-004Resolving an incident needs recovery evidence and a summary, and every change is recorded in an attributed timeline.
• OC-008Incident records you write are never deleted automatically.
• OC-021A move-in preview writes nothing, a person must review it before it is applied, and imported schedules stay paused.
• OC-022A move-in can be undone, and edits you made afterwards are kept rather than overwritten.
• OC-011Rotations hand over by wall-clock time in your named zone, and clock-change gaps show up as visible gaps.
• OC-003Viewers can only read, responders coordinate, and admins manage; alert-sending credentials grant no read access.

Move in from

• Opsgenie (saved files)
• PagerDuty (saved files)

Run it yourself

Install the command once, then clone a product and start it.

$ npx -y @runeditrun/rer cli install
$ git clone https://github.com/just-every/run-oncall
$ cd run-oncall && rer dev

No npm? curl -fsSL https://runeditrun.com/install.sh | sh installs the same command.