Turn your brain
into runbooks.
Runbook Studio composes your Ounie brain — process docs, incident notes, playbooks — into step-by-step SOPs your team actually runs. Every step cites its source and gets a role; then you start a run, check it off, and a “last verified” clock keeps it from going stale.
- On-call eng1. Freeze deploys, page the on-call
- Incident lead2. Confirm scope in the status board
- On-call eng3. Roll back the last release
- Comms4. Post the customer status note
- Incident lead5. Verify metrics recovered
- Incident lead6. File the postmortem doc
From tribal knowledge to a runnable procedure in three steps.
Point it at your brain(s)
Sign in with your Ounie account and pick the brain(s) that hold the know-how — process docs, incident notes, tool guides, onboarding material, policies. Blend up to five.
Name the procedure
Type what you want a runbook for — “handle a production outage”, “onboard a new engineer”, “close the monthly books”. Runbook Studio composes an ordered SOP from your material only: purpose, roles, and numbered steps, each with a checklist and a citation to the source page. Anything your brain doesn’t cover is left out, not fabricated.
Run it, check it off, keep it current
Start a run and tick each step off as the work happens — every run keeps its own state. Edit any wording free, regenerate for 5 credits when the process changes, and mark it reviewed to reset the “last verified” clock so it never quietly goes stale.
A procedure your team runs — not a wiki page they forget.
Each step is written ONLY from your brain — your real process docs, runbooks, and playbooks — and cites the page it came from. Then it becomes something you actually operate: start a run, check steps off, and get a “last verified” clock that flags an SOP the moment it’s overdue for review. That execution state is what a wiki can’t give you.
Every procedure that lives in someone's head.
The steps already exist across your docs. Runbook Studio composes them into a procedure, cites the source, hands your team a checklist to run, and keeps the whole thing current.
Incident runbooks
Turn your postmortems and on-call notes into a sev-1 runbook anyone can run at 3am: freeze, page, roll back, communicate, verify. Each step cited, each run checked off, so nothing gets skipped under pressure.
Employee onboarding
Your handbook and tooling docs become a first-week checklist per role — accounts, access, training, first tasks. Start a fresh run for each new hire and track exactly where they are.
Ops & deployment procedures
Release checklists, backup drills, month-end close, environment setup. Compose them from your engineering brain, assign the owner for each step, and keep a run history of every time it was executed.
Compliance controls & audits
Document the procedures your SOC 2 / ISO controls require, cited to your policy pages, with a “last verified” stamp that proves — and reminds you — they’re reviewed on schedule.
Field & service procedures
Install, maintenance, and safety procedures from your equipment and training docs — with tick-off checklists a technician runs on site and a review clock so the safety-critical ones never lapse.
Support & escalation playbooks
Refunds, escalations, outage comms — the repeatable customer procedures that live in someone’s head. Put them in a brain and hand your team a runbook that stays consistent as the team grows.
Generate runbooks over REST or MCP.
Every action — generate an SOP, list it, export it, start a run, verify it — is a REST endpoint and a native MCP tool. Point Claude, Cursor, or your Ounie AI Team at Runbook Studio and it can draft procedures grounded in your own Ounie brain, drawing your shared Ounie credits. One Ounie master key works across every Ounie app.
// Connect from any MCP host (Claude, Cursor, the AI SDK)
{
"mcpServers": {
"runbook-studio": {
"url": "https://sops.ounie.com/api/mcp",
"headers": { "Authorization": "Bearer sop_live_…" }
}
}
}
// …or the Ounie AI Team — the key rides the URL:
// https://sops.ounie.com/api/mcp?api_key=ounie_live_…
// Tool call → generate_sop (grounded in your brain)
{ "title": "Onboard a new engineer",
"brain_ids": ["…"] }
→ { "sop_id": "…", "steps": 9,
"grounded": true, "credits_spent": 5 }Pay per SOP. Run it forever.
Generating one SOP costs 5 Ounie credits (5¢), from the same wallet every Ounie product shares. If your brain doesn't cover the topic, you're not charged. And everything that makes it a runbook — starting runs, checking steps off, marking it reviewed, editing, and CSV/DOCX export — is free forever.
The questions we get first.
Stop losing the procedure when the person leaves.
The know-how is already in your brain. Runbook Studio turns it into an SOP your whole team can run — cited, checked off, and kept current.