Compare
Production Operations: 6 options
6 options compared · 2 tutorial, 1 plugin, 1 hook, 1 runbook, 1 reference
Comparing 6 options
Production Operations — Day-two work: monitoring, on-call, backfills, deployments and capacity. The registry currently holds 6 resources: 2 tutorials, 1 plugin, 1 hook, 1 runbook, 1 reference.
Side by side
Every field below comes from the curated record — nothing is sponsored or ranked by payment:
| Resource | Type | Difficulty | Verification | Score |
|---|---|---|---|---|
| Runbook Runner | Plugin | beginner | community | 35.6 |
| Plan and execute a backfill that doesn't break production | Tutorial | intermediate | community | 34.15 |
| Production gotchas — silent failures and partial writes | Tutorial | intermediate | community | 34.15 |
| Production Write Confirmation | Hook | beginner | community | 33.6 |
| Pipeline failed | Runbook | beginner | community | 28.75 |
| Reading CI Failures Across Pipelines, Not One Build at a Time | Reference | — | community | 23.55 |
Trust breakdown
Verification mix: 6 community. No evidence gaps: every claim on file matches the record. Read how verification works — nothing here is independently audited yet, and the site says so everywhere it matters.
Security posture
Flagged entries: Runbook Runner (1), Pipeline failed (4). Flags record declared capabilities (credentials, write access, network calls) — they are facts to review, not verdicts. Every entry also passes the 30-rule static trust scan; findings print on each detail page.
How to choose
How to choose: start with Runbook Runner, Production Write Confirmation for the gentlest on-ramp; Weight verification and evidence over score when two entries are close, and check the last-verified date on each page — the registry re-checks every 180 days.