Backup, Disaster Recovery and Exit

how does primevault prevent downtime, and what are your disaster recovery slas? architecture and backups multi az aws architecture with automated failover and cross region redundancy hourly cross region backups for application and system data, such as transaction metadata, policies, and logs immutable storage for audit logs to preserve the trail after recovery operations 24×7 on call engineering with documented runbooks for failover, rollback, and data restore continuous health checks on indexers, ingest pipelines, and event publishers targets under disaster conditions recovery time objective (rto) under 4 hours for service restoration recovery point objective (rpo) of 1 hour or better due to frequent backup cycles if primevault is unavailable, how do we stay independent and recover funds? key material protection mpc key shares are encrypted at rest with aes 256 and protected by hardware backed kms only attested enclaves can unwrap shares during normal operations encrypted share backups are stored in immutable, cross region object storage you can also keep your own encrypted copies or use a third party escrow your recovery path you retain encrypted mpc shares and an offline recovery kit with the required quorum, you can reconstruct vault keys locally and sweep funds without primevault the design scales to tens of thousands of keys and supports cold, warm, and hot configurations practiced teams typically regain full access in about 2 hours, assuming quorum participants are available recommended customer practice mirror daily encrypted share backups to at least two regions you control test reconstruction quarterly to validate keys, procedures, and quorum readiness even in a provider down scenario, you can independently restore access and move funds using your share quorum and the recovery kit