Claros Protocol

Static runbooks fail when it matters most.

Procedures stored as documents get skipped, shortcut, and followed incorrectly. Protocol turns them into executable workflows with verification checkpoints, approval gates, and automatic audit trails — generating compliance evidence as a byproduct of doing the work.

Protocol
94
score
12
active
3
flagged
Screenshot coming soon

Your procedures exist. Nobody follows them correctly.

The deployment runbook says "verify the health check passes before proceeding." The operator skips that step because they've done this fifty times and it always passes. This time it doesn't. The incident takes three hours to resolve.

The onboarding checklist has 40 items. The new hire checks them off in bulk at the end of the day. Two critical security steps were missed. Nobody notices until the access audit three months later.

Static documents can't enforce their own steps. They can't verify that critical actions happened. They can't generate evidence that a compliance auditor will accept. Protocol can.

Step by step

How Protocol works

01

Author the procedure

Write procedures with ordered steps. Each step gets a verification type: checkbox (simple confirmation), text-input (requires evidence — a URL, a screenshot description, a test result), or approval (requires a second person to sign off). AI-assisted authoring generates complete drafts from a natural-language description of what the procedure should accomplish.

02

Publish and version

Published runbooks are immutable. Edits create new versions. Previous versions remain accessible. Rollback is supported. This means the procedure someone followed last Tuesday is exactly the procedure you can audit today.

03

Execute with verification

Operators advance through steps with evidence capture at each checkpoint. Approval-type steps enforce a second-person gate — no self-approval. Conditional branching supports non-linear flows. Every action, timestamp, and piece of evidence is recorded.

04

AI post-run analysis

After execution, AI analyses the run: estimated vs. actual durations, deviations, skip patterns. It generates up to five improvement suggestions with evidence. Suggestions can include typed payloads for one-click application directly to the runbook source.

05

Compliance evidence generation

Every execution generates an auditable evidence record linked to compliance framework controls. No separate compliance workflow required. Doing the work is the compliance process.

Interactive demo

See it in action

A deployment runbook with verification checkpoints, a second-person approval gate, and an automatically generated compliance evidence record.

Protocol — Runbook Execution
94
score
12
active
3
flagged
Screenshot coming soon

What Protocol can do

Capabilities

Runbook Execution

Live procedure execution with three verification types. Approval steps enforce a second-person gate. Conditional branching for non-linear flows. Every step, timestamp, and evidence artifact is captured immutably.

AI-Assisted Authoring

Generate complete runbook drafts from natural-language descriptions. The AI produces step verification types, duration estimates, and role assignments. Improve individual steps with an AI technical writer that produces clearer, more actionable sub-steps.

AI Run Analysis

Post-execution analysis comparing estimated vs. actual durations, flagging deviations and skip patterns. Generates up to five improvement suggestions. Auto-apply payloads close the loop between execution data and procedure improvement.

Compliance Framework Management

Multiple frameworks simultaneously — ships with SOC 2, ISO 27001, and NIST CSF seed data. Cross-framework control mappings with confidence levels. Framework comparison showing how compliance with one translates to readiness for another.

Execution-Driven Evidence

Compliance status flows from runbook execution. Every tagged procedure run generates an auditable evidence record with maturity level, operator identity, and timestamps. No manual checkbox compliance.

Privacy Management

Full DSR lifecycle for GDPR, CCPA, LGPD, PIPL, and PDPA with jurisdiction-specific SLA enforcement. Consent management with legal basis tracking. ROPA register. Cross-border transfer assessments with mechanism tracking.

Breach Management

Incident lifecycle with multi-jurisdiction deadline enforcement: GDPR 72-hour, DORA 4-hour initial, NIS2 24-hour, HIPAA 60-day, CCPA 30-day, SEC 96-hour. Auto-generated notification timelines and remediation tracking.

Vendor Management

Vendor register with risk tiers, data access levels, and contract lifecycle tracking. Vendors inherit responsibility for specific controls with verification workflows. Concentration risk analysis flags over-reliance on single vendors.

Who uses Protocol

Built for

SRE / DevOps Engineers

Verified deployment procedures with approval gates and audit trails. Post-incident runbooks that enforce every step and capture evidence automatically.

Compliance Officers

Framework management, evidence generation, and maturity scoring without a separate compliance workflow. The execution is the evidence.

Privacy Teams (DPO)

DSR processing with jurisdiction-aware SLA tracking. Consent management, ROPA maintenance, and cross-border transfer assessments in one system.

Operations Managers

Standardised procedures across teams with visibility into execution patterns, deviations, and improvement trends.

See Protocol in action.

Book a 20-minute demo. We'll run through a live procedure with verification and evidence capture.

Already a customer? Go to Protocol →