Business Continuity & Disaster Recovery
How we handle backups, disaster recovery, and continuity planning to support reliable operations.
Last updated: December 16, 2025
At a glance
- Backups: we maintain backups suitable for a production SaaS environment.
- Recovery: recovery procedures are used to restore service after failures.
- Separation: application hosting (DigitalOcean) and inference workloads (AWS SageMaker) are separated.
- Continuous improvement: resilience practices evolve as the platform and customer needs mature.
Continuity approach
Our continuity approach is designed to reduce downtime and data loss risks. We use infrastructure separation, controlled deployments,
operational monitoring, and backups to support recovery from common failure modes.
Backups
We maintain backups and recovery procedures for production data and system configuration where appropriate. Backup protections and access
are controlled to prevent unauthorized access.
- Backup protection: access is restricted and managed through least privilege practices.
- Recovery readiness: backups support restoration of services after data loss events.
- Minimization: message content is processed briefly and removed; derived metadata is retained for reporting.
Disaster recovery
Disaster recovery focuses on restoring core service functionality and customer access. Recovery actions may include redeploying application
services, restoring databases from backups, and validating integrations and processing workflows.
- Application recovery: restore application services hosted on DigitalOcean.
- Database recovery: restore managed database state when needed.
- Inference recovery: restore inference workflows on AWS SageMaker if impacted.
Testing and improvement
We review operational incidents and significant outages to improve resilience. Where appropriate, we test recovery procedures and update
documentation and monitoring to reduce recurrence risk.