why walwarden exists

A logical dump is useful, but it does not by itself record a later restore or the sequence of actions around that restore.

Walwarden exists to make those product surfaces explicit: scheduled logical backups for Supabase and Neon to a configured customer-owned S3 destination, an ed25519-signed manifest, a hash-chained Audit chain, operator-run restore through the CLI, and Evidence-bundle export.

Verification remains artifact-specific. It requires the named bundle, its matching public key, and a successful verifier result. A static page or publication date is not live operational evidence, and these mechanisms do not guarantee a customer outcome.

The roadmap separates supported code capability, planned work, and claims Walwarden does not make. /proof provides one published static demo Evidence bundle for local inspection.