Four pillars, one product: monitoring, status pages, incidents and on-call, evidence. This page is the tour. No signup required.
01 · monitoring
Uptime monitoring
12 check typesHTTP with assertions, security headers, DNS and DNS hygiene, domain and TLS expiry, SMTP, IMAP, TCP, ping, traceroute, and host agents. Intervals down to 10 seconds, depending on plan. The reference explains each.
Quorum across regions.An alert fires after more than one region confirms, so a single flaky route does not page anyone.
Host agents for Linux and macOS.CPU, memory, disk, and services. Self-updating.
Maintenance windows.Planned work does not count against you, and the window is on the record.
Fig. 01 · The cockpit. Real product UI, sample data.
Fig. 02 · One monitor, up close: uptime, response, TLS certificate, per-region latency. Sample data.
02 · status pages
Status pages
Your own domain.status.yourcompany.com, not a rented subdomain.
Public or private.Open to the world, shared-password, or viewer accounts.
Subscribers by double opt-in.The people on your list actually asked to be there.
White-labelfrom Command: your brand, not ours.
status.example.comall systems operational
Sample status page component uptime
component
uptime, 90 days
API
99.99%
Dashboard
100%
Webhooks
99.97%
Fig. 03 · A status page, reduced to its components. Sample data.
03 · incidents and on-call
Incidents and on-call
Escalation until someone acknowledges.Push, then SMS, then a phone call. Timings per schedule.
Every phone.Escalation is platform-neutral. The native iOS app with Apple Watch, currently in TestFlight, is a bonus for Apple users, not a requirement.
Post-mortems with action items.Attached to the incident, not scattered across chat and wikis.
Manual incidents.Open, curate, and publish to your status page.
00:00 check fails · eu-fra 00:30 quorum confirms · na-ewr, as-sgp 00:30 push → on-call engineer 05:30 no ack → SMS 10:30 no ack → phone call 11:12acknowledged · incident timeline open
SLA reports with curated exclusion windows.Real window boundaries: the confirmed start of an incident, not a flattering approximation.
Built to be handed over.To a customer, an auditor, or a regulator. The record lives in the product today; a one-click report export is the stated next step.
Security postureis the stated next step on our roadmap. We say so instead of pretending.
The full artifact is worth more than a description:
