🚧 DROP is currently in active development — join the early access list to be notified at launch.
In Development — 2026

Disaster Recovery Orchestration Portal

DROP is GRATEIC's dedicated platform for structured DR plan documentation, runbook management, RTO/RPO tracking, and DR exercise scheduling — with a clear roadmap to full automated failover orchestration.

Join Early Access List View Roadmap
4
Development Phases
ISO 22301
Aligned Standard
BCMS
CMDB Integrated
AI
Powered Analysis

The Missing Link in Enterprise Resilience

Most organizations have DR plans — but they live in Word documents, shared drives, and spreadsheets nobody touches until disaster strikes. DROP changes that. It brings DR documentation into a structured, tested, living platform that connects directly to your BCMS and CMDB data.

📋

Structured DR Plans

Replace static Word documents with versioned, role-assigned DR plans — one per system, site, or application tier. Always current, always auditable.

📖

Living Runbooks

Step-by-step recovery runbooks with version history, AI review, and direct links to your CMDB server records, circuit documentation, and DR contacts.

⏱️

RTO/RPO Tracking

Define, track, and validate recovery time and point objectives against actual test results. Know instantly which systems are meeting their targets.

🧪

DR Test Management

Schedule, execute, and document DR exercises — tabletop, functional, and full failover tests — with after-action reports and ISO 22301 §8.5 compliance tracking.

🔗

BCMS + CMDB Integration

DR plans pull system data directly from your CMDB inventory and link back to BCMS BIA records and IT Systems DR tabs — one ecosystem, no double-entry.

🤖

AI-Assisted Runbook Review

AI reviews runbooks against best practices, flags missing steps, validates RTO feasibility, and generates first-draft recovery procedures from system profiles.

Core DR Documentation Modules

Phase 1 builds the structured documentation foundation — everything needed to replace ad-hoc DR docs with a managed, auditable DR program.

Phase 1 — Core
🗂️
System Registry
DR System Inventory
Central registry of all systems requiring DR coverage — linked to CMDB records with criticality tiers, RTO/RPO targets, DR strategy type, and owner assignment.
Tier 1/2/3 criticality classification
RTO / RPO target definition per system
DR strategy type (hot/warm/cold/cloud)
Owner and technical contact assignment
CMDB server record linkage
Phase 1 — Core
📖
Runbook Management
DR Runbooks
Step-by-step recovery runbooks per system — with versioning, role assignments, AI review, and structured sections covering activation, recovery procedures, validation, and failback.
Structured runbook template (10-step default)
Free-text custom runbook editor
Version history with change tracking
AI runbook review and gap detection
DR contact linkage per runbook
Phase 1 — Core
📄
Plan Management
DR Plan Library
Formal DR plan documents — one per system or application group — with structured sections, approval workflow, version control, and document repository linkage.
Structured plan sections (overview, activation, recovery, return)
Approval workflow (draft → review → approved)
Version numbering and change log
Document attachment and repository
ISO 22301 §8.4 compliance alignment
Phase 1 — Core
⏱️
Objectives Management
RTO / RPO Tracker
Define and track recovery objectives per system. Validate targets against actual DR test results and identify systems where objectives are at risk of not being met.
RTO / RPO definition per system and tier
Actual vs. target comparison from test results
At-risk objectives flagging
MTPD alignment from BCMS BIA records
Executive summary view
Phase 1 — Core
🧪
Test Management
DR Exercise Programme
Schedule, execute, and record DR tests — tabletop, functional, and full failover exercises. Capture results, issues, and generate after-action reports with remediation tracking.
Test types: tabletop, functional, full failover
Scheduled test calendar and overdue alerts
Pass/fail per RTO/RPO objective
After-action report generation
ISO 22301 §8.5 exercise compliance tracking
Phase 1 — Core
👥
Contacts & Teams
DR Contact Directory
Dedicated DR contact and team registry — separate from BCMS operational contacts. Role-based assignments for DR Lead, Technical Recovery, Business Liaison, and Vendor Support.
DR-specific roles and contact types
Primary and escalation contact chains
24/7 on-call contact details
Vendor and support contract references
Linked to system registry assignments
Phase 1 — Core
📊
Dashboard & KPIs
DR Programme Dashboard
Real-time view of your entire DR programme health — systems tested vs. overdue, RTO compliance rates, plan approval status, open issues, and upcoming test schedule.
DR coverage percentage by criticality tier
Test compliance rate (tested / overdue / never)
RTO objective compliance heat map
Open issues and remediation tracker
Upcoming test schedule widget
Phase 1 — Core
🚨
Issue Tracker
DR Issues & Gaps
Track DR gaps, findings from tests, and remediation actions — with owner assignment, due dates, severity rating, and closure evidence. Integrates with Jira for ticket creation.
Gap severity: Critical / High / Medium / Low
Owner and due date assignment
Test finding linkage
Jira ticket creation integration
Closure evidence and sign-off

