From registration to your first trustworthy alert.

Guided onboarding takes you through a real check, a delivered alert and a published status page.

1. First monitor

HTTPS is the simplest starting point. Enter a public address, expected status range and interval. Public probes block localhost, private networks, metadata endpoints and DNS rebinding.

GET https://api.example.com/health
expected: 200–399
quorum: 1 / 1 (current deployment)

2. Alerts

Add email, Telegram or a webhook. Run channel.test — only a delivered test completes the onboarding step.

3. Status page

Choose components, a slug and history range. The snapshot is signed and served by a separate renderer with no access to PostgreSQL or NATS.

4. Incidents

Retries, failure thresholds, recovery and anti-flap protect against one-off failures. After adding independent regions, you can increase quorum without changing the monitor type.

5. SLA reports

Paid plans can generate signed reports with uptime, incidents, maintenance and response metrics, including scheduled delivery.

6. Voice

SIP OPTIONS checks signaling. REGISTER tests authentication. Synthetic Call adds SDP, RTP, DTMF, IVR and diagnostic MOS. These features require an active Voice region and a verified target.

7. API

API keys belong to service accounts and explicit scopes. The secret is shown only once, and every operation leaves an audit trail.

8. Security

Enable TOTP or a passkey. Enterprise organizations can enforce OIDC. Sensitive operations require fresh step-up authentication.