Work away from production. Open a branch in the Dashboard, edit freely, then review and merge everything back when it's ready.
The full lifecycle
Split off, make changes in isolation, merge back — scroll to watch it happen.
Isolated from production until you merge
Typical time to open a new branch
Branches opened by early access teams
Faster reviews with field-level diffs
Open a branch
Every branch starts the same way as everything else in Cairn — a couple of clicks in the Dashboard. Pick a starting point, name it, and start editing. Nothing you touch there reaches production until you merge it back.
Review before you merge
Every branch produces a real diff — field by field, document by document — reviewed right in the Dashboard, so you know precisely what a merge will change before it happens.
Why teams switch
A branch is a full working copy of your content — edits, drafts and structure changes stay contained until you merge.
Cairn checks a branch against the current state of main and flags conflicts before you can merge, not after.
Every merge is recorded — who merged what, and when — so content history stays as clear as your schema history.
“We used to be terrified of touching content close to a launch. Now the editors just open a branch, and nothing they do can reach production by accident.”
Content team, early access partner
Works with your stack
Open your first branch in the Dashboard and edit without touching production.