From Documentation to Full Orchestration

DROP is being built in four phases — starting with structured documentation and progressively advancing to full automated DR failover orchestration. Each phase delivers immediate standalone value while building toward the complete vision.

Phase 1 — In Development
DR Documentation Foundation
2026 — Active Build
  • System DR inventory with CMDB linkage
  • Structured DR plan library with approvals
  • Runbook management with AI review
  • RTO / RPO objective definition and tracking
  • DR exercise programme and scheduling
  • After-action report generation
  • DR contacts and team registry
  • Programme health dashboard and KPIs
  • DR issues and gap tracker
Phase 2 — Planned
Monitoring & Alerting Integration
2026–2027
  • Azure Monitor and health check integration
  • System availability polling and alerting
  • DR activation trigger notifications
  • Real-time RTO countdown during incidents
  • Automated DR log initiation on alert
  • On-call escalation notification chains
  • Status page for internal stakeholders
Phase 3 — Roadmap
Semi-Automated Failover
2027
  • Guided failover workflow execution
  • Step-by-step runbook activation interface
  • Validation checkpoints per recovery step
  • DNS and load balancer change management
  • User access verification automation
  • Recovery progress tracking and reporting
  • Failback workflow management
Phase 4 — Vision
Full DR Orchestration
2027–2028
  • Automated failover execution via Azure APIs
  • VM provisioning and configuration automation
  • Database PITR and replication failover
  • Multi-region DR scenario management
  • AI-driven recovery sequence optimization
  • RTO achievement prediction and alerting
  • Full audit trail for regulatory compliance

Built Into the GRATEIC Ecosystem

DROP is designed as a standalone portal that integrates deeply with every other GRATEIC platform — eliminating silos between your GRC, BCMS, and infrastructure data.

🏗️
CMDB Integration
DR plans pull server records, circuit data, datacenter topology, and DR capability fields directly from your CMDB inventory.
🔄
BCMS Integration
BIA records, IT Systems DR tabs, and MTPD/RTO objectives flow from BCMS into DROP — one source of truth for recovery requirements.
📋
GRC Framework Alignment
DR activities map to ISO 22301, NIST CSF, and SOC 2 controls in the GRC platform — test results satisfy framework evidence requirements.
🎫
Jira Integration
DR gaps and remediation actions create Jira tickets automatically — tracked through to closure without leaving the platform.
🤖
AI Compliance Assistant
The same AI engine powering GRC and BCMS reviews runbooks, generates DR plan drafts, and flags recovery procedure gaps.
☁️
Azure Native
Hosted on Azure with the same multi-tenant isolation model as all GRATEIC platforms. Phase 4 automation runs directly against Azure APIs.

ISO 22301:2019 DR Coverage

DROP is structured around the ISO 22301:2019 requirements for BC strategies, plans, and exercises — making DROP test records directly usable as compliance evidence.

§8.3 — BC Strategies

DR strategy type, recovery infrastructure, and RTO/RPO documentation aligned to clause requirements.

§8.4 — BC Plans

Structured DR plans with activation procedures, roles, communication protocols, and return-to-normal sections.

§8.5 — Exercises

Exercise programme management, after-action reports, and findings tracking satisfying §8.5 exercise requirements.

§9.1 — Monitoring

KPI dashboard and RTO compliance tracking supporting clause §9.1 performance evaluation requirements.

NIST CSF — RC.RP

Runbooks and recovery procedures aligned to NIST CSF Recover function subcategories RC.RP-01 through RC.RP-05.

SOC 2 — A1.2 / A1.3

DR test evidence and availability controls mapped to SOC 2 Trust Services Criteria A1.2 and A1.3.

Be First When DROP Launches

JOIN the early access list to get notified at launch, provide input on features, and receive preferred pricing as a founding customer.