Blog.
Long-form thinking on incident governance, automation safety, observability engineering, and the culture that makes reliable systems possible.
Why EAL is the only automation metric that matters for enterprise incident response
Most incident automation fails not because the automation is wrong, but because there's no principled way to bound it. EAL solves this by making the automation ceiling a governed, auditable policy decision — not a judgement call made at 3am under pressure.
How to author your first Scrubbe playbook — from pattern identification to production deployment
A step-by-step walkthrough — triggerConditions with confidence weights, branching investigationSteps, remediationOptions, blast radius hints, and how to set your automationStage correctly. Includes a real CrashLoopBackOff example with full JSONB config.
Ezra Code Engine now in GA — diff suggestions, auto PR, CI failure comparison
Ezra now suggests targeted code diffs against the file it identifies as root cause. Diffs presented as unified patches against your actual repo. One-click PR creation. CI comparison across last 5 passing runs.
More Articles
How Fintrax cut MTTR by 79% in 8 weeks on the Govern plan
Fintrax processes 2M+ payments daily. 90% of incidents were resolved manually despite having Datadog and PagerDuty. Here's how they built their first governed playbook library and what they learned.
Blast radius, not severity: the metric that should gate automated remediation
Severity is a snapshot. Blast radius is a graph computation. Using severity alone to gate automation leads to systematic over-permission — and how DIRECT / CASCADE / INDIRECT node classification fixes it.
Event-driven policy evaluation at scale — lessons from building Scrubbe's core loop
How we designed the Event → Evaluation → Decision → Action → Audit loop to be deterministic, replayable, and auditable. What we got wrong in the first two iterations before we got it right.
Fortnightly. No filler.
Deep dives, governance patterns, connector releases, and community highlights. Engineers at Stripe, Shopify, and Cloudflare subscribe.
Cookie preferences
We use essential cookies to keep Scrubbe secure and functional. You can choose whether to allow analytics, preferences, and marketing cookies, and update your choices at any time.
Essential cookies
Required for security, session continuity, consent state, and core site functionality. These are always on.
Analytics cookies
Help us understand usage patterns so we can improve product pages, onboarding paths, and documentation quality.
Preference cookies
Remember selected settings such as region, UI preferences, and previously chosen site options.
Marketing cookies
Enable campaign measurement and more relevant follow-up communications across trusted channels.
Your choices are stored locally in this browser and can be updated at any time from the cookie settings button.