Business Continuity
Last updated: July 2026
Purpose
This document outlines how Teacher's Buddy maintains service availability and recovers from disruptions to protect client data and minimise downtime.
Recovery Objectives
| Metric | Target |
|---|---|
| Recovery Time Objective (RTO) | < 1 hour for application, < 4 hours for full service |
| Recovery Point Objective (RPO) | < 24 hours (daily automated backups) |
Infrastructure Resilience
Teacher's Buddy is fully cloud-native. All infrastructure is managed by providers with independent certifications.
| Component | Provider | Resilience | Certification |
|---|---|---|---|
| Web applications | Railway + Cloudflare | Managed deployments, health checks, edge routing and deployment rollback | SOC 2 Type II |
| Core database | PlanetScale | Daily backups, point-in-time recovery (7 days) | SOC 2 Type II |
| File storage | Cloudflare R2 | 99.999999999% durability, automatic replication | SOC 2 Type II, ISO 27001 |
| Background services | Railway | Automatic restart, health checks | SOC 2 Type II |
Backup Strategy
| Data | Method | Frequency | Retention | Encryption |
|---|---|---|---|---|
| Core database | PlanetScale automated | Daily + point-in-time | 7 days | AES-256 |
| File storage | Cloudflare replication | Continuous | Durable by design | AES-256 |
| Application code | Git (GitHub) | Every commit | Indefinite | GitHub encryption |
Database restoration uses provider point-in-time recovery, while application recovery uses deployment rollback and redeployment procedures. We review these recovery procedures when infrastructure or material providers change.
Disaster Recovery Scenarios
- Application failure: Roll back or redeploy a previous successful application version through Railway, with Cloudflare continuing to provide edge routing.
- Database failure: PlanetScale automatic failover (near-instant). Manual recovery from point-in-time backup < 1 hour.
- Storage failure: Cloudflare R2 automatic replication handles facility-level failures transparently.
- Third-party outage: Graceful degradation. Core platform continues; AI generation and email queue for retry.
- Region failure: Follow provider recovery procedures and redeploy affected services in a supported region when required.
We review disaster recovery scenarios as part of continuity planning and update response steps when infrastructure or material providers change.
Communication During Outages
For significant service disruptions, we notify affected clients via email within 4 hours with regular status updates until resolution.
Data Residency
For Australian customers, database storage is hosted in the Australian region via PlanetScale. Backups remain in the same region. See our Privacy Policy and Sub-Processors page for full details.
Contact
Questions about business continuity? Contact privacy@teachersbuddy.com