For · Engineering

Built by engineers who would rather not get paged for nothing.

The cold start guard. The deploy correlation. The audit row per fanout. Engager makes the choices a senior on call would make if they had a vote.

No flapping

The N consecutive failures rule.

A single ping failure is noise. A second is a warning. A third with the same cause is a story. Engager waits for the third before opening an incident.

The threshold is per host. Default is two. Critical hosts can drop to one if you accept the false positive risk.

ts
if (consecutiveFailures >= host.incidentThreshold &&
    !inColdStartReverify(host)) {
  openIncident(host, samples);
}
Threshold logic

Deploy correlation

When latency drifts within fifteen minutes of a Github push, the commit is named.

Engager watches your tracked Github repos. When an incident opens within the deploy window, the matching commit, author, and message are pinned to the incident.

Confirm or dismiss with one click. The signal compounds across postmortems.

Deploys · Incidents

Last twenty four hours

Engineering primitives

Six things you would have built yourself.

Cold start guard

Three stage re verify at 10s, 25s, 55s before declaring a Render free tier dead.

P99 anomaly detector

Rolling baseline, multiplier, sustained sample count, absolute floor. All four configurable per host.

Deploy correlation

Commit, author, minutes elapsed pinned to the incident automatically.

Worker API

HMAC signed routes for test-channel, test-integration, run-report. Designed to be scripted.

Audit row per fanout

Every send is recorded with a timestamp, the kind, the channel, the result.

Fast recovery probe

Ten second cadence loop the moment an incident opens. Recovery email goes out the second the response code clears.

  • No tag soup

    Routing is six fields. No regex. No template language. No "label me, please".

  • Predictable latency

    P95 and P99 from the live distribution, not bucketed approximations. Reports show both side by side.

  • Re entrant

    Every dispatcher is idempotent. A duplicate push of the same incident is a noop, not a duplicate row.

Try it in five minutes. Your on call team will notice the difference in five days.