Standby

Yes. You run it on your own machines against your own PostgreSQL, and it is white-label throughout — your customers see your name on the status page, not ours.

Outbound reach to your install. It does **not** need an inbound port opened to it, which is the usual objection and a fair one. It runs on Debian, Ubuntu, RHEL, SUSE, Alpine and Windows.

Because it exists to be readable during an outage. If it shared a host or a database with on-call, the incident that took on-call down would take the page down with it — exactly when people are loading it. On-call pushes HMAC-signed events to the status app, which applies them to its own store and regenerates a static snapshot. An audience arriving all at once reads a file, not a render.

No, but it is the part customers actually see, and running it apart is the whole reason it stays up during the incident it is reporting. It is a second small deploy, not a second product, and it is included.

The outside probes can watch any endpoint — HTTP, TCP, ICMP, SSL expiry or DNS — from more than one region. The agent is for machines you run.

They are matched against the packages each host **actually has installed, at the version it actually has**. A finding is about your machine rather than about software you do not run — which is the difference between a report you act on and one you learn to ignore.

Backups are replayed by **restore drills** on a schedule and the count is recorded, so you can answer "when did you last test that?" with a date. Compliance scores are derived from what the fleet is observed doing, and signed — not from a spreadsheet filled in before an audit.

Per device, with the status page included rather than sold separately.

It keeps running and keeps watching. You stop receiving updates, and the admin says so plainly rather than degrading quietly.