Skip to main content
Pre-launch. The product described here is being built. Pages still carrying skeleton content from the template are marked; run grep -rn "TODO: replace before launch" docs/ to find them.

What this is

Scaling is incident management for the people who get woken up. It routes an alert to whoever is actually on call, escalates when nobody answers, and keeps the record of what happened afterwards. It is for teams small enough that on-call is a rota rather than a department, and who have discovered that the expensive part of an incident is not detecting it — it is the twenty minutes spent working out who to wake.

Where to go next

Quickstart

Sign up, create an organisation, and make one authenticated call.

Your first API call

A worked example against a running instance, including the failure cases.

API reference

Base URL, authentication, and the shared error shape.

Guides

Task-shaped walkthroughs. One ships with the template; add yours beside it.

How this site is organised

This part is true of the skeleton and worth keeping. Documentation for a change is written before the change and a ticket is not finished without it. If a page reads awkwardly, the API is usually wrong — that is the point of writing it first, and it is cheaper to discover here than after it ships.