restoredrill
Automatically restores your latest PostgreSQL backup into a throwaway container and proves it actually works, with an audit-ready report.
🔗 Visit restoredrillDescription
Backups are only useful if they actually restore when you need them, and the uncomfortable truth is that a lot of teams have never actually tested whether theirs do. restoredrill automates that test: it grabs your most recent PostgreSQL backup, restores it into a temporary, disposable environment, runs checks you define, and hands you a report proving (or disproving) that your backup is good, without ever touching your real production database.
restoredrill fetches the latest backup (supporting pgbackrest and S3-based sources), restores it into a temporary Docker container, and runs user-defined validation checks, including RPO freshness and RTO timing, before generating a timestamped JSON report with audit-grade evidence suitable for SOC 2, ISO 27001, or AWS Foundational Technical Review requirements. It's fail-closed by design: any check that can't run counts as a failure rather than being silently skipped, integrates natively with GitHub Actions, and can alert via Slack, Prometheus, or generic webhooks.
💬 Our review
The short version: restoredrill fills a genuinely underserved niche, proving PostgreSQL backups actually restore, with paper trail, cleanly and for free, and it's actively maintained.
General backup platforms like Databasus cover more databases (MySQL, MongoDB, MariaDB) with a web UI but don't focus specifically on audit-grade restore proof, while BackupDrill targets Supabase specifically; restoredrill's niche is PostgreSQL-first compliance evidence via CI. Its fail-closed default (an unrunnable check counts as failure, not a silent pass) is exactly the right instinct for anything feeding an auditor, and running the restore in a disposable container means zero risk to production. With 89 stars and activity as recent as today, it's a small but clearly live project. Free and MIT-licensed, so there's essentially no reason not to add it to CI if you're on PostgreSQL and need to prove backup validity.
💰 Pricing
📊 Global score
🤖 AI-enriched data
Gratuit, MIT
Pros
prouve que les backups PostgreSQL se restaurent réellement, pas juste qu'ils existent
fail-closed : un check qui ne tourne pas = échec, jamais silencieux
rapport JSON de niveau audit (SOC2/ISO27001/AWS FTR)
restauration dans un conteneur jetable, zéro risque pour la prod
gratuit, open-source (MIT), natif GitHub Actions
Cons
PostgreSQL uniquement, pas multi-SGBD
nécessite Docker en CI
projet encore petit (89 stars)
