Runbook Assembly Platform Overview

A product-level walkthrough for prospects, customers, and internal demos.
Go to Runbooks Guide FAQ

What it is

Runbook Assembly is a secure operations workspace for software engineering and DevOps teams to design, execute, and govern deployment and rollout procedures with clear ownership, auditability, and collaboration.

Who it serves

  • Engineering teams running deployments, migrations, and release cutovers.
  • SRE / DevOps teams coordinating change windows with approvals and rollback plans.
  • QA, Release Managers, and Support teams that need shared execution visibility.

Core capabilities

Runbook authoring
  • Flexible table structure with rich column types (Text, Date, Enum, Jira Key, Auto Increment).
  • Topic Rows for sectioning by team or phase (Pre-checks, QA, DevOps, Rollback).
  • Template system for repeatable operational patterns.
Import and acceleration
  • Spreadsheet import (CSV/TSV) with preview, append/replace, and mapping support.
  • Document import (PDF/DOCX/HTML/paste) with preview and optional field extraction.
  • Rollback last import to safely recover from mistaken replacements.
Execution + governance
  • Finalize runbooks, rows, or columns to enforce immutability where needed.
  • Execution sessions, assigned steps, approvals, and timeline/audit trails.
  • Feature gating for plan-aware controls managed by Owner Admin.
Sharing + security
  • Share with users, teams, or key-based access (view/edit permissions).
  • Organization tenancy with org-level boundaries and administration.
  • 2FA, optional Okta SSO, audit logs, and Owner Admin controls.

Business value

  • Reduces deployment risk with repeatable, reviewable, and enforceable workflows.
  • Shortens onboarding by giving teams structured operational playbooks.
  • Improves compliance posture with clear evidence of who changed what and when.
  • Creates a reusable runbook/template library that compounds team velocity over time.

Typical workflow

  1. Create or import a runbook.
  2. Assign ownership and permissions.
  3. Execute with approvals and live updates.
  4. Capture outcomes and reuse as templates.

Demo scripts (5 / 15 / 30 min)

A ready-to-use sales/demo script is available in: docs/SALES_DEMO_SCRIPT.md

Use the 5-minute flow for executive previews, 15-minute for evaluation calls, and 30-minute for technical deep dives.