Tivni Ask for early access

Every incident has one name on it.

Tivni is an on-call pager where handing an incident over is something you do, not something you type into a chat. Whoever claims it is the one who gets paged.

Ask for early access

Tivni is being built. There is no public release yet.

One incident on checkout-api, as Tivni records it

  1. Error rate at 8%. Tivni pages the engineer on call.

  2. Push to Asha. No answer.

  3. Text to Asha. No answer.

  4. Call to Asha. No answer.

  5. Escalated. Push to Ben.

  6. Ben acknowledges.

    Ben has it
  7. Ben's shift ends. Ben offers it to Chen.

    Status
    Rolled back the 01:50 deploy. Error rate is falling.
    Impact
    About 1 in 12 checkouts failed for 20 minutes.
    Next
    Watch for 30 minutes. If it climbs, fail over.
  8. Chen claims it.

    Chen has it
  9. The alert fires again. Tivni pages Chen, not Ben.

Being paged, nobody has it yetBenChen

Handing over is something you do.

Most incidents change hands at least once: a shift ends, or the fault turns out to belong to another team. In a chat thread, "handing over to you" can mean it was read, or not. Tivni makes it an act with two sides.

  • Acknowledging is taking it

    The person who acknowledges a page has the incident. Tivni stops paging everyone else.

  • You offer, they claim

    You offer the incident to a person or a team, with a short note: status, impact, next action. It stays yours until someone claims it.

  • The claim moves the pages

    From the moment they claim, every page for that incident goes to them. There is no second tool to update.

  • If nobody claims

    Tivni pages up the receiving team's escalation. You still have the incident, and the record says so.

  • Shift over, incident open

    Tivni asks you to hand it over before you leave. It never moves an incident by itself.

The record keeps who knew what, and when.

After an incident, the hard questions are about people and minutes. Tivni keeps the answers as it goes.

  • Every page, by push, text, call or chat, and whether it arrived.
  • Who acknowledged, and when.
  • Each handoff: who offered it, the note, who claimed it.
  • The stretches when nobody had it, and who was being paged.

Pages reach people the way they choose.

Push, text message, voice call, Slack. Each person sets their own order and the wait between steps. If one way fails, Tivni goes to the next.

Hand over to another team, or another company.

When the fault is on the other side of a boundary, offer the incident across it. Their on-call is paged under their own rules, and each side chooses what the other sees.

Tivni is being built.

We are building a working prototype and testing it on our own phones first. If handoffs are where incidents go wrong on your rota, tell us how. It shapes what we build.

Early access is not open yet.