Showcase

See what OpenSRE looks like in practice — install, investigate, and share.

Want to know what OpenSRE actually looks like when you run it? Here’s a walkthrough of a first install, the files you get after an investigation, and a way to put your own demos on the page.

Watch a first run

Install, set things up, and throw a sample alert at it. Most people are done in under ten minutes.

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

Prefer step-by-step with platform-specific GIFs? Start at the Quickstart.

Full quickstart

Install, onboard, and run the sample alert — with screenshots for macOS, Linux, and Windows.

Jump to the GIFs

Skip straight to the install and onboard recordings.

What you get after a run

When an investigation finishes, OpenSRE drops a few files you can open in any editor:

File	What’s inside
problem.md	What it thought the incident was about, and what looked impacted
theory/hypothesis_*.md	Each idea it tested, with the evidence for and against
report.md	The final write-up — likely cause, how sure it is, and what to try next

Need one file for a script or pipeline instead?

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

You can also send the summary to Slack. Here’s what that looks like:

More on the full flow, slash commands, and delivery options: Investigations overview.

Put it through CloudOpsBench

Curious how OpenSRE stacks up? CloudOpsBench is a 452-scenario Kubernetes RCA suite — you can run OpenSRE against it and compare to published LLM-only baselines.

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

Setup, integrity checks, and cost notes live on the CloudOpsBench page.

Show us what you built

Got a demo, a runbook, or a post-mortem that used OpenSRE?

1. Post in GitHub Discussions with the Showcase tag — include the commands you ran, which tools were connected, and redacted output if you can.
2. Join the bi-weekly giveaway when you share something — there’s OpenSRE swag in the mix.