Business Continuity Policy
Ensuring uninterrupted educational software services, data integrity, and disaster recovery for Australian schools.
1. Executive Summary & Purpose
Inkcraft Education Pty Ltd ("Inkcraft Education", "we", "our") recognises that educational institutions depend on our platforms — including Inkcraft Studio and Inkcraft Report — for daily classroom diagnostic assessments, student tracking, curriculum mapping, and report writing workflows.
This Business Continuity Policy ("BCP") outlines our framework for maintaining operational resilience, mitigating potential service interruptions, and executing rapid recovery procedures in the event of technical disruptions, infrastructure outages, or natural disasters.
2. Architectural Resilience: Cloud Redundancy & Isolated Databases
A foundational pillar of Inkcraft Education's reliability is our secure cloud architecture with strict tenant isolation embedded within Inkcraft Studio and Inkcraft Report. Both products are cloud-hosted on Australian infrastructure (Fly.io, Sydney) and benefit from resilient architecture with automatic failover and redundancy.
Single-Tenant Database Isolation
Every school is provisioned its own dedicated database. This eliminates the risk of cross-institutional data corruption and ensures that any database-level issues are isolated to a single tenant, vastly reducing the blast radius of potential incidents.
3. Recovery Time & Recovery Point Objectives
Inkcraft Education adheres to strict target metrics for system restoration and data preservation:
< 2 Hours
Target maximum downtime to restore core cloud services following a catastrophic cloud provider outage.
< 15 Minutes
Target maximum allowable data gap for cloud-synced diagnostic records, backed up via continuous point-in-time replication.
4. Cloud Infrastructure & Redundancy
All cloud components supporting Inkcraft Education are hosted via Fly.io on tier-1 data centre infrastructure located within Sydney, Australia. Key safeguards include:
- Automated Daily Backups: Full system snapshot backups are performed daily with 30-day retention cycles and securely pushed to off-site encrypted vault storage hosted on Tigris Data in Sydney.
- Minimal-Downtime Deployments: Software patches and feature updates utilise rolling deployment strategies to maintain continuous user access.
5. Incident Response & School Communication
In the event of a critical service disruption or unexpected incident, Inkcraft Education follows a standardised four-phase Incident Management Protocol:
- Detection & Triage: Automated monitoring alerts on-call engineers within 5 minutes of anomalous service behaviour.
- Containment & Mitigation: Emergency failover mechanisms are triggered to isolate affected components and restore functionality.
- Institutional Notification: School IT administrators and designated contact persons are notified via email and status portal updates within 30 minutes of a confirmed major outage.
- Post-Incident Review: A root-cause analysis (RCA) report is conducted within 5 business days and shared with affected educational institutions upon request.
6. Testing, Auditing & Policy Governance
To ensure our continuity measures remain effective against evolving technical challenges:
- Disaster recovery failover simulations are conducted bi-annually.
- Data backup restoration tests are performed quarterly.
- This Business Continuity Policy is reviewed annually by Inkcraft Education leadership to reflect infrastructure updates and legislative compliance requirements.
7. Continuity Support & Enquiries
For enquiries regarding our disaster recovery specifications or institutional continuity compliance, please reach out via Contact & Consultations or email support@inkcrafteducation.com.