Business Continuity Summary

Business Continuity Summary

Version: 1.0 · Owner: Pocket PMO Ltd · Approval status: Approved · Review date: annually

Purpose

This summary explains how Pocket PMO continues to serve customers through disruption, including hosting-provider outages, key-personnel unavailability, and third-party service failures.

Scope

Pocket PMO's SaaS service and its customer-facing surfaces.

Dependencies

Pocket PMO depends on:

• Managed Postgres and edge functions — Lovable Cloud (Supabase-managed).
• Static hosting — Lovable-managed.
• Payments — Stripe.
• Email — Lovable Emails (Resend under the hood).
• AI Gateway — Lovable AI Gateway.
• Sign-in providers — Google and Apple (for OAuth sign-in only).
• Transcription — ElevenLabs.
• Optional error monitoring — Sentry.

Continuity strategy

• Client resilience. The application is a PWA with offline caching (React Query IndexedDB persistence, 24-hour stale) and a FIFO offline mutation queue. Users can view and continue work through short outages of the backend.
• Feature isolation. AI, email, and payments are independent of core project workflows; degraded modes stay usable.
• Stale-chunk recovery. Deployment code path recovers automatically from stale asset bundles.
• Manual failover. Where a sub-processor is unavailable, the affected feature is disabled in-app and reported on the status route.

Recovery objectives

• RTO (Recovery Time Objective) — 24 hours.
• RPO (Recovery Point Objective) — 24 hours.
• Backup retention — approximately 14 days of daily backups managed by Lovable Cloud, browsable and restorable.

Testing

An annual restore-and-fail-over dry run is recommended. Results and date will be recorded here.

Document history