On-Call Rosters & Schedules

Build the rotation once and it keeps turning. Everyone can see whose week it is, overrides cover holidays and swaps, and the escalation policy pages the person the roster names - not the whole channel.

roster daily_oncall · Europe/London on call now: Rio until Fri 09:00

primary

backup

Thu-Fri backup is an override - the underlying rotation is untouched and resumes on Saturday.

Incident fires -> on-call roster consulted -> escalation chain paged until ACKed -> incident closed.

Schedules & rotations

Build daily, weekly, bi-weekly, or custom rotation schedules. Set the members, the order, and the handover time, and the rota keeps turning without anyone re-typing a spreadsheet. Everyone takes their fair share, the schedule is always visible, and your team knows exactly who's on call and when their turn comes around.

Overrides & swaps

People take holidays. People get sick. People swap shifts because they have a dentist appointment on Tuesday. Overrides let you handle all of it without breaking the underlying rotation - a one-time override for a specific date range, after which the original schedule resumes exactly where it would have been.

A roster per team or service

Platform, database, and application on-call rarely belong to the same people. Create as many rosters as you need, each with its own members and cadence, and let escalation policies pick the one that fits the alert. Handover times are timezone-aware, so a distributed team hands over at the right local hour.

Escalation chains

If the on-call engineer doesn't respond in five minutes, escalate to the next person. Then the next. Different channels at each step - a push notification first, then SMS and WhatsApp. Every incident gets handled, even if someone's phone is on silent or they slept through the notification. Acknowledge to stop escalation, or let it keep climbing to the catch-all so nothing ever ends in silence.

See how alerting and escalation policies work

Acknowledge from anywhere

Pages reach Slack, Telegram, WhatsApp, SMS, email, and the mobile app. Acknowledging in any one of them stops the escalation everywhere, so nobody further up the chain gets woken for an incident that is already being handled.

Priced per server, never per teammate

Per-seat on-call tools charge you for every engineer you add to the rotation, which is exactly the wrong incentive - it pushes small teams to keep the rota short and burn the same two people out. AlertKick's bill tracks your infrastructure instead, and your whole team is included on every plan.

Common questions

Do you charge per person on the rota?
No. Plans are priced by infrastructure, not seats, and your whole team is included on every plan - including the free one. Adding someone to the rotation never changes the bill.
Can one team have more than one rota?
Yes. Create a roster per team or per service - platform, database, application - and point each escalation policy at the roster that fits the alert.
What happens to the rotation when someone takes an override?
Nothing. An override sits on top of the rota for a date range. When it ends, the underlying rotation carries on from where it would have been.
Can I use it for on-call without using your monitoring?
Yes. AlertKick accepts alerts from Prometheus Alertmanager, Grafana, Datadog, CloudWatch, Zabbix, Nagios, Icinga2, and a generic webhook. Point your existing alerts at it and use it purely as the on-call and escalation layer.

Your servers, watched by tonight.

Install one agent. Get security monitoring, infrastructure alerts, and on-call management - all included with every host.