§01.1 · DETECT · LIVE
HTTP monitoring
HTTP probes on configurable intervals, methods, expected status codes, and latency thresholds. Three consecutive failures open an incident; three consecutive successes close it. SSL-expiry, DNS, keyword, and multi-region checks are on the roadmap — not yet shipped.
§01.2 · DETECT · LIVE
Third-party alert ingest
Receive incidents from Prometheus Alertmanager, Datadog, CloudWatch (via SNS), Grafana, Sentry, or the generic JSON endpoint. Tenant-scoped tokens, Datadog HMAC verification, CloudWatch SSRF hardening, dedup + normalize + auto-resolve after 24h.
§01.3 · DETECT · PLANNED
Synthetic user journeys
Headless Chromium walking login → checkout → logout every 60 seconds, with screenshots and HAR on failure. No code yet — this is a roadmap item, not a shipped feature.
§02.1 · TRACE · LIVE
Deploy correlation
Inbound deploy webhooks record every release with SHA, branch, author, and optional commit list. Every incident is ranked against recent deploys by time proximity and confidence. One cURL line from your CI is all the wiring.
§02.2 · TRACE · LIVE
Suspect scoring
Every candidate deploy scored on temporal proximity, locality (does it touch the affected service?), and blast radius (lines changed, tests skipped). Top-N ranked with a one-line rationale per candidate.
§02.3 · TRACE · LIVE
Diff-aware recaps
Commit analysis pipeline reads the actual diff — hunks, file paths, structured evidence — not just the commit title. Produces a diagnosis explaining which change likely broke what, with direct quotes from the patch.
§02.4 · TRACE · LIVE
Distributed trace correlation
Pull spans for the failing request from whichever backend you run: Tempo, Jaeger, Honeycomb, New Relic, Elastic APM, AWS X-Ray, or Lightstep. Shown inline with the suspect commit.
§03.1 · RESPOND · LIVE
AI-drafted fix PRs
One-click revert for confident reversal candidates; AI-drafted patches for smaller fixes. PRs open through our GitHub App with scoped permissions and signed commits. Honors your branch protection — we do not bypass reviewers.
§03.2 · RESPOND · LIVE
Slack notifications
Outbound incident notifications via Slack incoming webhook, routed per channel. Channel-per-incident war rooms, slash commands, and socket-mode two-way chat are on the roadmap— today we send, we don't listen.
§03.3 · RESPOND · LIVE
SMS + voice paging
Twilio-backed SMS + voice (TwiML announce + DTMF acknowledgement). Web push via VAPID. US/CA/UK at cost; +30% uplift for other destinations. Hard caps, burst limiters, storm-mute on by default.
§03.4 · RESPOND · LIVE
On-call schedules
Rotations, overrides, escalation chains, timezone-aware calendars. iCal export so Google / Outlook show who's holding the pager. Phone-verified contacts with bcrypt-hashed OTPs.
§03.5 · RESPOND · LIVE
Auto postmortems
Every resolved incident drafts a postmortem — summary, timeline, customer impact, root cause, contributing factors, action items, and a link to the fix PR. Edit in-app, then publish.
§04.1 · COMMUNICATE · LIVE
Status pages
Public and private pages on custom subdomains. Service status aggregation, timestamped incident updates, 30s revalidation. Subscriber email/webhook notifications and scheduled maintenance windows are on the roadmap — not shipped yet.
§04.2 · COMMUNICATE · PLANNED
Customer changelog
An opt-in changelog embedded on your status page so customers see what shipped that morning right next to the incident it caused. No code yet.
§04.3 · COMMUNICATE · PLANNED
Geo latency map
Regional probe results plotted on a map so you can tell whether an outage is global, AWS-regional, or one ISP in Ohio. Requires multi-region probing first — both planned, neither shipped.
§05.1 · PLATFORM · LIVE
SSO, SAML, audit log
GitHub + Google OAuth on every plan. SAML + SCIM via WorkOS on Enterprise. Every admin action recorded in a hash-chained, tamper-evident audit log. Verify the chain at any time; export CSV or NDJSON.
§05.2 · PLATFORM · LIVE
Encrypted secrets
AES-256-GCM for observability credentials, webhook signing secrets, and alert ingest tokens. Alert tokens stored as SHA-256 hashes — plaintext returned once, never persisted. Single ENCRYPTION_KEY per deployment today; per-tenant KEKs via KMS are on the roadmap for Enterprise.
§05.3 · PLATFORM · LIVE
Self-hosted option
Docker Compose for a production-ready install. Bring your own Postgres 15+ and Redis 7+. Helm charts for Kubernetes are on the roadmap — today, you drive self-host through compose.