Workflow: dev, staging, and prod as Neon branches

TL;DR

Staging is a long-lived child branch of prod, refreshed nightly via reset from parent. Developers get personal branches from staging or prod, with expiration set (7 days) and anonymization if they carry prod data.

Steps

1. Production lives on the default (root) branch. Mark it protected.
2. Staging is a long-lived child branch of prod, refreshed nightly via reset from parent.
3. Developers get personal branches from staging or prod, with expiration set (7 days) and anonymization if they carry prod data.
4. Promote by merging code and resetting staging from prod, not by copying data upward; data flows down, code flows up.
5. Scope IP Allow to protected branches so prod is locked down while dev branches stay accessible.

When to use

You are seeing this: Dev, staging, and production as branches of one Neon project, with data flowing one direction. Use this skill when you run into "Workflow: dev, staging, and prod as Neon branches".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Neon's branch management docs (verified live 2026-09-26): branch hierarchies, protected branches, reset from parent for refreshes, branch expiration, and IP Allow scoping to protected branches; Neon's branching workflow guides document the production/staging branch model.