Keep incident-response runbooks as markdown in your repo. mustr renders them, executes the steps, and records what happened, from your terminal or a local dashboard.
No agents to deploy, no YAML to learn. mustr reads the markdown you already have.
Headings become steps. Fenced code blocks become commands. Commit it next to your service.
mustr walks each step, shows you the command, and waits for your go-ahead before executing.
Every step, operator, and outcome is logged locally, or streamed to Point for a central audit trail.
The runbook is readable in GitHub, in your editor, and in an outage. No proprietary format to migrate to.
Approve each command before it runs, or pass --yes for the steps you trust. Skip, retry, or jump mid-run.
See exactly what would execute against which environment before a single command touches production.
Runbooks change through pull requests. Diffs, blame, and approvals you already have, for free.
One binary on your machine. Nothing to deploy, no server to keep up while you are trying to fix a server.
Add one line of config and every local run streams to your hosted audit log. Nothing else changes.
mustr serve opens a dashboard on localhost. Rendered markdown on the left, live execution log on the right. Click a step to run it.
Use when api-us-east-2 p99 latency exceeds 2s for 5+ minutes.
Point is the hosted audit log for mustr. Every command, every operator, every outcome. Centralized, searchable, and ready for your next audit.
Explore Point →