Live demo
A real Kubernetes cluster.
Deliberately broken every few minutes.
Reflex Runtime is watching demo-payments-api on a real single-node k3s cluster. Every 4–9 minutes the service starts returning 5xx. Reflex detects the SLO breach, posts a Slack approval, and restarts the deployment. The state below is live — the events, the counter, the countdown.
Service status
Breaching
payments-api
Recovery in progress
active breach
Reflex is responding
Total remediations
2,975
Last: 32m ago
What this looks like for your team
Reflex has caught 2,975 breaches on this service.
- Avg breach → recovery
- 140s
- Overnight (12am–6am ET)
- 26%
- Est. on-call hours saved
- 198.3
Hours-saved uses a conservative 4 min/page estimate. Real on-call interrupts — page → diagnose → fix → cool down — typically run 15–30 min.
Incident log
Live feed of breach and recovery events from the demo cluster.
- Demo VM unreachable — paused1m ago
- Demo VM unreachable — paused2m ago
- Demo VM unreachable — paused5m ago
- Demo VM unreachable — paused16m ago
- Demo VM unreachable — paused17m ago
- Demo VM unreachable — paused22m ago
- Breach detected · error rate 80%25m ago
- Demo VM unreachable — paused26m ago
- Recovered · restart (auto) · 120s32m ago
- Breach detected · error rate 69%34m ago
Reflex is acting now
The exact Slack message your on-call would receive.
#reflex-demo·Slack
R
ReflexAPPjust now
SLO breach detected
demo-payments-api error rate at 80% — exceeds 5% threshold over 5m.
Pattern: error_spike
Action taken: restart deployment/demo-payments-api
Trust mode: auto
Executed by Reflex
Breach cycles randomized 4–9 minutes · All remediations are real · This is a real Kubernetes cluster running Reflex Runtime.