TokayOps
Source-available · self-hosted · Slack-native

From alert storm to one on-call human - in seconds.

TokayOps is a lightweight incident-management layer between Alertmanager and your on-call engineer. It groups alerts, finds the right person by schedule, escalates until someone answers, and lets them Ack / Resolve right in Slack. One container, your Postgres, your data.

Get started Star on GitHub
See how it works

The problem

On-call shouldn't hurt.

Four failure modes turn a quiet night into a bad one. TokayOps is built to remove each.

The alert storm

Dozens of near-identical alerts wake the on-call again and again. TokayOps groups and deduplicates them into one Alert Group.

The page went nowhere

Wrong team, stale rotation, nobody owns it. Routing by team + severity plus on-call schedules always find the right human.

No one answered

Multi-step escalation with parallel fan-out - the whole shift is paged at once, with delays and timeouts. Nothing hangs on one unanswered ping.

Priced per seat, locked in

Enterprise on-call SaaS bills by the head and owns your data. TokayOps is one container against your Postgres - your stack, your data, no per-seat pricing.

How it works

The path of an alert - from Alertmanager to a human.

Five stages, no glue scripts. Everything below runs inside one process against your Postgres.

  1. 1

    Alerts arrive

    Alertmanager POSTs grouped alerts to the TokayOps webhook, authenticated by a stored secret.

  2. 2

    Group & dedup

    Create or merge one Alert Group by groupKey (fingerprint fallback). The storm becomes a single incident.

  3. 3

    Route to a team

    Team comes from labels, severity selects the escalation policy, and the L1 schedule resolves the current on-call.

  4. 4

    Escalate, in parallel

    A staged job DMs the whole on-call group at once, plus the channel - with delays, timeouts and continue-on-failure.

  5. 5

    Ack in Slack or Telegram

    Block Kit and Telegram buttons: Ack takes ownership and pauses escalation, Resolve closes it. The message updates in place.

Reaches people on
Slack Telegram SMS soon Phone call soon
Lifecycle
new processing triggered acknowledged resolved closed