01 / evidence begins here
Backups you can verify without us.
Walwarden turns Supabase or Neon backups into signed evidence stored in your own AWS S3.
02 / source
Connect the Postgres you already run.
Add your Supabase or Neon database. Walwarden follows its backup activity without replacing your provider.
03 / custody
Your backup. Your AWS S3.
Scheduled logical backups land in a destination controlled by your team.
04 / evidence
Every successful backup leaves signed evidence.
A manifest records the artifact checksum, signature, and hash-linked audit history for that backup.
05 / independent check
Verify it offline.
Use the matching public key to verify the backup, signature, and supplied history without trusting Walwarden. Public-key publication alone is not proof.
Open the published evidence
06 / agent control
Hand the controls to your AI agent.
Scoped REST, JSON CLI, SDK, and public agent docs let an agent inspect, trigger, and poll backup jobs within policy. Offline bundle verification stays with the public verifier.
Published evidence
Don’t trust the animation. Check the evidence.
Run the public verifier against Walwarden’s demo bundle and its separately published public key.
Verify the published bundle
curl -fsSO https://walwarden.com/proof/walwarden-demo-evidence-bundle.tgz curl -fsSO https://walwarden.com/proof/walwarden-proof-pubkey.pem npx --yes @walwarden/verifier --bundle walwarden-demo-evidence-bundle.tgz --pubkey walwarden-proof-pubkey.pem
Evidence bundle contents
manifests/bjob_proof_20260612.manifest.json audit_events.json artifacts/team/team_proof_demo/db/db_proof_demo/backup/2026/06/12/bjob_proof_20260612.dump README.md
The matching public key is published separately from the signed manifest.
Verifier output
OK: manifest signature valid for backup_job=bjob_proof_20260612 OK: manifest artifact sha256 matches for backup_job=bjob_proof_20260612 (d91ea6fdb014…) OK: legacy audit rows internally valid through seq=8 (8 audit events); source completeness not proven OK: 1 manifests verified, legacy audit row set valid; source completeness not proven
Storage you control. Proof you can verify.
Own the backup. Keep the evidence.
Restore remains operator-run, so target database credentials stay on the machine you control.