Triage incidents
Ranked causes for the symptom you describe.
AI incident copilot for SRE teams
Clarity when systems get complicated.
Meet Vigil. Describe the symptom and get ranked hypotheses, the exact read-only commands to confirm them, and a clear next step, without giving any tool access to your infrastructure.
- No credentials or cluster access
- Read-only checks first
- Engineers approve every step
Built for the tools your on-call already uses · integrations coming soon
Why Vigil
On-call is hard. Triage shouldn’t be.
Incidents rarely fail for lack of tools. They stall in the first minutes, when nobody is sure where to look.
Without Vigil
- Alerts fire at 3am and nobody knows where to start
- Thousands of log lines to scroll through
- Generic AI answers that guess and suggest risky fixes
- Knowledge stuck with the most senior engineer
With Vigil
- A ranked triage plan in seconds, from the symptom you describe
- Attach the log; Vigil keeps the errors and the context around them
- Evidence-first hypotheses with read-only checks first
- Shareable investigations the whole team can read and continue
From noise to signal
1,800 log lines down to 6
Drop in a log file. Vigil redacts secrets on your device, keeps the errors and the lines around them, and explains what went wrong.
Try it with your own log →How it fits
Everything you know, turned into a plan.
Vigil sits between the signal and the fix. It never connects to your systems; you bring the evidence, it brings the method.
You bring
Alerts & pages
Logs & stack traces
Error messages
Your questions
VigilTriage engine
- Redact · Rank · Verify · Explain
You get
Ranked hypotheses
Read-only checks
Clear next step
Shareable write-up
Capabilities
One copilot, the whole incident.
From the first alert to the follow-up tickets, Vigil helps at every step, with guardrails built in.
Read your logs
Attach a file; Vigil finds the lines that matter.
Explain alerts
What fired, why it usually fires, what to check.
Write queries
PromQL, Logs Insights and kubectl, ready to paste.
Suggest safe checks
Read-only first; risky steps clearly flagged.
Ask the next question
Every answer ends with one-tap follow-ups.
Draft postmortems
Timeline, factors and actions from rough notes.
Share with the team
Revocable links, Markdown and email.
No access to your infrastructure
Nothing to install, no credentials, no agents in your cluster. You share symptoms; it never touches production.
Read-only first
Every check starts with safe get, describe, logs and metrics commands. Anything that changes state is flagged.
Hypotheses, not guesses
Causes are ranked by how well they fit your evidence, each with the signal that confirms or rules it out.
Use cases
Built for the moments that page you.
Pick a scenario to see how Vigil answers. Every reply is short, structured and ready to act on.
VigilExample answer
payments-api pods are in CrashLoopBackOff after the 14:02 deploy.
The container exits right after start; Kubernetes is backing off between restarts.
Likely causes
- Startup error from new config or a missing env var
- OOMKilled: memory limit too low (exit code 137)
- Liveness probe kills the app before it is ready
bashCopy
kubectl logs deploy/payments-api -n <namespace> --previous
Ask next
How do I compare the two releases?How do I roll back safely?
~10s
to a first triage plan
Typical response time in our tests
0
credentials or agents
Vigil never touches your systems
3
follow-ups after every answer
So the investigation keeps moving
30 days
revocable share links
Hidden from search, stop anytime
Early access
Give your on-call team a calmer 3am.
Join the waitlist for team workspaces, integrations and private deployments.