Private backup architecture.
A careful approach to preserving Holliday's snapshots and historical evidence, using encryption and verifiable restoration rather than blind copying.
Project status: Configuration and testing. One disposable encrypted transfer test passed, but the production encryption key and dedicated Google Drive connection have not been deployed. This is not a public backup service.
What it is for
This project is intended to allow the Holliday AI owner to archive historical backups to their own Google Drive. We aim to encrypt data before upload, preserve the recovery key with the owner outside the VPS, and independently verify that an archive can be restored.
How Google Drive is used
Once configured, OAuth authorization will permit the private backup software to upload, inspect, and verify only the backup data and files supported by the permissions granted. Google Drive content is not used for advertising or sold to third parties. The connection is for one authorized owner, not public website visitors.
What stays on the VPS
Active mission databases, memory, operational services, and other live workloads stay on local disk. Backups must pass remote integrity and real restore checks before a separate owner-approved local cleanup is considered.
Get in touch
Read the Privacy Policy and Terms of Use. Before publication, Druvex Lab must confirm the working privacy contact address for this website.