Spatial Branches
Git for the Physical World
Branch the live spatial state, design and simulate changes in isolation, then review and merge — with full history and a complete audit trail. Move fast without ever breaking the world of record.
How Spatial Branches Work
Branch, Review, and Merge the Live World
Spatial Branches brings the git workflow to physical space. Fork the live world into an isolated branch, make and stage spatial edits, open a merge request, review the spatial diff, then merge back into main — with full history and an audit trail.
- 01
Branch the World
Fork the live state into an isolated branch.
- 02
Stage Edits
Add, move, and remove entities; every change is tracked.
- 03
Merge Request
Propose the branch for review.
- 04
Review Changes
Inspect the spatial diff and approve.
- 05
Merge to Main
Promote to the live world with full history.
Legacy Challenges
Why Editing the Live World Is Risky
Traditional GIS edits the system of record in place. There's no safe sandbox to try a change, no way to compare scenarios side by side, and no clean trail of who changed what — so teams move slowly and cautiously.
No Safe Sandbox
Changes hit the live state directly, so experimenting means risking the system everyone depends on — or copying data into a disconnected file.
Core Capabilities
Branch, Review, and Merge the World
Spatial Branches brings the discipline of version control to physical space — isolated work, reviewable diffs, and safe merges into the live state.
Fork the live world
Create an isolated branch of the spatial state in one click. Design, edit, and simulate freely without touching the system of record.
Product Benefits
Move Fast Without Breaking the World
Give teams a safe place to design and simulate, a clear way to review change, and a complete record of everything that happened.
Experiment without risk
Branch, try bold changes, and discard freely. The live world of record is never exposed to work in progress.
Compare scenarios side by side
Hold multiple design options against the same baseline and diff them, so decisions are made on evidence, not memory.
Audit every change
Every edit is attributed and reversible, giving compliance and stakeholders a defensible history of how the world evolved.
Feature Details
Version Control for Spatial State
Spatial Branches applies the proven branch-review-merge model to the live physical world, backed by the versioned DataStore.
One-Click Branch
Fork the entire spatial state instantly into an isolated workspace that shares nothing with the live world.
Scenario Branches
Keep several competing designs alive at once, each a full branch from the same baseline.
Agent Branches
Let the agent work on a branch, so autonomous redesign happens safely off to the side.
Related Products
Explore the Spatial AI OS
One platform for all spatial data and workloads, from design to field operations.
FAQ
Get the Facts About Spatial Branches
Read the DocsThey bring git-style version control to the physical world. You branch the live spatial state, work in isolation, then review and merge — with conflict detection, full history, and an audit trail of every change.
A branch is a sandboxed copy of the spatial state backed by the versioned DataStore. Edits, simulations, and agent work on a branch never touch the system of record until the branch is merged.
It shows exactly what changed against the baseline — entities added, moved, or removed — both on the map and as a reviewable change list, so approvals happen with full context.
An approved branch is promoted into the live state with conflict detection, and the merge is recorded in full history so it can be inspected or reversed later.