The RatioA weekly newsletter on reliability economics | | |
|
The Number
64%
Of the 47 services in the benchmark where AI-assisted tools apply, 30 say it is too early to tell whether production stability changed.
103 services answered. 56 marked the question not applicable and are excluded here. Of the other 47, 30 said too early to tell, and 17 gave a clear answer: 5 improved, 8 saw no change, 4 got worse.
Neutral
Most teams adopted these tools before they could measure what the tools did to stability. You cannot price a risk you have not instrumented.
They are underwriting the outcome blind, like an insurer writing flood policies with no loss history. The 17 with an answer do not settle it either. Most saw no change, and the rest nearly cancel out on a sample too small to call.
So the first deliverable of an AI rollout is not the tool. It is the before-and-after stability baseline that tells you which group you landed in.
| Nearly two in three services where AI-assisted tools apply cannot yet say whether those tools made production more stable or less. |
|
|
This Week in Reliability
The agent is cheap. Trusting it isn't.
Three major vendors shipped production AI SRE agents this week while practitioners question investigation reliability and deployment safety. The gap between vendor promises and enterprise reality is widening—teams need audit trails, sandbox limits, and human override before they'll trust autonomous remediation in regulated environments.
|
Pragmatic Engineer · Primary evidence—practitioner deep-dive Examines three AI SRE startups' approaches to autonomous incident investigation in 2026, including Resolve's three-agent system with structurally independent verifier roles to prevent self-confirmation bias. Details the high-level workflow patterns all three vendors follow for investigation automation. Prevention The verifier-as-structural-check is the first honest engineering answer to the 'can we trust this?' question. Most AI SRE pitches skip audit architecture entirely—Resolve's team ships with skepticism built in, which makes the economics conversation possible instead of theoretical. | Independent verifier agents turn trust into architecture. |
|
StackGen · Enterprise deployment reality check StackGen's Vishwajeet Kumar discusses technical challenges of deploying AI SRE in enterprises, focusing on infrastructure compatibility, policy constraints, and integration with existing toolchains. Addresses the gap between vendor demos and production deployment requirements. Neutral Enterprise reality means audit logs, change windows, and compliance checkpoints—none of which appear in vendor demos. The real cost isn't the agent license, it's the six months of policy integration and the shadow team verifying every autonomous action until trust accumulates through evidence. | Enterprise deployment costs dwarf the agent subscription fee. |
|
Yahoo Finance / PagerDuty · Vendor launch—market signal PagerDuty launched Paige, an AI SRE agent integrated into their new PD Reliability Platform, combining AI-assisted detection, triage, resolution, and prevention capabilities. Firefighting PagerDuty's agent launch signals the on-call market recognizes autonomous ops as table stakes for 2026 renewals—expect pressure on SRE budgets to justify agent spend versus incremental headcount. | On-call platforms now ship with agent expectations baked in. |
|
StackGen · Agent safety investment signal StackGen acquired Shipyard to add production-like ephemeral environments for testing AI-generated infrastructure changes before deployment, addressing the safety gap in autonomous operations. Prevention Ephemeral test environments are the missing safety rail—agents that can't rehearse changes in prod-like sandboxes shouldn't touch production, and this acquisition admits it. | Agent safety requires rehearsal infrastructure, not just logs. |
|
Techgenyz · Adjacent—SRE practice baseline for agents Notes that by 2026 traditional static-threshold alerting has been largely replaced by error budget burn rate alerting, which fires when error budgets are consumed faster than projected to catch real incidents earlier. Neutral Burn rate alerting is now table stakes, but it only works if someone acts on the alert—agents accelerate response but don't fix the underlying budget discipline problem. | Burn rate alerts are standard; response automation isn't. |
|
Lorin Hochstein · Counter-signal—automation amplifies hidden risk Analyzes the eMudhra PKI incident where eight TLS intermediate certificate authorities had cryptographically weak keys that allowed trivial private key reconstruction from public keys, representing a fundamental security failure. Firefighting AI agents inheriting access to weak PKI infrastructure inherit invisible catastrophic risk—autonomous operations accelerate exploitation timelines for structural vulnerabilities like this one. | Agents inherit structural risks humans haven't mapped yet. |
|
SRE Weekly · Practitioner curation—safety limits Curated SRE news and links from the week, including incident.io's note that 'your agent is only as useful as the tools it can reach, and only as safe as the limits you set' with a focus on building safe agent extensions. Neutral The extension boundary is where agent safety either holds or breaks—most teams are bolting on tools without asking what blast radius each new skill creates. | Agent skills expand faster than safety boundaries do. |
|
|
The Challenger — Comment of the Week
What's the right SRE-to-developer ratio?
In a Reddit discussion on r/sre, one engineer described a team of 8 SREs supporting 250 developers.
They owned everything: on-call, escalations, observability, release engineering, and production issues.
The engineer described it as unsustainable and eventually left.
But the interesting part isn't the 250:8 ratio. It's what those 8 SREs were expected to do.
We keep debating the ideal SRE-to-dev ratio. 1:5? 1:10? 1:20?
But headcount alone doesn't tell you whether reliability is improving.
A 1:5 team with SLO-driven decisions, error budgets, and time for prevention can outperform a 1:4 team stuck handling L3 escalations.
One is engineering reliability. The other is a help desk with better job titles.
Headcount ratio measures staffing. Prevention-to-firefighting ratio tells you how that capacity is being used.
Before asking how many SREs you need, ask how much of their time actually prevents the next incident.
Source: https://www.reddit.com/r/sre/comments/m711id/what_is_the_ratio_of_engineerssre_at_your_company/
Neutral
| Headcount ratio hides the real constraint. |
| Should this replace the favorite? | |
|
|
The Ratio is a weekly newsletter by Florian Hoeppner. Early edition, you are one of the first.
Forwarded this? Get The Ratio in your inbox every week.
|
Take the assessment → reliabilityeconomics.com/benchmark Reply to this email with your take.
How this newsletter gets better: Every link is tracked and every vote is counted. Sections that get a down vote get replaced. Topics that get an up vote stay. No personal data is stored — just click and vote counts per section. Your feedback shapes the next edition.
|
|
|