self-hosting postgres backups after pgBackRest — separate the workflows first

Choosing backup tooling starts with the access model. A self-hosted Postgres operator can evaluate physical backup and WAL-archive tools. Walwarden does not provide that workflow.

Walwarden supports a narrower product path: scheduled logical backups for Supabase and Neon, uploaded to a configured customer-owned S3 destination. Each completed backup can include an Ed25519-signed Manifest and a hash-chained Audit chain. Operator-run restore uses the CLI and a presigned S3 read.

That distinction matters when comparing tools. If the requirement is physical backups, WAL archiving, or point-in-time recovery, we do not claim Walwarden provides it. AWS RDS/Aurora support is also on the roadmap, not a current provider capability.

The repository-backed roadmap separates current capability statements from planned work. /proof publishes one static demo Evidence bundle with its checksum and drill key; it is not live product-status evidence.