Showcase

Concrete examples of what OpenSRE looks like in practice — from install through root-cause analysis.

Quickstart walkthrough

Install, onboard, and run your first investigation in under ten minutes.

Step-by-step install, onboarding, and sample alert investigation.

GIF walkthroughs for macOS, Linux, and Windows.

Typical first-run commands:

curl -fsSL https://install.opensre.com | bash
opensre onboard
opensre investigate -i tests/e2e/kubernetes/fixtures/datadog_k8s_alert.json

A completed local run writes structured RCA artifacts you can open in any editor:

File	What it contains
`problem.md`	Incident framing, impacted components, initial hypothesis
`theory/hypothesis_*.md`	Each hypothesis tested during the run, with supporting evidence
`report.md`	Final root-cause summary, confidence, and recommended next steps

Export a single JSON file for automation:

opensre investigate -i <alert-file> --output ./rca.json

See Investigations overview for the full workflow, slash commands, and Slack delivery.

Run OpenSRE against the 452-scenario CloudOpsBench Kubernetes RCA corpus and compare to published LLM-alone baselines.

uv run python -m tests.benchmarks._framework.cli run \
  --config tests/benchmarks/cloudopsbench/config.yaml \
  --models claude-sonnet-4-20250514

See CloudOpsBench benchmark for configuration, integrity guards, and cost tracking. Have a demo, runbook, or incident post-mortem powered by OpenSRE?

Open a GitHub Discussion with the tag Showcase — include commands, integrations used, and (if possible) redacted output.
Join the bi-weekly giveaway for a chance to win OpenSRE swag when you share what you built.