Git-style branching for your entire backend. Spin off a branch to get a full, isolated copy of everything: your database, storage, auth, edge functions, and more, ready for your agents to experiment on without touching production.
Databases and servers cost a lot, if we create as much as we have have branches, how do we manage cost?
Do they sleep when not used ?
Report
neon figured out database branching for postgres specifically and it's genuinely useful. doing it for the full backend stack, database plus storage plus auth plus edge functions, is a meaningfully harder problem. curious whether all those components branch atomically or whether there's a coordination layer that can get out of sync
Replies
Pandada AI
The value is clearer when you say the branch includes database, auth, storage, functions, and config together.
iArt.ai
Does the branch copy production data, or can teams choose schema-only branching for privacy-sensitive apps?
PageOn.ai
I can imagine using this before every risky agent task: branch, let it build, inspect diff, then merge.
ApplySeed
neon figured out database branching for postgres specifically and it's genuinely useful. doing it for the full backend stack, database plus storage plus auth plus edge functions, is a meaningfully harder problem. curious whether all those components branch atomically or whether there's a coordination layer that can get out of sync
Vokal