Night Shift
$390/mo per rotation
Triage and investigation. Nightwatch observes, concludes and briefs. It never touches production.
- Acks, triages & investigates every page
- Evidence-cited incident summaries in Slack
- Up to 10 services
- 30-day audit log
Nightwatch · AI SRE
When the page fires at 3 AM, Nightwatch acks it, reads the logs, the dashboards and the last deploy, then drafts the fix PR and the incident summary. It wakes a human only when judgment is genuinely required.
Private beta · read-only by default · SOC 2 in progress
Replay of incident INC-4127: at 03:07 AM a SEV-2 page fires for checkout-api p99 latency. Nightwatch acknowledges it, reads the logs and dashboards, correlates the regression to a deploy 22 minutes earlier that shrank the database connection pool, drafts the revert PR, rolls back behind a canary, and closes the incident at 03:11 AM. No human was woken.
02 · The 3 AM tax
The hour your roadmap pays for your reliability
Pager fatigue isn’t a tooling gap. It’s a staffing model where your best engineers do their worst work. Woken at random. Dropped into a maze of dashboards. Re-deriving context a machine already had. Fixing the same class of regression they fixed last month.
The on-call rotation was designed for a world where only a human could read the logs. That world ended.
03 · Operating loop
Acks in seconds, not snoozes.
Nightwatch acknowledges the page, dedupes the alert storm, pulls the runbook and the service map, and states a working hypothesis before a human would have found their glasses.
Reads everything. Forgets nothing.
Logs, dashboards, traces, the last ten deploys, that config change from Tuesday. Every claim cites its evidence: line numbers, chart links, commit hashes. The morning review takes minutes, not a meeting.
Drafts the fix, under your rules.
Rollbacks, reverts, scale-ups and feature-flag kills, proposed as PRs and runbook actions, executed only inside policies your team wrote. Nothing touches production that you didn’t pre-authorise.
Wakes you only for judgment.
Some calls are genuinely human: data-loss risk, customer comms, an unknown unknown. For those, Nightwatch pages with the full story attached. You wake up briefed, not blind.
04 · Patched into
Connect via scoped, revocable API credentials, read-only by default. Something custom in your stack? Nightwatch speaks anything with an API and a log line.
05 · Rules of engagement
# least privilege, written by your team
mode: read_only
allow:
- logs.read
- metrics.read
- deploys.read
actions:
pr.draft: auto
rollback: requires_approval
db.write: never
escalate:
sev1: page_human_immediately
uncertain: page_human_with_brief06 · Pricing
Priced per on-call rotation, not per seat. The whole team reads the summaries; nobody pays to sleep.
$390/mo per rotation
Triage and investigation. Nightwatch observes, concludes and briefs. It never touches production.
Most teams
$1,180/mo per rotation
The whole loop. Guarded actions under your policies: rollbacks, fix PRs, runbook execution.
Customannual
For platform orgs running many rotations, with the compliance team in the room.
※ Waitlist teams lock founding pricing: 40% off the first year, forever-grandfathered.
07 · Early access
We’re onboarding a small number of engineering teams into the private beta, pager-heavy stacks first. Founding pricing locked for everyone on the list.
A Lunvex Labs venture