ControlTheory Launches Dstl8 2.0, the AI SRE That Doesn't Need An Observability Platform
SALT LAKE CITY--( BUSINESS WIRE)--ControlTheory today launched Dstl8 2.0, its telemetry-native AI SRE, at KubeCon + CloudNativeCon North America. Dstl8 now extends Telemetry Distillation to metrics and traces in addition to logs, so it works from telemetry it distills itself rather than data borrowed from an observability platform. This release challenges a decade of conventional wisdom about why teams need observability at all.
For years, teams have bought observability the way they buy insurance: because the alternative feels risky, and because it is what has always been done. They pay to ingest, index, and retain every byte, then sample and drop data to keep the bill in check. Companies are paying real-time prices for an archive; at ControlTheory, we call that the Telemetry Tax.
AI SREs promised to change the equation, but most were built on top of that same platform. They investigate what it flags and reason over whatever survived the cost cuts. If nothing fires, they never look. That is what we call the Telemetry Trust Problem.
"If your AI SRE finds an issue, diagnoses it, and fixes it, all on telemetry it brings itself, it's fair to ask what your observability platform is for," said Bob Quillin, CEO and co-founder of ControlTheory. "For most teams, the honest answer is: less than they're paying for. Instead of following the herd and adding an AI SRE to observability, we built observability into our AI SRE."
The approach is already in production. At an enterprise fintech, Dstl8 resolved 328 incidents across 13 Kubernetes clusters in its first two months, without the team writing a single alert rule.
An AI SRE is only as good as the telemetry it's handed
Two-thirds of organizations hosting generative AI models now run some or all of that inference on Kubernetes, according to the 2026 CNCF Annual Cloud Native Survey. The same clusters now carry services, agents, LLM calls, and GPUs, and teams ship changes to all of them faster than ever.
One bad deploy can ripple through every layer at once. A bigger blast radius needs a wider net. With Telemetry Distillation across logs, metrics, traces, and events, Dstl8 reasons over sentiment, patterns, anomalies, and severity to find and fix problems that used to take several tools.
Key benefits of Dstl8
For GPU and AI cloud providers and their customers, that means a faster answer to the question asked most, "Is it your infrastructure or my code?", with the evidence to settle it, and a clear view of GPUs that are reserved but sitting idle.
Additional new features
"Most telemetry gets stored before anyone looks at it," said Eric Anderson, co-founder and CTO of ControlTheory. "Telemetry Distillation flips that order. Every log, metric, and trace is analyzed first, close to the source, and what we keep is chosen based on what we found. That's what lets Dstl8 show its work. And it looks ahead. 'Your disk is full' means you're already in trouble. 'Your disk will be full at 11 p.m.' gives you time to fix it."
Availability
Dstl8 2.0 is available today, with metrics and traces in preview. See it live at ControlTheory booth 188 (Hall 1, Solutions Showcase, Salt Palace) at KubeCon + CloudNativeCon North America in Salt Lake City, November 9-12. Start a 14-day free trial at dstl8.ai.
Related
About ControlTheory
Founded in 2024 by observability veterans from StackEngine (acquired by Oracle Cloud) and CopperEgg (acquired by Idera), ControlTheory builds Dstl8, the telemetry-native AI SRE. Built on Telemetry Distillation, Dstl8 analyzes logs, metrics, and traces close to the source, finds root cause with zero alert rules, and delivers the fix to Slack, Claude Code, Cursor, and Codex, so teams don't need a separate observability platform. ControlTheory also created Gonzo, the open-source OTLP terminal UI with 2,700+ GitHub stars. The company is based in Austin, Texas. Learn more at controltheory.com.