Connect your backups

Nothing to install: Verestore reads the newest PostgreSQL dump under a bucket prefix with a key that can only list and read that prefix, in any S3-compatible store, Azure Blob or Google Cloud Storage. Provider snapshots die with your account; prove your off-site copy restores. Pick your platform for a copy-paste policy, or read how the countersigned evidence maps to SOC 2, ISO 27001 A.8.13 and NIS2 Article 21.

How access works

What Verestore needs from your storage and why a list-and-read key on one prefix is enough.

AWS (RDS and S3)

Keep pg_dump backups of RDS or Aurora PostgreSQL in S3 and give Verestore a read-only, prefix-scoped IAM user.

Scaleway

Read-only Object Storage access for Verestore with an IAM application, a project-scoped policy and a bucket policy.

Cloudflare R2

Write pg_dump backups to an R2 bucket and give Verestore a read-only R2 API token scoped to that bucket.

Backblaze B2

Write pg_dump backups to a B2 bucket and give Verestore an application key limited to one bucket, one prefix, list and read.

Wasabi

Write pg_dump backups to a Wasabi bucket and give Verestore a sub-user with a read-only, prefix-scoped policy.

OVHcloud Object Storage

Write pg_dump backups to OVHcloud S3-compatible Object Storage and give Verestore an S3 user with a read-only policy.

DigitalOcean Spaces

Write pg_dump backups to a Space and give Verestore a limited-access Spaces key with read permission on that bucket only.

Google Cloud Storage

Give Verestore read-only access to a Cloud Storage bucket through an HMAC interoperability key on a dedicated service account.

Azure Blob Storage

Give Verestore read-only access to one Blob Storage container with a read-and-list SAS token or a service principal holding Storage Blob Data Reader.

Azure Backup for PostgreSQL Flexible Server

Restore Azure Backup vaulted backups of PostgreSQL Flexible Server as files to a storage container and let Verestore test the database file.

Cloud SQL for PostgreSQL

Schedule Cloud SQL for PostgreSQL exports to Cloud Storage and let Verestore test the newest export with a read-only HMAC key.

Neon

Schedule pg_dump of a Neon database to S3-compatible storage and give Verestore a read-only key.

Supabase

Keep a pg_dump of your Supabase database in your own bucket and connect it to Verestore with a read-only key.

Self-hosted PostgreSQL

Cron pg_dump to MinIO or any S3-compatible store and create a read-only, prefix-scoped user for Verestore.

API tokens

Read-only access to runs, coverage, reports and evidence over /api/v1 for CI pipelines and compliance tools.

Webhooks and incident tools

Signed webhooks, Microsoft Teams, PagerDuty and Opsgenie alerts for restore test results, with retries and a delivery log.

SOC 2 evidence for backup recovery

How Verestore's countersigned restore tests support the SOC 2 availability criterion on testing recovery.

ISO 27001 A.8.13 evidence for backups

How Verestore's countersigned restore tests support ISO/IEC 27001

NIS2 Article 21 evidence for backup management

How Verestore's countersigned restore tests support NIS2 Article 21(2)(c), backup management and disaster recovery.