Runbooks that
actually run.
Your wiki says “run this query” but doesn't actually run it. Caret creates living runbooks — executable docs where code runs inline and procedures stay current.
Works offline · Version history · Access control
Sound familiar?
Documentation debt is real. Here's what you're dealing with.
Runbooks that nobody trusts
The wiki says to run this command. But is it still valid? Last updated: 18 months ago. Good luck.
Knowledge trapped in senior engineers' heads
New team member asks how to debug X. Senior engineer shares screen, types magic commands. Nothing documented.
2am incidents with outdated docs
Pager goes off. You follow the runbook. Step 3 doesn't work anymore. Now you're debugging the runbook AND the incident.
Docs and code always out of sync
README says one thing, code does another. Someone updated the script but forgot the wiki.
Documentation that can't get stale
Because the code IS the documentation.
Wiki page says:
“1. SSH into prod-db-01”
“2. Run: SELECT * FROM connections...”
“3. Kill connections with: SELECT pg_terminate...”
❓ Is this the right server name?
❓ Is this query syntax still valid?
❓ Did we change the threshold?
❓ Copy-paste errors in commands
SELECT count(*) FROM pg_stat_activity; Current connections: 95/100 ⚠️
Found 3 idle connections: ┌──────┬────────────┬─────────┐ │ PID │ Duration │ State │ ├──────┼────────────┼─────────┤ │ 1234 │ 00:12:34 │ idle │ │ 1235 │ 00:08:21 │ idle │ │ 1236 │ 00:06:45 │ idle │ └──────┴────────────┴─────────┘
Terminated 3 connections. Current connections: 92/100 ✓
Build runbooks engineers use
Document with code
Write context in markdown. Add executable code blocks. Readers understand the “why” and run the “how”.
Test by using
Every time someone uses the runbook, they're testing it. If something breaks, you know immediately.
Share & collaborate
Organize by service or incident type. Search across all procedures. Version history for accountability.
Start with proven procedures
Pre-built runbooks for common scenarios. Customize for your infrastructure.
Built for infrastructure and reliability
Everything platform teams need for operational excellence.
Executable Documentation
Python, SQL, shell commands — all executable directly in the document. No copy-paste to terminal.
Database Connections
Connect to PostgreSQL, MySQL, MongoDB, Redis. Read-only mode for safety. Results as formatted tables.
Offline-First
Incident at 2am and VPN is flaky? Your runbooks are cached locally. Always accessible.
Version History
See who updated what and when. Roll back if changes break things. Compare versions side-by-side.
Variables & Parameters
Define variables at the top, reference throughout. Change one value, every command updates.
Access Control
Restrict dangerous runbooks to specific roles. Audit log shows who ran what and when.
Platform teams trust Caret
Our MTTR dropped 40% after moving runbooks to Caret. On-call engineers stopped wasting time on 'does this command still work?'
New engineers used to take 2 weeks to get comfortable with on-call. With executable runbooks, they're confident after day 3.
I used to dread writing docs because they'd be outdated in a month. Now our docs are always current because people run them.
Build documentation your team will actually use.
Join platform teams shipping runbooks that work.
Free plan available · Upgrade anytime