resistro verify spins up a temporary database, restores your backup into it, validates row counts and constraints, and reports pass or fail — automatically, after every backup.
Most backup tools write a file and stop. resistro verify goes further: it provisions a temporary database instance, runs a full restore, validates row counts and constraints, then tears it down. If the restore fails, you find out now — not at 3 AM.
On failure, resistro sends an alert via your configured channel (email, Slack, Teams, webhook) before anyone is woken up. The failed backup is flagged in the catalog and excluded from restore targets.
One static Go binary. No JVM, no Python runtime, no daemon orchestrator. Just database backups that work.
Full, incremental, and cluster-wide backups. Restore single databases or entire clusters with adaptive parallelism and automatic tuning.
Every backup is verifiable. Checksums, integrity checks, and restore drills ensure your backups actually work when you need them.
Content-addressable chunk storage eliminates redundancy across backups. Save up to 80% storage on recurring database snapshots (benchmark on request).
WAL archiving and continuous backup for PostgreSQL. Recover to any point in time, not just when your last backup ran.
Built-in metrics exporter. Track backup age, duration, size, and success rate. Alert before problems become disasters.
AES-256 encryption at rest. Gzip or Zstandard compression. Your data stays safe and small, at rest and in transit.
Push backups to S3-compatible storage, sync across regions, or keep them local. Your infrastructure, your choice.
Automated restore testing. Schedule regular drills to prove your backups are recoverable. RTO analysis included.
Searchable catalog of all backups. Retention policies, automatic cleanup, and history tracking across your entire fleet.
Every PostgreSQL and MariaDB backup tool can write a file. The question is whether that file actually restores. Most tools leave that question unanswered.
| Tool | Creates backups | Restores backups | Automatic restore verification |
|---|---|---|---|
| resistro | ✓ | ✓ | ✓Full restore into temporary DB, row count validation |
| pgBackRest | ✓ | ✓ | ✗verify checks file checksums only, not restore success |
| Barman | ✓ | ✓ | ✗check-backup validates WAL/file integrity, not a restore |
| mariabackup | ✓ | ✓ | ✗None built-in |
| pg_dump + cron | ✓ | ✓ | ✗None built-in |
Point resistro at your database. One config file, sensible defaults, auto-detection of engine and version.
Run resistro backup manually or via systemd timer. Compression, encryption, and verification happen automatically.
Prometheus metrics, retention policies, and restore drills run on autopilot. You get alerted only when something needs attention.
No wrapper scripts needed. The CLI does exactly what you'd expect.
# Backup a single database resistro backup single myapp_production # Backup all databases on this host resistro backup cluster # Backup with compression and encryption resistro backup single myapp --compress zstd --encrypt
Native integration with PostgreSQL and MariaDB/MySQL. No plugins, no extensions.
pg_dump, pg_restore, custom format, WAL archiving
mysqldump, socket and TCP auth, binary log
Use the open-source binary for free, forever. Or let Resistro Cloud handle storage, alerting, and verified restores for you.
All plans include client-side AES-256-GCM encryption. Your data never leaves your control. EU-hosted on Hetzner. AVV/DPA available for Business and above.
Alle Preise netto zzgl. gesetzlicher MwSt.
Free and open-source for self-hosting. Or let Resistro Cloud handle storage, alerting, and automated restore verification — from 9€/month, EU-hosted, E2E encrypted.
What teams say about Resistro.
Running our pilot program — feedback from production users coming soon.
Using Resistro in production? We’d love to hear from you.