InsForge
The agent-native cloud infrastructure platform
2.2K followers
The agent-native cloud infrastructure platform
2.2K followers
InsForge is the agent-native alternative to AWS.
This is the 3rd launch from InsForge. View more
InsForge Backend Branching
Launched this week
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.
Launch Team / Built With
LobeHub
A concrete example of an agent making a risky migration safely inside a branch would be very persuasive.
InsForge
@thechaos A good example is schema + RLS + edge function changes. The agent can run the risky migration inside a backend branch, test against real backend APIs, then show a PR-style diff before anything touches prod.
Gro
Agentic coding needs guardrails like this. Speed without isolation is risky.
InsForge
@lily_liu8 Exactly. Agents can move incredibly fast, but backend state is where mistakes get expensive.
The goal is to give them a real backend to work against, while keeping production untouched until the changes are reviewed and merged.
InsForge
@lily_liu8 100%
This feels like a missing primitive for coding agents. Production should not be the first place an agent tests a backend change.
InsForge
@song_kirby Exactly. “Try it on production” does not make sense once agents are changing backend state.
We wanted Backend Branching to become that missing primitive: give the agent a real backend to test against, but keep production isolated until the changes are reviewed and merged.
InsForge
@song_kirby exactly! This is the future of agentic engineering
SocialEcho 2.0
The PR-style diff before merge is the part that really clicks for me. Agents can experiment, humans still approve.
InsForge
@eexlkuang_se Yes, that’s the core idea: let agents experiment freely, but keep the final decision human-reviewed.
The branch can carry real backend changes, and the merge preview makes those changes explicit before anything reaches production.
InsForge
@eexlkuang_se yep, human-in-the-loop is the most important part
Lessie AI
When using Claude Code or Cursor, backend state is usually the scary part. Branching the whole backend makes the workflow feel safer.
InsForge
@alexia_li Totally agree. With Claude Code or Cursor, frontend iteration is already fast, but backend changes need a safer loop.
That’s why we made the branch a full backend environment instead of just a database copy, so agents can test auth, storage, functions, and database changes without touching production.
InsForge
@alexia_li this is exactly why we built backend branching XD
How do you prevent a branch from drifting too far away from main?
InsForge
@mia_qiao we don’t auto-sync branches with main. A branch keeps its T0 baseline, then merge uses 3-way diff + conflict checks. If it drifts too far, reset the branch back to its create-time snapshot or recreate it.
InsForge
@mia_qiao since it's backend setup we don't expect the branch from drifting too far away.
But if it does actually happen, in the future we also plan on adding a rebase functionality.
For now users or agents just discard their branch and tell the agents to create a new one from main
Kollab
How conservative is the merge blocker when there is a potential conflict?
InsForge
@yan_labs_ If parent and branch both changed the same object since T0 and the result diverges, we block the merge instead of guessing.
The goal is to give your coding agent the conflict context, let it fix the branch, then retry the merge safely.