neon recovery and logical backups — two distinct workflows

Recovery features and logical backups answer different operational questions. Their availability, retention, and account boundaries are provider-specific facts, so teams should verify those details in current provider documentation and their own contracts.

Walwarden's supported Neon path is concrete: schedule a logical backup, upload it to a configured customer-owned S3 destination, create a signed Manifest, and record the workflow in a hash-chained Audit chain. An operator can initiate restore through the CLI using a presigned S3 read.

Walwarden does not claim point-in-time recovery or instant rewind. Keeping that boundary explicit makes architecture reviews clearer: evaluate the provider feature on its own terms, and evaluate Walwarden's logical-backup artifact and operator-run restore path separately.

The roadmap records current and planned product statements. /proof is a published static demo artifact whose result is scoped to its matching checksum, drill key, and verifier run.