The Ratio
A weekly newsletter on reliability economics
The Number
2 of 107
Only 2 of 107 organizations have SLOs that are central to release and investment decisions — the rest either have no SLOs or treat them as reporting artifacts.
107 organizations reported SLO maturity. 29 have none. 59 have SLOs that don't influence decisions. 14 influence some decisions. Only 2 have SLOs central to release and investment choices.
A decade of conference talks, blog posts, and SLO evangelism. The benchmark says almost none of it landed. 2 out of 107. That's the conversion rate on an entire industry movement.
SLOs without decisions attached to them are compliance artifacts. Paperwork. Like a building inspector who files reports but never stops construction, the assessment exists, the consequence doesn't. 88 organizations either skipped SLOs entirely or built ones that change nothing about how software ships or where money goes.
The first group, the 29 with no SLOs, at least isn't pretending. The second group, the 59 with SLOs that influence nothing, has the overhead without the outcome. That's worse.
88 of 107 organizations have SLOs that either don't exist or don't influence a single decision.
This Week in Reliability
Monitoring Cost Reckoning
The observability vendor pricing model is breaking under AI workload scale. Teams are forced to choose between visibility and budget—or build their own stack.
Deep Reads
Cloud Monitoring Costs 2026: Vendor-Neutral Pricing Intelligence
MonitoringCost.com · Primary evidence
Independent site comparing Datadog, New Relic, Grafana Cloud, Dynatrace, Splunk, and Elastic on identical scenarios. Claims most teams overpay by 30-60% and pricing ranges from $0 to $200k/month.
The fact that vendor-neutral monitoring price comparison is now a standalone product tells you everything about the state of observability economics. When teams need a calculator before they can instrument, the prevention-vs-cost curve has inverted.
Pricing opacity has become a reliability tax.
Free Cloud Monitoring Tools 2026: Real Free Tiers Reviewed
MonitoringCost.com · Primary evidence
Describes the 2026 open-source stack: OpenTelemetry for collection, Prometheus/Loki/Tempo/Pyroscope for storage, Grafana for visualization—all permissive licenses with no per-seat or volume fees.
The rise of the OTel-native self-hosted stack is not ideological—it's economic self-defense. Teams are choosing operational complexity over vendor lock-in because the lock-in cost now exceeds the operational burden.
Self-hosting is the new cost optimization.
APM Pricing 2026: Datadog vs New Relic vs Dynatrace vs AppDynamics
MonitoringCost.com · Data point
Compares APM pricing across major vendors, noting Splunk bundles APM with infrastructure monitoring starting at $60/host/month.
Bundled pricing looks cheaper until you realize you're paying for infrastructure monitoring you don't need—vendor arbitrage masquerading as value.
Bundle inflation hides per-feature unit economics.
The reliability versus cost trade-off that keeps engineers awake
DEV Community · Practitioner signal
Community post discussing the architectural tension between reliability investment and cost control.
When community engineers are writing about the reliability-cost tradeoff as the thing that 'keeps them awake,' the U-curve has become the daily operating constraint.
Reliability is now a budget negotiation, not engineering.
Site Reliability Engineer: 7 Practical SRE Skills
Cademix · Skills realignment
Career guide advising SREs to focus on multi-cloud portability, avoid vendor lock-in, and optimize resource usage and cost alongside platform knowledge.
When SRE career advice now includes 'avoid vendor lock-in' and 'optimize cost,' the skills have shifted from reliability to reliability economics.
SRE now means 'spending reliability engineer.'
Site Reliability Engineering: A Complete Guide
Moon Technolabs · Adjacent signal
SRE guide covering SLIs, SLOs, error budgets, MTTR, and proactive checks on certificate expiry, memory growth, and database capacity to reduce preventable incidents.
The guide treats SLOs and error budgets as prevention tools, but without cost data they're just qualitative targets—prevention theater without the ROI proof.
SLOs without cost tracking are just vibes.
Run cost-effective, always-on agents to monitor your environment: the engineering behind Watchers
Grafana Labs Blog · Vendor response
Grafana introduces 'Watchers'—cost-effective always-on agents for monitoring, positioned as an alternative to swarm-all-agents-everywhere AI monitoring that drives astronomical bills.
Vendor-built cost optimization is the canary—when Grafana has to build tooling to prevent their own platform from bankrupting customers, the pricing model is structurally broken.
Vendor cost controls admit pricing is unsustainable.
The Crowd Favorite
- One (Remastered) — Metallica ↗ — A runbook without a rollback path leaves on-call with no exit. That's a design failure, not an operational one.
- Even Flow — Pearl Jam ↗ — The unrepeatable studio fix is your hero-action: decisive, undocumented, invisible to the next engineer paged at 3 a.m.
- Synchronicity II — The Police ↗ — "Unrelated" services fail simultaneously at peak load because they share a hidden dependency, not because the incidents coincidentally overlap.
- Radio Ga Ga — Queen ↗ — When every threshold fires, the revenue-impacting signal drowns in noise. Alert fatigue is a pipeline architecture problem, not an ops discipline problem.
- Times Like These — Foo Fighters ↗ — A DR plan that lives in one engineer's head doesn't survive attrition. Test the rebuild, not just the backup.
No rollback, no runbook, no handoff.
The Challenger — Industry Shift
Platform engineering absorbed SRE's toil-reduction mandate. The 2024 DORA report shows high-performing organizations centralizing reliability tooling in internal developer platforms, not in SRE teams.
The analogy is hospital sterile processing: nurses once managed their own instrument supply, consuming clinical hours. Centralized departments restored that capacity for patient care. The reliability parallel is direct. When platform teams own the paved road, SRE capacity shifts from infrastructure babysitting to availability architecture.
Reliability is centralizing. Teams that miss this will fund the wrong headcount for the next three years.
Reliability is centralizing. Fund the right team.
The Ratio is a weekly newsletter by Florian Hoeppner.
Take the assessment → reliabilityeconomics.com/benchmark
Reply to this email with your take.