Product

Five parts of Perstat share one availability record, from monitoring to the interfaces and apps around it. You can read how each one works without an account.

Perstat cockpit showing availability, incidents, and live activity
Real product UI, sample data.

The common record is the product model

The cockpit, timeline, status communication, and later review all refer to the same event. Perstat does not copy a check result into a separate incident story.

  • MeasuredSignals and confirmed incident boundaries retain their timestamps.
  • AttributedAcknowledgments and curation show who acted and why.
  • ReversibleCuration can be previewed and reversed. Perstat does not describe the record as tamper-proof.
A fit when
You want one availability record from the first signal through response and later review.
Keep other tools when
You need APM, log management, or a native Android app. Perstat does not provide them.

One lifecycle from signal to review

Every view works from the same event instead of handing an outage between disconnected tools.

  1. 01Measure

    Thirteen check types observe services, hosts, and jobs.

  2. 02Confirm

    Eleven regional check types can require agreement across regions before an incident opens.

  3. 03Own and respond

    Acknowledgment makes ownership visible. On-call escalation starts with Sentinel.

  4. 04Communicate

    Status pages publish the incident explicitly to the audiences you select.

  5. 05Review

    The availability record keeps measured events, curation, and actions together.

Five parts, one record

Open the public samples before you sign up

Each public sample states what it can and cannot show.

Start with a check or the buying review

All five prices and the plan boundaries are public, and standard plans are self-service. Security and documentation stay readable without an account.