backup independence — define the destination and restore operator

"Who owns the bytes?" is shorthand. A useful architecture review asks more precise questions: which AWS account contains the configured destination, who controls its policy, who pays for storage and egress, and who operates restore.

Walwarden's supported path is a configured customer-owned S3 destination. Backup execution uploads the logical dump and signed Manifest to that path. Operator-run restore uses a presigned S3 read and runs `pg_restore` through the CLI on the operator's machine.

These are capability and configuration statements, not an absolute custody promise. Deployment configuration, destination policy, credentials, and external service availability still matter. Review the exact setup rather than inferring an outcome from marketing language.

Walwarden supports Supabase and Neon today; AWS RDS/Aurora is on the roadmap. The published /proof bundle is a static demo artifact with a declared checksum and drill key.