pgbranch

pgbranch

Branch your Postgres database like you branch code

2 followers

Ever run migrations on a feature branch, then switch back to main, only to find your database is broken? pgbranch fixes that. Just like git manages code branches, pgbranch manages database branches. Create snapshots of your database state, switch between them instantly, and never manually roll back migrations again.
pgbranch gallery image
pgbranch gallery image
pgbranch gallery image
Free
Launch tags:Developer ToolsGitHub
Launch Team / Built With
Webflow | AI site builder
Webflow | AI site builder
Start fast. Build right.
Promoted

What do you think? …

Vladyslav Len
I built pgbranch because I was tired of the "switch branches, database is broken" dance. Every time I'd context-switch to review a PR or fix a bug on main, I'd have to deal with migrations from my feature branch. Drop and re-seed? Wait 5 minutes. Roll back manually? Miss something and waste an hour debugging. pgbranch uses PostgreSQL's template database feature to create instant snapshots. When you "checkout" a branch, it drops your working database and recreates it from the template. File-level copy. Fast. It's intentionally simple — git-like commands for a git-like workflow. Works with any Postgres setup, no special configuration needed. Would love your feedback. What's missing? What would make this more useful for your workflow?