Skip to content
walwardenPricingProofBlogRoadmapDocsSign inStart free

Postgres backup independence

Postgres backups with cryptographic proof.

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.

  1. SourceSupabase or NeonManaged Postgres
  2. WalwardenBack up and signpg_dump · SHA-256 · Ed25519 · audit chain
  3. Your copyYour object storageArtifact · manifest · evidence bundle

What ships today

A backup copy with evidence attached.

Scheduled logical backups

Run managed Postgres backups on a schedule, outside the source provider backup system.

Evidence bundles with signed manifests

Export the manifest, artifact checksum, audit events, and signature for offline review with the matching public key.

Hash-linked audit chain

Check the supplied event sequence for broken links or inconsistent hashes during independent verification.

Operator-run restore

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

From managed Postgres to portable recovery evidence.

  1. Connect Postgres

    Add a supported Supabase or Neon database.

  2. Choose your storage

    Configure AWS S3 or a supported S3-compatible destination you control.

  3. Walwarden runs and signs

    The worker creates the logical dump, checksum, manifest, and audit record.

  4. Verify independently

    You or a reviewer can inspect the evidence offline with the public verifier.

Bring your own LLM

Give your LLM a scoped way to operate Walwarden.

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.

  1. Create a scoped API key

    Choose only the database, backup, restore, or evidence scopes the agent needs.

  2. Load the public agent guide

    Give the LLM Walwarden’s generated integration guide or public llms.txt context.

  3. Use machine-readable commands

    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

Trust the verification, not a screenshot.

This is the verifier command and output for Walwarden’s published demo bundle: 1 signed manifest and 8 hash-linked audit events.

Backup bjob_proof_20260612 · bundle SHA-256 3bca0d291cd68383ee34b66daf61e225deca727f48effe14d150a1afac776713

Open the complete proof bundle

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/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.

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

Stronger chain of custody

A second, independently verifiable recovery record.

Walwarden complements provider backups with a copy in storage you control and portable evidence of what happened. Independent verification uses the matching public key.

Provider backupWalwarden record
Copy held inside the provider boundaryCopy held in object storage you control
Service logs and status screensSigned manifest and hash-linked audit events
Recovery through provider toolingOperator-controlled restore and offline verification

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

Own the backup. Keep the evidence.

Walwarden — Postgres backups with cryptographic proof