DSTL8 · THE TELEMETRY-NATIVE AI SRE

The AI SRE That Doesn’t Need an Observability Platform.

Dstl8 brings its own telemetry. Telemetry Distillation reads your telemetry at the source, Möbius reasons over it, and the fix lands in Slack, Claude Code, Cursor, or Codex. Source to fix, nothing to assemble.

328 incidents resolved · Zero alert rules
13 Kubernetes clusters · Enterprise fintech, first two months.

Dstl8 AI Code Debug Runtime Incidents

Works with your stack

Runtime platforms and AI coding tools — connected in minutes. See all integrations →

THE TELEMETRY PROBLEM

An AI SRE is only as good as the telemetry it’s handed.

01

The Telemetry Tax

You ship, index, and retain everything to find the few lines that matter. AI-speed engineering multiplies the volume, and the bill.

# monthly telemetry
ingested: everything
indexed: everything
read by anyone: almost none
→ you pay for all of it

02

The Telemetry Trust Problem

Most AI SREs sit on someone else’s data plane. They reason over whatever survived sampling and indexing, and can’t see what was dropped.

# ai sre investigation
source: vendor index
sampled: yes
dropped lines: unknown
→ confident answer, with partial evidence

03

Rules Can’t Keep Pace

More code, shipped faster, by more agents. Alert rules catch the failures you already know. The expensive ones never had a rule.

# deploy 14:07 · all green
alert rules fired: 0
retry volume: 8x baseline
customer tickets: 3
→ nobody wrote a rule for this

// See how Dstl8 brings its own telemetry.

BUILT ON TELEMETRY DISTILLATION

04

Knowledge graph

Every resolved incident becomes institutional memory. What one service teaches, every service keeps.

03

FEEDBACK LAYER

Root cause, evidence, and the fix, delivered to Slack, Claude Code, Cursor, or Codex. Fixes land where work happens, not in a ticket queue.

02

Möbius reasoning

Our own fine-tuned model investigates every incident, reasoning over distilled signal, never the raw firehose.

01

TELEMETRY DISTILLATION

Reads the content of all your telemetry close to the source: sentiment, patterns, anomalies, severity. Signal before spend.

Distilled at the source. Reasoned in Dstl8. Delivered where you work. Remembered.

14 days free · Full platform access

Start Here

See what’s actually happening.

Connect your deployment chain. Surface emergent patterns. Get root cause analysis with fix recommendations — right in your editor.

↻ Intelligence that compounds — every runtime signal makes the next one sharper.

14-day free trial
5-minute setup
No credit card required
Full platform access

Dstl8 — Supabase runtime analysis

Open Source

Not ready for Dstl8? Start with Gonzo.

Free, open source log analysis TUI. Real-time charts, pattern detection, AI-powered insights — right in your terminal. No account, no config.

brew install gonzo

2625 stars

ACTIVE ATTACK

“Active path traversal and RCE attack attempts detected on customer-portal”

CODE REGRESSION

“TypeError cascade in catalog_event affecting 4 services”

CASCADING IMPACT

“Potential downstream effect: Google CSE rate-limiting causing Vercel anomalies”

EXTERNAL DEPENDENCY

“OpenAI API credits exhausted (429) impacting data-enrichment pipeline”

ANOMALY DETECTION

“Host error spikes on two production nodes with z-scores 139.3 and 120.8”

RATE LIMIT

“Service hit Stripe API rate limit — 4,995 errors in 2 hours”

Why DSTL8

Not an observability platform with an AI SRE bolted on.

DATA PLANE

TELEMETRY TAX

What the AI sees

Detection

Where it lands

Pricing

Over time

Observability platform + AI SRE

Required, paid for separately

High: Ingest, index, retain all.

Whatever survived sampling

Alert rules you write and tune

Another dashboard

Metered by GB or investigation

Starts from zero each incident

DSTL8

Not needed. Built-in.

None: no per-GB pricing

Every signal, distilled

Zero alert rules

Claude Code, Cursor, Codex

Unlimited incidents

Knowledge graph compounds

Install & Configure Dstl8 in Under 2 Minutes.

Try the Dstl8 CLI and TUI for continuous runtime feedback. Install it, add sources, connect the MCP server into Claude Code, and more.

brew install control-theory/dstl8/dstl8
dstl8 setup
npx dstl8
nix run github:control-theory/dstl8

Quick Start

# 1. Install the CLI
brew install control-theory/dstl8/dstl8

# 2. Create a Dstl8 account (or `dstl8 login` if you already have one)
dstl8 setup

# 3. Add a source so logs flow in
dstl8 sources add vercel

# 4. Connect your AI agent, auto-detects MCP-compatible clients on your machine and configures them
dstl8 install --all
dstl8 install claude-code

Add Sources

# Add Sources

dstl8 sources add kubernetes
dstl8 sources add cloudwatch
dstl8 sources add vercel
dstl8 sources add supabase
dstl8 sources add otlp
dstl8 sources add github

See Dstl8 in Action

Your first root cause, in minutes.

// 14 days free · No credit card · Setup in minutes