Overview
This summary explains how continuity and recovery responsibilities are divided for customer-hosted OpsRabbit deployments. Product recovery procedures cover components managed by the OpsRabbit provider, while customers retain responsibility for their hosting platform and selected dependencies.
The policy addresses business impact, preparedness, exercises, recovery validation and customer communication.
Continuity approach
OpsRabbit provider maintains response and recovery responsibilities for the OpsRabbit product components it controls. For customer-hosted deployments, the customer owns infrastructure availability, backups, recovery configuration, identity availability and the resilience of customer-selected cloud and model services.
Core practices
- Identify critical product capabilities, dependencies and owners.
- Maintain recoverable code, configuration and release artifacts.
- Exercise restoration and incident-coordination procedures periodically.
- Review material changes to hosting, model endpoints and integrations for continuity impact.
- Document and communicate customer actions required for recovery.
Deployment-specific objectives
Recovery time, recovery point, service availability and support commitments must be defined in the applicable customer agreement or deployment plan. This public summary does not create an SLA.
Business impact and dependencies
Continuity planning identifies essential product functions, source and release repositories, personnel, customer-hosted services, identity systems, databases, model endpoints and integrations. Each material dependency has an owner and a documented recovery or workaround strategy appropriate to OpsRabbit provider’s control.
Preparedness and recovery
OpsRabbit provider maintains contact, escalation and recovery procedures for components it controls. Customers maintain backups, infrastructure redundancy, platform monitoring, database recovery, identity recovery and provider continuity for customer-hosted deployments. Recovery actions must preserve evidence, validate integrity, restore least-privilege access and confirm product behavior before normal operation resumes.
Testing and maintenance
Continuity exercises use scenarios such as loss of a key service, corrupted configuration, credential compromise, provider outage and unavailable personnel. Results record objectives, participants, observations, corrective actions, owners and target dates. Material lessons are incorporated into plans and shared-responsibility documentation.
Customer communication
For a disruption affecting an active engagement, OpsRabbit provider coordinates through the agreed operational contacts and provides available information about scope, workaround, recovery and customer actions. This policy does not create availability, RTO or RPO commitments beyond an executed agreement.