Nighthawk · overnight on-call
Nighthawk watches production overnight. It fixes what it is sure of, and it scores the blast radius before it touches anything. On payments, auth, and data-loss paths, it does not guess.
When it is not certain, it escalates, and the escalation is the product. It pages you with a complete case file: the incident, a reproduced failing test, every fix it tried and why each was accepted or rejected, and ranked root causes.
Read-only by default · protected paths never shipped without sign-off
guard retry in auth/middleware
blast radius · every authenticated session
cap retries on payments/retry/backoff.ts
isolated path · 41 tests green · reversible
Two patches, one verdict each
01 · The escalation
At 03:12 a SEV-2 fires for checkout-api 5xx errors. Nighthawk acknowledges it without paging anyone, reproduces the failure as a red test, and traces it to a deploy that added a retry on timeout. Its first fix would guard the retry inside auth middleware; the risk gate rejects that because auth is a protected path with a blast radius of every session. A second, contained fix on an isolated payments retry path passes the tests and opens PR 2231 behind a flag. The durable root cause sits in the protected payment-capture path, where Nighthawk’s confidence is 0.58, below the 0.80 gate, so it escalates: it compiles a case file with the incident, the failing test, both fixes and why each was accepted or rejected, and three ranked root-cause hypotheses, then pages the on-call engineer.
02 · The risk gate
Plenty of tools can write a patch at 3 AM. The hard part is knowing which patch is safe to ship and which one should wake a human. Nighthawk decides with three numbers, every time.
# the gate, written by your team
gate:
min_confidence: 0.80
max_blast_radius: service
protected: # never auto-written
- payments
- auth
- data_migrations
actions:
pr.draft: auto
rollback: requires_approval
protected.write: never
escalate:
below_confidence: page_with_case_file
protected_root_cause: page_with_case_file03 · Pricing
Priced per on-call rotation, not per seat. The whole team reads the summaries; nobody pays to sleep.
$390/mo per rotation
Detect, reproduce, and brief. Nighthawk reproduces the incident, ranks the root cause, and hands you the case file. It never touches production.
Most teams
$1,180/mo per rotation
The whole loop, under your risk gate. Contained fixes ship as PRs. Protected paths still wake you.
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.
04 · Early access
We’re onboarding a small number of teams into the private beta, the ones without an on-call rotation first. Founding pricing is locked for everyone on the list.
A Lunvex Labs venture