What Oncall does not do

Oncall keeps your rota and your incident coordination. Some things it leaves to other tools on purpose, and it says so rather than pretending.

It does not page anyone

Oncall sends no SMS, voice calls, push notifications or paging emails, and it never wakes anyone up. Your existing pager stays in charge of that. Escalation delays you save are stored as data your team can read; no timer runs from them. Any attempt to deliver a page is refused with an explanation.

It does not decide for you

• An alert never declares an incident by itself; a responder does.
• A recovered alert never resolves an incident; resolving needs a person, a summary and recovery evidence.
• Coverage previews and the now-and-next view explain the schedule you configured. They are not proof that anyone was reached.

It does not reach into your other accounts

Moving in from Opsgenie or PagerDuty reads export files you saved yourself. Oncall asks for no API key, makes no request to those services and turns nothing on there. Imported schedules arrive paused for you to review. See Move in from Opsgenie or PagerDuty for exactly which rota shapes come across and which are named as differences.

It does not call AI or outside services

Nothing you write in Oncall is sent to an AI model or any outside service. Sign-in emails on your own computer go to a local outbox.

It runs on your computer today

Oncall runs on your own computer. Running it for a whole team on a server waits on a tested standby: rer deploy --dry-run checks the build, and a real deploy refuses until then.