The matrix referenced from the Business Continuity Policy. Reviewed annually as part of the BC/DR test cycle.

Definitions

  • Recovery Time Objective (RTO) — maximum acceptable time between the disruption and full restoration of service.
  • Recovery Point Objective (RPO) — maximum acceptable data loss measured in time (e.g., last hour of writes).

Matrix

SystemTierRTORPORecovery procedureOwner
Customer-facing SaaS — AWS-hosted services (production app + API on AWS)Tier 14 hours15 minutesMulti-AZ failover; restore from continuous backups in alternate AWS region within 4h.CTO
Customer-facing SaaS — Vultr-hosted services (production compute on Vultr)Tier 14 hours15 minutesFailover to alternate Vultr region; cross-cloud failover to AWS for the same workload where the architecture supports it.CTO
Production database (AWS — Aurora / RDS Postgres)Tier 14 hours15 minutesPoint-in-time restore from automated AWS RDS backups; cross-region replica failover.CTO
Production database (Vultr — Postgres)Tier 14 hours15 minutesPoint-in-time restore from Postgres WAL archives; failover to a Postgres replica in an alternate Vultr region; logical-replication standby on AWS RDS available as cross-cloud DR.CTO
Object storage — customer data on AWS S3Tier 14 hours1 hourCross-region replication with versioning; restore from replica.CTO
Object storage — customer data on Vultr Object StorageTier 14 hours1 hourVultr Object Storage versioning; secondary copy replicated to AWS S3 (cross-cloud) where contractually required.CTO
Authentication (Rippling SSO + AWS IAM Identity Center)Tier 18 hours1 hourVendor-side failover (Rippling). Local break-glass IAM admin role for AWS, and break-glass root account for Vultr (held by CTO + CISO) for use during SSO outage.CISO
Secrets management (HashiCorp Vault — self-hosted on Vultr)Tier 14 hours15 minutesMulti-region Vault HA cluster on Vultr (Raft-based replication across distinct Vultr regions); periodic encrypted Vault snapshots replicated to AWS S3 (Object Lock) so Vault state can be restored on alternate Vultr regions or stood up on AWS Cloud Compute as last-resort cross-cloud DR. Break-glass root token sealed in CISO + CTO Dashlane vaults.CISO + CTO
Logging & monitoring (Better Stack)Tier 224 hours1 hourVendor-side. Local CloudWatch fallback for production-critical alerts.CISO
Source control / CI (GitHub, GitHub Actions)Tier 224 hours24 hoursVendor-side. Mirrors of master are pushed to S3 nightly for code recovery.CTO
Email / collaboration (Microsoft 365)Tier 224 hours24 hoursVendor-side. Out-of-band channels (cell, alternate email) per Key Contacts.CISO
Issue tracker (Linear)Tier 248 hours24 hoursVendor-side. Active incidents tracked out-of-band in #security-incidents Slack during outage.CTO
Password manager (Dashlane)Tier 28 hours24 hoursVendor-side. Break-glass credentials sealed in CISO + CTO vaults.CISO
Helpdesk / support toolingTier 35 business days24 hoursManual queue from helpdesk@ until restored.CISO
Marketing site / public docsTier 35 business days24 hoursVendor-side (Mintlify); rebuild from neuroscale/compliance-docs.CTO

Tiering rationale

TierDefinitionExamples
Tier 1Loss of service directly impacts customers’ ability to use Neuroscale products or breaches a contractual SLA.Production app, production DB, customer object storage.
Tier 2Loss of service blocks Neuroscale’s internal ability to operate, secure, or support production.SSO, logging, source control, collaboration.
Tier 3Loss of service is inconvenient but not customer-impacting and not security-critical short-term.Marketing site, internal helpdesk tooling.

Test cadence

  • Annual end-to-end DR test including Tier 1 backup-restore — see Compliance Calendar.
  • Quarterly spot-check of one Tier-2 recovery path.
  • Per incident that exercises any recovery procedure — results recorded in the IR ticket and used to refine this matrix.

Cross-references

Version history

VersionDateDescriptionAuthorApproved by
1.0May 8, 2026Initial versionCameron WolfeIshan Jadhwani