git404hub

what is backwyn fr?

vncwr/backwyn — explained in plain English

Analysis updated 2026-05-18

3GoAudience · ops devopsComplexity · 4/5LicenseSetup · moderate

tl;dr

A Postgres backup tool that test-restores every backup automatically and alerts you if no verified backup currently exists.

vibe map

mindmap
  root((Backwyn))
    What it does
      Backs up Postgres databases
      Test restores every backup
      Alerts on missing coverage
    Tech stack
      Go
      Docker Compose
      Postgres
    Use cases
      Verify Supabase backups
      Verify Neon backups
      Automate restore drills
    Audience
      Backend developers
      DevOps teams
      Database administrators

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Automatically verify that Supabase or Neon backups can actually be restored, not just that they exist.

VIBE 2

Get alerted when no verified backup exists within a set time window.

VIBE 3

Restore a production database from a proven-good backup during an outage.

VIBE 4

Enforce retention rules that only count backups which passed a real restore test.

what's the stack?

GoDocker ComposePostgreSQLAES-256-GCM

how it stacks up fr

vncwr/backwyn12vault/ravelalexremn/finalizer-doctor
Stars333
LanguageGoGoGo
Setup difficultymoderateeasyeasy
Complexity4/52/53/5
Audienceops devopsdeveloperops devops

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires a Postgres database, a storage bucket, and a 32-byte encryption key, run via Docker Compose.

MIT license: free to use, modify, and distribute, including commercially, as long as the copyright notice is kept.

in plain english

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.

prompts (copy fr)

prompt 1
Help me set up backwyn to back up my Supabase Postgres database using a read-only role.
prompt 2
Explain how backwyn's verify step differs from a normal backup job.
prompt 3
Write a monitoring integration that alerts my team when backwyn's check command exits with code 3.
prompt 4
Show me how to restore a backwyn backup into a fresh database without overwriting production.
prompt 5
Set up a retention policy with backwyn prune that keeps 14 daily and 12 monthly verified backups.

Frequently asked questions

what is backwyn fr?

A Postgres backup tool that test-restores every backup automatically and alerts you if no verified backup currently exists.

What language is backwyn written in?

Mainly Go. The stack also includes Go, Docker Compose, PostgreSQL.

What license does backwyn use?

MIT license: free to use, modify, and distribute, including commercially, as long as the copyright notice is kept.

How hard is backwyn to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is backwyn for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.