Your Pod Crashed. Dstl8 Tells You Why.

Pipe kubectl logs or your cluster’s OTLP into Dstl8 and get root cause — CrashLoopBackOff, OOMKilled, the silent restart — cited to the exact log line, across every namespace.

Start your free trial →

14-day free trial · No credit card · Setup in 5 minutes

★ 2,625 on GitHubbrew install control-theory/dstl8/dstl8Built on OpenTelemetryWorks with Claude Code, Cursor & Codex

Click through it yourself — watch Dstl8 detect a runtime issue and fix the code. No signup required.

Kubernetes tells you what failed, not why.

kubectl logs won’t say why

The pod restarted, but the logs scroll past faster than you can read and the reason is three crashes back.

Millions of lines across namespaces

The failure is in there somewhere — across pods, namespaces, and replicas. You don’t have time to grep all of it.

Everything’s red, nothing says what started it

CrashLoopBackOff, OOMKilled, a cascading failure — the dashboard shows the symptoms but not the first domino.

Root cause in three steps.

1 · Pipe in your cluster logs

kubectl logs -f | dstl8, work alongside k9s or Stern, or point your cluster’s OTLP collector at Dstl8. No agents to deploy.

2 · Möbius AI distills the noise

Continuous distillation turns millions of pod and namespace log lines into the handful of patterns, regressions, and anomalies that actually matter.

3 · Get root cause, cited

Why the pod crashed — OOMKilled, a bad config, a failing dependency — delivered to your terminal or Slack, cited to the exact log line.

Inside Dstl8 — service health, pod incidents, log patterns, and the root cause Möbius surfaces.

“brew install, pointed it at our K8s cluster, and Möbius was answering why is this service degrading in 90 seconds. Felt like cheating.”
— Platform Engineer, Series B AI infrastructure startup
Start debugging in 5 minutes →

14-day free trial · No credit card · Setup in 5 minutes

Before you start.

Does it work with kubectl, k9s, and Stern?

Yes. Pipe kubectl logs straight into Dstl8, run it alongside k9s or Stern, or send your cluster’s OTLP. It fits the CLI workflow you already use.

Do I need a credit card to start?

No. The 14-day free trial gives you full platform access with no credit card required.

Does it work across multiple namespaces?

Yes. Dstl8 analyzes log streams across pods, namespaces, and replicas, and surfaces the pattern behind the failure wherever it started.

Is there a free, open-source option?

Yes. Gonzo is our MIT-licensed terminal log analysis tool — pipe kubectl logs in with brew install gonzo, no account needed. Dstl8 adds continuous analysis and Möbius AI root cause.

How is this different from Datadog?

Dstl8 distills signal at the source instead of charging you to ingest everything, and Möbius AI hands you root cause cited to the log line instead of a dashboard to interpret yourself.

Find out why the pod died.

Free 14-day trial. No credit card. Full platform access.

Start your free trial →

14-day free trial · No credit card · Setup in 5 minutes

Find out why the pod crashed — free for 14 days.Start free trial