Scheduled logical backups
Run managed Postgres backups on a schedule, outside the source provider backup system.
Postgres backup independence
Walwarden runs scheduled logical backups from Supabase or Neon into AWS S3 or supported S3-compatible storage you control, then produces signed evidence you can verify offline with the matching public key.
Your database stays with your provider. Your backup lands in storage you control.
LLM-ready. Scoped API keys, JSON CLI output, REST, SDK, and public agent docs.
What ships today
Run managed Postgres backups on a schedule, outside the source provider backup system.
Export the manifest, artifact checksum, audit events, and signature for offline review with the matching public key.
Check the supplied event sequence for broken links or inconsistent hashes during independent verification.
Restore from object storage to a target database from a machine you control.
Target database write credentials stay on the operator machine during restore.
How it works
Add a supported Supabase or Neon database.
Configure AWS S3 or a supported S3-compatible destination you control.
The worker creates the logical dump, checksum, manifest, and audit record.
You or a reviewer can inspect the evidence offline with the public verifier.
Bring your own LLM
Any LLM or coding agent that can run shell commands or call HTTP can use Walwarden’s public CLI, SDK, and REST API to inspect backups, trigger jobs, poll status, and read evidence.
API tokens are available on the Team plan. An Admin or Owner chooses the least-privilege scopes and can revoke the token at any time.
Choose only the database, backup, restore, or evidence scopes the agent needs.
Give the LLM Walwarden’s generated integration guide or public llms.txt context.
Run the CLI with --json, then check job and evidence results before reporting success.
export WALWARDEN_BASE_URL="https://walwarden.com" export WALWARDEN_API_KEY="<scoped-api-key>" npx --yes walwarden-cli --json profile validate
Do not paste the API key into a chat. Provide it through the agent runtime’s approved secret store or environment.
Real published evidence
This is the verifier command and output for Walwarden’s published demo bundle: 1 signed manifest and 8 hash-linked audit events.
Open the complete proof bundlecurl -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
manifests/bjob_proof_20260612.manifest.json audit_events.json artifacts/org/org_proof_demo/db/db_proof_demo/backup/2026/06/12/bjob_proof_20260612.dump README.md
The signed manifest records the artifact checksum and signature. The matching public key is downloaded separately.
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
Stronger chain of custody
Walwarden complements provider backups with a copy in storage you control and portable evidence of what happened. Independent verification uses the matching public key.
A bundle containing a signed manifest can enter downstream fraud-review or data-analysis pipelines with artifact-integrity evidence attached. Walwarden verifies signed-manifest and artifact integrity and checks the supplied audit chain for internal consistency; it does not detect fraud.
Postgres backup independence