Features · AI & Automation · AI Triage
AI & Automation · Triage

Three alerts firing, one cause.
AI gets there first.

Stop reading three pages of dashboards to find out it's the same disk filling. AI Triage groups noisy symptoms, ranks by real impact, attaches the evidence — and points at the change that broke things.

Without AI alerts · firing 02:31
Disk /var 94 % · keywest
cpu_saturation · server_metric · log_storage
23 min
High 5xx rate · api-prod
uptime · ratio > 5 %
4 min
Backup older than threshold · keywest
backup_check · db-prod-1
2 min
DB write latency p95 climbing · api-prod
postgres_plugin · 720 ms peak
1 min
Four pages. Three dashboards. One pager. Are these the same incident? Different ones? Which to start with? You're reading log lines while the page count grows.
With AI Triage incident · auto-grouped 02:31
P1 · keywest · disk-pressure cascade

Log rotation stalled at 02:14. Everything below is downstream.

Disk on /var reached 94 %, postgres started fsync-stalling, that's your p95 latency climb on api-prod, then 5xx propagated to upstream uptime probes. The backup-age alert is the same root: nightly dump can't complete with 6 % free.

Evidence the AI used
02:14:08 syslog logrotate exited 1 — “disk full”
02:21:42 postgres checkpoint sync 1842 ms (was 47 ms baseline)
02:27:11 nginx upstream timeout count ↑ 14×
02:30:00 backup pg_dump aborted at 73 % — “no space”
— Capabilities

Three modes of AI, one chain of trust.

Each mode answers a different question. None of them answer with vibes — every conclusion is anchored in evidence pulled from the same sources you'd read manually.

01 — Triage

Group, rank, summarise

Multiple firing alerts → one ranked incident. Severity grading from real impact (user-facing 5xx beats free-disk warning), not metric thresholds.

02 — Root cause

Ask why, get an answer

Natural-language query against logs, metrics, recent deploys, config diffs. The output cites which lines and which time-windows were used.

03 — Forensic

Time-travel after the fact

Replay fleet state at any timestamp. See what was running, what changed, what alerted in the half hour before things broke. The data already exists — we're building the UI that overlays it on a chosen window.

— AI Explain

Right where you already are.

AI Explain is a button on the page you're looking at — server, domain, incident, attack timeline. Modal opens, evidence is gathered, summary lands. No leaving context.

SERVER

Why is this host slow?

Status, recent changes, current saturation, plugin signals — synthesized in one sweep.

DOMAIN

Why is SSL flaky?

DNS chain, CDN posture, certificate origin/edge mismatch, monitor history — collated.

INCIDENT

What happened in this attack?

Post-attack analysis writes the summary you'd otherwise put together with grep and patience.

— Provider-agnostic

Bring your AI. We'll do the rest.

Any OpenAI-compatible endpoint works. Your key, your provider, your data plane. We don't hold a model hostage behind a paywall.

AAnthropic · Claude OOpenAI · GPT-4 / GPT-4o GGroq · Llama, Mixtral LOllama · self-hosted AAzure OpenAI · enterprise endpoint +Any OpenAI-compatible endpoint

Page once. Read once. Fix once.

Triage, root cause, forensic — same evidence, three modes.

Get early access All features