Databricks
databricks.com › blog › database-branching-postgres-git-style-workflows-databricks-lakebase
Database Branching in Postgres: Git-Style Workflows with Databricks Lakebase | Databricks Blog
April 10, 2026 - This log-structured architecture is what makes database branching possible as a primitive rather than as a feature layered on top. Because storage is versioned, multiple branches can reference the same underlying data without risk of conflict. Because compute is independent, each branch runs its own Postgres process and scales on its own.
Xata
xata.io › postgres-branching
Instant branching
Your database in seconds, without copying data. Fully isolated Postgres branches with schema and production-like data, instant and cheap to run.
Pg_branch: Experimental Postgres extension brings Neon-like branching
I think this should be really straightforward by using one database as a template for another. This is how Postgres's create database works and it defaults to Template1 · https://www.postgresql.org/docs/current/manage-ag-templatedb More on news.ycombinator.com
67
193
October 10, 2023GitStyle branching for local PostgreSQL
Very interesting. I have the same issue day to day, so will definitely give this a shot! More on reddit.com
22
73
December 7, 2025How are you managing isolated Postgres database branches for preview deployments /CI?
For quick and cost effective solution, yes Vercel and Neon are the way to go. Docker and RDS are a great solution but, the evolution of tech always leans toward efficiency. Unless your project is massive, you are not outgrowing Vercel or Neon anytime soon. I think it's a great solution. More on reddit.com
18
7
June 9, 2026What is database branching?
Database branching creates an isolated Postgres environment from a selected source so teams can test code, schema, and data changes without modifying the original database.
vela.simplyblock.io
vela.simplyblock.io › database-branching
Database Branching for Postgres | Vela
Is database branching the same as database cloning?
Branching uses cloning as a primitive, but it adds workflow around the clone: naming, lifecycle, CI integration, access, review, and cleanup.
vela.simplyblock.io
vela.simplyblock.io › database-branching
Database Branching for Postgres | Vela
When should teams use database branching instead of shared staging?
Use branching when teams need isolation, production-like data shape, and repeatable lifecycle. Shared staging can still be useful for long-running integration environments, but it should not be the only validation path.
vela.simplyblock.io
vela.simplyblock.io › database-branching
Database Branching for Postgres | Vela
Videos
11:13
Getting Started with Database Branching - YouTube
01:07
What is Postgres Branching? The Future of Database Testing & ...
01:03
What is Database Branching in PostgreSQL? - YouTube
06:34
A Postgres database for every GitHub branch 🤝 GitHub branching ...
01:08
How to Speed Up Dev Testing with PostgreSQL Database Branching ...
03:31
Data drop: Branching and deploy requests - YouTube
PlanetScale
planetscale.com › docs › postgres › branching
Branching - PlanetScale
When your PostgreSQL database is first initialized, a single production branch is created called main which acts as the default branch. You can then create development branches that you can use for development before shipping schema changes ...
Hacker News
news.ycombinator.com › item
Pg_branch: Experimental Postgres extension brings Neon-like branching | Hacker News
October 10, 2023 - I think this should be really straightforward by using one database as a template for another. This is how Postgres's create database works and it defaults to Template1 · https://www.postgresql.org/docs/current/manage-ag-templatedb
Reddit
reddit.com › r/postgresql › gitstyle branching for local postgresql
r/PostgreSQL on Reddit: GitStyle branching for local PostgreSQL
December 7, 2025 -
Hey, just wanted to share my tiny tool with the community.
This is an OSS CLI tool that helps you manage databases locally during development.
https://github.com/le-vlad/pgbranch
Why did I build this?
During the development, I was quite often running new migrations in a local feature branch; sometimes they were non-revertible, and going back to the main branch, I realized that I had broken the database schema, or I just needed to experiment with my data, etc.
This is a simple wrapper on top of PostgreSQL's CREATE DATABASE dbname TEMPLATE template0;
Appreciate your thoughts on the idea.
Neon
neon.com › branching
Database Branching Workflows - Neon
A new paradigm for managing Postgres. Instantly create, test, preview, and roll back environments with Neon’s powerful database branching.
PostgresAI
postgres.ai › blog › 20250721-dblab-engine-4-0-released
DBLab 4.0: instant database branching with O(1) economics | PostgresAI
July 21, 2025 - Traditional database management makes this prohibitively expensive. DBLab 4.0 makes it effectively free – same cost whether you run 1 experiment or 1,000. Before diving into the new features, here's how DBLab's terminology maps to practical usage: ... # Create a clone to work with dblab clone create --branch main --id my-clone-id --username postgres --password <your-password> # Connect to your clone and make some changes psql -h localhost -p 6001 -U postgres # port may be different ...
Filip-prochazka
filip-prochazka.com › blog › database-branching-in-postgresql
Database branching (just like with git) in PostgreSQL
November 8, 2021 - If only you could just magically revert the database to where it was before you’ve started changing the schema. Sadly, PostgreSQL does not have a real branching feature. But it has something that can be used as such - the CREATE DATABASE command.
Vela
vela.simplyblock.io › database-branching
Database Branching for Postgres | Vela
Give developers and CI pipelines isolated, production-like Postgres environments for every meaningful change. Vela turns database branching into a platform workflow: create a branch, validate code and schema changes, review the result, then clean it up without relying on a shared staging database.
Postgres FM
postgres.fm › episodes › database-branching
Postgres FM | Database branching
November 11, 2022 - Nikolay and Michael discuss database branching — how to define it, and the current state of tools and approaches.
Xata
xata.io › blog › neon-vs-supabase-vs-xata-postgres-branching-part-1
Neon vs Supabase vs Xata: Postgres Branching Compared
April 3, 2026 - Supabase integrated database branching with git workflows, providing full-stack preview environments for every feature branch. With our new PostgreSQL platform at Xata, we’ve reimagined branching from the ground up to address the limitations we saw in existing solutions.
Vela
vela.simplyblock.io › blog › database-branching-is-dead
Database Branching is Dead. Long Live Database Branching. |…
February 22, 2026 - Most “database branching” solutions fall into the same trap: they optimize for “looks like a branch” instead of “behaves like a branch.” · To me, the biggest offender is this schema-as-branch approach. It looks tempting at first because it’s cheap and it fits inside one PostgreSQL instance.
Vercel
vercel.com › docs › storage › vercel-postgres › limits
Postgres on Vercel
January 13, 2026 - Vercel lets you connect external Postgres databases through the Marketplace, allowing you to connect external Postgres databases to your Vercel projects without managing database servers.
PostgreSQL
postgresql.org › about
PostgreSQL: About
Below is an inexhaustive list of various features found in PostgreSQL, with more being added in every major release: ... Procedural Languages: PL/pgSQL, Perl, Python, and Tcl. There are other languages available through extensions, e.g. Java, JavaScript (V8), R, Lua, and Rust · SQL/JSON constructors, query functions, path expressions, and JSON_TABLE · Foreign data wrappers: connect to other databases or streams with a standard SQL interface
Wikipedia
en.wikipedia.org › wiki › PostgreSQL
PostgreSQL - Wikipedia
June 4, 2026 - Neon: An open-source, serverless implementation of PostgreSQL that separates storage and compute to offer modern development features like database branching.
PostgreSQL
postgresql.org
PostgreSQL: The world's most advanced open source database
PostgreSQL is a powerful, open source object-relational database system with over 35 years of active development that has earned it a strong reputation for reliability, feature robustness, and performance.
DEV Community
dev.to › semaphore › a-first-look-at-neon-a-postgres-database-that-branches-10e6
A First Look at Neon: A Postgres Database That Branches - DEV Community
March 6, 2023 - Head: the new branch is a copy of the current database. Time: the branch has the parent's data up to a specified date and time. LSN: the branch has the parent's data up to a specified log sequence number. The create branch UI. Endpoints for the branches can be created on the same screen or on the Endpoints page. Neon is a PostgreSQL database, so we'll need to install the client tools.
GitHub
github.com › sastraxi › pgsh
GitHub - sastraxi/pgsh: Branch your PostgreSQL Database like Git · GitHub
Finding database migrations painful to work with? Switching contexts a chore? Pull requests piling up? pgsh helps by managing a connection string in your .env file and allows you to branch your database just like you branch with git.
Starred by 602 users
Forked by 16 users
Languages JavaScript 99.8% | Shell 0.2%
Reddit
reddit.com › r/sql › how are you managing isolated postgres database branches for preview deployments /ci?
r/SQL on Reddit: How are you managing isolated Postgres database branches for preview deployments /CI?
June 9, 2026 -
Hey everyone, I’m looking at workflows to optimise how we spin up staging databases for app previews. I’ve been experimenting Neon’s serverless architecture (specifically looking at how Databricks integrates it for Lakebase) to use its instant database branching.
Being able to use a Vercel integration to automatically spin up an isolated database branch for a preview deployment, run schema migrations, test a data app and tear it down without duplicating storage costs or impacting production seems like a massive win for modern dev.
For those running serverless Postgres in production, are you relying heavily on these types of branching workflows, or are you still doing it in the old fashioned way with Docker or isolated RDS staging instances.
Top answer 1 of 8
1
For quick and cost effective solution, yes Vercel and Neon are the way to go. Docker and RDS are a great solution but, the evolution of tech always leans toward efficiency. Unless your project is massive, you are not outgrowing Vercel or Neon anytime soon. I think it's a great solution.
2 of 8
1
hi u/Shanjun109 One thing worth flagging, since the thread is all Neon/Lakebase: that branching model assumes your production already lives on Neon. If you're running prod on RDS, Aurora, or Cloud SQL (which it sounds like you might be) getting that workflow means migrating your primary onto Neon first. The copy-on-write mechanics people are describing are right, though. If you want the workflow without moving production, leave prod on RDS and let a separate system maintain a continuously replicated copy in sync. Branches are copy-on-write forks of that copy, Xata does exactly this. (Full disclosure: I work there, so salt to taste.) There was a comment about data masking, and that's the actual gotcha with prod preview branches. Clone real prod data and you've now got PII sitting in N ephemeral databases that preview apps and CI logs can reach. Xata can anonymize the data when the production clone is created so the PII never lands in the branch. Branching beats Docker and RDS clones for prod-shaped previews. I agree with the thread there. Just nail down whether your option needs you to migrate prod first and how you handle anonymization, because that's the line that actually decides it for most teams.