Untested backups aren't backups. restoredrill proves your PostgreSQL backups actually restore. It fetches the latest backup, restores it into a throwaway Postgres container, runs checks you define, and writes a JSON report with the restore time. Status: v0.1.0, early days. Postgres only. Things may still change.

Why: Everyone knows they should test restores. Almost nobody does, because there's nowhere safe to do it and never enough time. Scripts and cron jobs don't really fix this either, they fail quietly too: the job stops running, or keeps looping on stale data, and nobody gets told. restoredrill turns the restore drill into one command, and makes it loud if you skip it.

It runs on whatever schedule your recovery policy sets, not constantly, since most compliance frameworks actually warn against claiming continuous testing. Any gap becomes a finding. You get real proof you did what you said, when you said you'd do it. A policy doc is easy to fake, on purpose or by accident. Someone can write "we test quarterly" today even if nobody's run a test in a year. A report with a real timestamp, made by the tool itself, is much harder to fake.

If you're doing SOC 2, ISO 27001, or an AWS Foundational Technical Review, this is the kind of proof they want: real logs from real restores, showing what ran and when. restoredrill does one thing: a CI-native check built for an auditor's report, not a dashboard. Fail-closed by default, an RPO freshness check, your own SQL assertions, RTO tracked against a target, and every field formatted the same way so it copies cleanly into a SOC 2, ISO 27001, or AWS FTR packet. If your backups are handled and you just need proof they work on schedule, this is that. Quickstart: ten minutes, no production access.