A working incident-response sandbox

Turn alert noise into a safe, explainable response.

On-call engineers lose time joining scattered evidence—and an AI-generated fix can make an outage worse. Sentinel assembles the evidence, proposes one bounded action, and lets deterministic policy keep the human in control.

Real database records Real queue processing Zero production mutations
INCIDENT IN PROGRESSpayments-api / SEV1
Observed signalError rate jumped after releaseLogs + metrics + deploy history correlated
AI proposalRollback deployment
Java guardrailDRY-RUN ONLY
✓ Evidence grounded✓ Audit event written

LIVE DATABASE SNAPSHOT

This is not a static mockup.

These totals are queried from PostgreSQL when this page loads.
services
metric samples
log events
audit events

THE PROBLEM, MADE CONCRETE

One alert. Five accountable decisions.

Follow the same path a real on-call engineer would inspect during an outage.
01

Ingest

Accept and fingerprint the alert

02

Correlate

Join deploys, metrics, logs and runbooks

03

Propose

AI suggests; it never authorizes

04

Guard

Java policy approves, blocks or escalates

05

Record

Append the outcome to an immutable ledger

WHO USES IT?

Built for the moment when every minute matters.

On-call engineer

Gets one evidence-backed incident instead of hunting across four tools.

SRE approver

Sees the proposed action, risk, grounding and audit history before deciding.

Platform team

Defines the deterministic policy boundary that neither a user nor a model can bypass.

READY TO SEE THE BACKEND MOVE?

Run a safe incident yourself.

Choose one server-owned scenario. Sentinel will create fresh records, publish durable work, investigate it, apply the safety gate and return the persisted result.

0 visitor-triggered runs recorded so far