Analysis updated 2026-05-18
Automatically verify that Supabase or Neon backups can actually be restored, not just that they exist.
Get alerted when no verified backup exists within a set time window.
Restore a production database from a proven-good backup during an outage.
Enforce retention rules that only count backups which passed a real restore test.
| vncwr/backwyn | 12vault/ravel | alexremn/finalizer-doctor | |
|---|---|---|---|
| Stars | 3 | 3 | 3 |
| Language | Go | Go | Go |
| Setup difficulty | moderate | easy | easy |
| Complexity | 4/5 | 2/5 | 3/5 |
| Audience | ops devops | developer | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires a Postgres database, a storage bucket, and a 32-byte encryption key, run via Docker Compose.
Backwyn is a command line tool that takes and checks Postgres database backups, built for teams using Supabase, Neon, PlanetScale, or any other Postgres database. Its core idea is that a backup file sitting in storage tells you nothing about whether it would actually work if you needed it. Many backup systems only confirm that a job ran, not that the resulting file can be restored. On every cycle, backwyn dumps the database, encrypts it with AES-256-GCM, uploads it to a storage bucket you control, and then proves the backup is good by fetching it back, decrypting it, checking it, and restoring it into a real, throwaway database it spins up just for that test. Only after a successful restore is a backup marked as verified. A separate check command can be run on a schedule to confirm a verified backup exists within a set time window, exiting with an error code and firing a webhook if not, so a team can be alerted before an outage rather than during one. Restoring your data back is done with a restore command, which by default refuses to overwrite a non-empty database or restore from a backup that was never verified, with explicit flags available to override those guards when needed. There is also a plain file export option, so recovered backups can be restored using standard Postgres tools with no dependency on backwyn itself. A prune command deletes old backups according to retention rules, but only ever removes verified backups, and always keeps at least the most recent one. Setup involves a docker compose file, a database connection using a read-only role, a storage bucket, and an encryption key. The project is written in Go, is MIT licensed, and states it is not a replacement for point-in-time recovery or a provider's own backup system, but an independent, tested second copy.
A Postgres backup tool that test-restores every backup automatically and alerts you if no verified backup currently exists.
Mainly Go. The stack also includes Go, Docker Compose, PostgreSQL.
MIT license: free to use, modify, and distribute, including commercially, as long as the copyright notice is kept.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.