The on-call desk that opens the fix.
Nightglass was built around a single observation: alerting is no longer the bottleneck — the stretch from page to fix is. We are building the desk that closes that stretch, so the rotation reviews a change instead of writing one under duress.
Alerting is solved. The stretch from page to fix is not.
Modern alerting is fast. Alert correlation layers can fuse logs, traces, and deploy markers into a single incident card in seconds — and then escalate. The on-call still has to wake up, read the diff, decide whether to revert, write the patch, and queue the rollback. The correlation layer has handed the page off, but the work has just started.
The bottleneck on a bad night is no longer detection; it is the stretch from page to fix. Even an engineer who rolls out of bed in two minutes needs another ten to read the failing path, decide what changed in the last hour of commits, and produce a patch that will hold under review. That is a quarter-hour of customer-impact window multiplied by every incident the rotation absorbs in a quarter.
Nightglass pulls the fix forward into the desk. The same desk that correlates the signal drafts the PR, embeds the rollback, queues the Slack thread, and stages the one-click revert behind the merge button. The on-call still reviews and still merges, but they review a change instead of writing one.
Every incident arrives with a fix queued and a rollback wired.
The founding mission is to make every incident arrive with a fix queued and a rollback wired. Not a recommendation, not a draft the on-call has to edit — a PR that the on-call can read, merge, or revert in under a minute. The desk writes the postmortem. The on-call signs off.
Nightglass is being shaped into a colleague, not another alert-correlation layer. That means reading the repo, learning the team’s conventions, calibrating confidence against the team’s error budget rather than a generic noise threshold, and routing every action through the channels the team already lives in. The work is to give every operation a desk that already knows its codebase.
The near-term arc is wider integrations and tighter confidence. Wider on alert sources and Git hosts so Nightglass fits any pager rotation; tighter on the PR-confidence floor so the on-call desk only opens fixes that will hold under review. The end state is an on-call rotation that reviews code instead of writing it under duress.
From the page to a queued PR in under fifteen seconds.
The same artefact the home console renders, told as a sequence. Each step is one beat of an incident that opens against checkout-api at three in the morning.
- 01[detect]
SLO breach fires at INC-2419 on checkout-api. error_budget_burn = 4.2× against payment.charge, severity scored against the team’s budget — not a generic noise floor.
- 02[correlate]
The desk reads the last hour of commits on checkout-api and matches the failing path to feat/checkout-retry-with-jitter (commit a91f3c, deployed 38 minutes ago).
- 03[triage]
SLO at 38% of budget. Severity scores SEV-2; ownership maps to the checkout rotation. Page routes to #sre-checkout with Joon on call.
- 04[open]
The desk opens PR #1841 against checkout-api with the rollback pre-wired — revert queued behind the merge. A Slack draft posts the same channel; the on-call reviews the diff and picks merge or revert in one click.
The desk is ready when the rotation is.
Join the waitlist and an engineer will follow up, or skip the queue and book a working session with the team that builds it.
Join the list / request a demo.
The list stays short; a real engineer reads every demo request.
Join the Nightglass listRequest a demo