Business Continuity
What happens if something goes wrong, and why your Orca keeps running regardless
1. Overview
Orca is a managed service operated by OMG Center Limited, a small specialist provider. This document sets out our approach to business continuity, covering both the resilience of the Orca application itself and the continuity of the managed service OMG Center provides around it.
The most important thing to understand upfront is that the two are largely independent. Your Orca instance operates locally on your device and connects to services you own and control. OMG Center provides the software and configuration layer. A disruption to OMG Center does not take your Orca offline.
2. Your Orca instance independence
Because your Orca instance runs locally and connects to your own systems, your day-to-day operations are not affected by disruptions to OMG Center. Your meetings still get prepped. Your follow-ups still go out. Your data remains exactly where it always was, in your own systems.
Your Orca application is installed on your device and runs as a native desktop application. It does not depend on OMG Center servers to function day-to-day. The connections it makes are between your device and services you subscribe to directly, such as Microsoft 365, Google Workspace, Supabase, and the AI APIs.
If OMG Center is temporarily unavailable for any reason, your Orca continues to operate normally. Meeting preparation, follow-up drafting, contact analysis, and all core features continue without interruption.
3. Licence continuity
Orca uses Keygen for licence management and validation. Keygen's infrastructure is independent of OMG Center.
The licence system includes a 7-day offline grace period. If the licence validation server is temporarily unreachable, whether due to a network issue on your side or a Keygen outage, your Orca application continues to function normally during that window. Normal validation resumes automatically once connectivity is restored.
In the event of an extended disruption, OMG Center would communicate with affected clients and arrange licence continuity on an individual basis.
4. Third-party service resilience
Your Orca instance depends on services you subscribe to and control. The availability of these services determines what Orca can do at any given moment. The table below summarises the key dependencies and their typical behaviour under disruption.
| Service | What it does | Typical uptime | Fallback behaviour |
|---|---|---|---|
| Microsoft 365 / Google Workspace | Email, calendar, contacts | 99.9%+ (provider SLA) | Orca queues and retries pending operations |
| Supabase | Contact database, analysis storage | 99.9% (Supabase SLA) | Application functions with locally cached data |
| Anthropic Claude API | AI analysis and drafting | 99.5%+ | Features requiring AI are temporarily unavailable; all other features continue |
| Transcription service | Meeting transcripts | 99%+ | Manual transcript upload available as an alternative |
Because you hold your own API keys and subscriptions for each of these services, you have direct access to each provider's status pages and support channels.
5. What requires OMG Center
The following activities require OMG Center's involvement and would be affected if Chris Simmance were unavailable for an extended period:
- Configuration changes to your Orca instance (adjusting prompts, workflows, or integrations)
- Deployment of new features or application updates
- Technical support and troubleshooting
- Licence provisioning, renewal, and management
- Onboarding new users or seats
Day-to-day operation of your existing Orca configuration is not in this list. An unavailable OMG Center means your Orca stays exactly as it is, not that it stops working.
6. Contingency measures
OMG Center maintains the following measures to reduce the impact of any disruption to its operations:
- All client configurations are fully documented and version-controlled
- Build and deployment processes are documented, scripted, and reproducible without reliance on tribal knowledge
- Source code is maintained in private version control repositories with appropriate access controls
- Successor planning is in place for scenarios involving extended unavailability, including arrangements for continuity of client support
- Client data is never at risk from an OMG Center disruption, because it is entirely client-controlled and lives in client-owned systems
7. Communication
If a disruption affects OMG Center's ability to deliver support, configuration changes, or software updates, clients will be notified by email at the earliest opportunity. Notifications will include:
- The nature and expected duration of the disruption
- Which services or activities are affected
- Confirmation of what is not affected (i.e., your running Orca instance)
- Expected resolution timeframe and any interim arrangements
Contact for continuity matters: chris@simmance.ai
8. Recovery priorities
In the event of a disruption requiring recovery effort, OMG Center will prioritise restoration in the following order:
- Licence validation - Ensuring client licences remain active and Keygen connectivity is restored
- Critical bug fixes - Addressing any defects that prevent normal use of the application
- Configuration changes - Client-requested adjustments to running instances
- Feature updates - Planned enhancements and new functionality
9. Review
This business continuity plan is reviewed annually and updated following any material change to the architecture of the Orca service or OMG Center's operating model. The current version was last reviewed in March 2026.
Questions regarding business continuity should be directed to chris@simmance.ai.