All systems operational · 99.99% · 214 days since last SEV-1 · View status →
New Vigil Responder — AI joins the call in 10s

When it's 3am,
be ready in seconds.

Vigil is the on-call command center for SaaS teams. Smart routing wakes the right human, AI drafts the timeline, and your status page stays honest — automatically.

KTRSAM+2k
★★★★★ 4.8/5 on G2Trusted by 2,400+ on-call teams · Free 14-day trial
SEV-2 checkout-latency p99 > 800ms now
SEV-3 queue depth rising · eu-west 2m
RESOLVED api error budget recovered 18m
INC-4812payments / checkout-latency● SEV-2 · open 14m
p99 latency spike on /charge
Started 02:14 UTC · 3.1% of checkouts affected · owner: Priya (primary)
● Response 41s👥 5 responders▲ Escalated once
Alert fired

Burn-rate monitor paged payments-primary via app + call.

Acknowledged by Priya

“Looking — rolling back canary first.” War room opened.

Vigil Responder drafted timeline

Correlated deploy pay-api@8f3c1a + 214 related errors.

Vigil Responder · suggesting confidence 92%

Rollback to 8f3b77 would restore p99 in ~6 min. Drafted status update + customer notice. Approve →

✓ Median acknowledge: 38sPagerDuty → Vigil in 11 min✓ 41 incidents auto-resolved this weekSlack · PagerDuty · Datadog · GitHub✓ Status page updated automaticallySOC 2 Type II · EU data residency

On-call teams at fast-moving companies run on Vigil

FernwayLedgerlyKapstanMoonshotNorthbeamCartloop
The platform

Everything an incident needs.
Nothing it doesn't.

Routing, schedules, war rooms, status pages and learning loops — connected so nobody pastes links at 3am.

01 — Smart routing

The right human, woken once

Urgency-aware rules combine service ownership, past fixes and who's actually awake. No more paging the whole team.

payments-api · burn-rate > 4xPAGE
docs-site · cert expires in 20dTICKET
flaky test · staging onlySNOOZE
02 — Schedules that respect sleep

Fair rotations, sane handoffs

Follow-the-sun, overrides in two taps, and load scores that flag burnout before it pages someone.

Mo
Tu
We
Th
Fr
Sa
Su
03

War rooms in one click

Slack channel, bridge, timeline and roles spawn together. Guests get scoped access automatically.

04

Status pages customers believe

Incident state publishes itself. Pre-written templates keep wording calm, clear and consistent.

05

Postmortems without homework

Timelines, graphs and action items are drafted from the response — you just add the lessons.

How it flows

Detect. Respond. Learn.

Three modes, one rail. Switch tabs to see what Vigil does at each stage.

Noise becomes one clear page.

200 related alerts collapse into a single incident with severity, blast radius and likely cause attached.

  • ✓Alert grouping across Datadog, Prometheus, Sentry
  • ✓Flap suppression + maintenance windows
  • ✓Auto-severity from blast radius
●●●   grouping — live
# 214 alerts → 1 incident
group_by: service + deploy_sha
correlate: errors ↑ 18x after pay-api@8f3c1a
severity: SEV-2 (3.1% checkouts)
page: payments-primary (Priya · 41s median)

Everyone knows their job.

Commander, comms and ops roles are assigned on open. Runbooks and rollbacks sit next to the timeline — not in another wiki.

  • ✓Role assignment + stakeholder paging
  • ✓One-tap rollback & feature-flag links
  • ✓Responder drafts updates for approval
●●●   war-room — INC-4812
/vigil role commander @priya
/vigil page payments-secondary
/vigil runbook checkout-latency-v4
status → “Identified — rolling back canary” (auto-posted)

The next incident is shorter.

Timelines write themselves from pages, chats and deploys. Action items open as tracked tasks with owners.

  • ✓Auto-drafted timeline + customer impact
  • ✓Blameless template + follow-ups
  • ✓Repeat-incident detection
●●●   review — INC-4812
## What happened (drafted)
detected 02:14 · mitigated 02:31 · resolved 02:58
## Actions →
[ ] canary auto-halt on burn-rate @sre
[ ] p99 alert threshold 800→600ms @payments
Automation

Declare the boring parts.
Keep the judgment calls.

Escalations, pages and status updates as readable rules. Humans approve the moments that matter.

Median acknowledge38s ↓ from 4m12s
Pages per incident1.3 ↓ from 6.8
●●●   vigil.yml
on: burn_rate > 4x for 2m
do:
  - page: payments-primary (app + call)
  - open: war-room + bridge
  - draft: status-page "Investigating"
escalate: +secondary after 8m unacked
resolve: auto-close when burn < 1x for 15m
Proof in numbers

Calmer on-call, measurable in weeks.

0smedian time to acknowledge
0%fewer 3am pages after grouping
0 minmedian SEV-2 mitigation time
0.99%status-page delivery uptime
Customers

Teams sleep better on Vigil.

★★★★★

“We cut pages by two-thirds in a month. The first SEV after switching felt… boring. That's the highest praise I can give.”

KT
Kara TurnerSRE Lead, Ledgerly
★★★★★

“Customers stopped asking 'is it down?' Our status page updates itself before support even notices. Trust went up, tickets went down.”

RS
Ravi ShahVP Engineering, Kapstan
Pricing

Pay for responders, not noise.

Unlimited alerts and status pages on every plan. 14-day trial, migrate from PagerDuty in an afternoon.

Starter

$0
For side projects & tiny teams
  • Up to 5 responders
  • Unlimited alerts + 1 status page
  • Slack integration
Start for free

Team

$24 / responder
For SaaS teams with real SLAs
  • Unlimited responders + schedules
  • Responder AI + auto-timelines
  • Status pages + call routing
Start 14-day trial

Enterprise

Custom
Regulated & global orgs
  • EU residency + audit logs
  • SAML, SCIM, dedicated phones
  • Migration + game-day support
Talk to sales
FAQ

Asked at 3am, answered now.

How is Vigil different from PagerDuty / Opsgenie?

Routing is only the start. Vigil groups related alerts into one incident, drafts timelines and status updates with AI, and closes the loop with postmortems — so a page becomes a 20-minute fix, not a 3-hour thread.

How long does migration take?

Most teams import schedules, services and escalation policies in under an hour with our PagerDuty / Opsgenie importer, then run both in shadow mode for a week before switching.

Do you support on-call compensation and burnout tracking?

Yes. Load scores show nights paged, interruptions per rotation and override debt, so managers can rebalance before someone burns out.

What happens if Vigil itself goes down?

Pages fail over across regions and to SMS/voice carriers directly. Our status page is hosted on fully separate infrastructure — 99.99% delivery over the last 12 months.

Is my incident data used for training?

No. Team and Enterprise workspaces are never used for model training. Ephemeral AI sessions, scoped tokens, SOC 2 Type II and EU residency available.

Get started

Your next incident
doesn't have to hurt.

Import your schedules today. Page yourself tonight (safely) and watch Vigil route, draft and resolve.

No credit card · Cancel anytime · Free PagerDuty import