InsForge
The agent-native cloud infrastructure platform
1.8K followers
The agent-native cloud infrastructure platform
1.8K followers
InsForge is the agent-native alternative to AWS.
This is the 3rd launch from InsForge. View more
InsForge Backend Branching
Launching today
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
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.
sounds very interesting! do we get merge conflict here as well? :D
InsForge
@ashishkingdom Yes we do! We can branch diff so you can easily tell what did the agent do.
Congratulations! This feels like a missing primitive for agentic development.
Do you plan to support protected-branch-style policies for backend changes? Especially, to stop agents from modifying RLS, auth, billing schemas, or other high-risk areas without human approval?
Feels like backend governance is the natural next layer after diffs.
InsForge
@jesecamilo Thanks for your feedback! We would definitely consider that to make a safer agentic development workflow!
InsForge
Hey guys! I'm @tonychang430 , co-founder of InsForge 👋
Coding agents are getting incredibly good at building software. The problem isn't capability anymore! It's trust.
Most people still hesitate before letting an agent touch production. And honestly, they should. One bad migration, one accidental deletion, or one wrong configuration can take down critical infrastructure in seconds.
We believe the future isn't about replacing humans. It's about giving humans confidence in what agents are doing.
That's why Backend Branching is so exciting to us.
Instead of giving agents direct access to production, every change happens inside an isolated backend branch!
It is a complete clone of your backend, including your database, auth, storage, functions, and configuration.
Agents can move fast, experiment freely, and build against a real environment without putting production at risk.
Then, just like a pull request for code, humans stay in control. You can review the exact changes, approve them, reject them, or ask the agent to fix conflicts before anything reaches production.
Our vision is simple: agents should be able to move at machine speed while humans maintain visibility, control, and trust.
We're excited to hear what you think and would love any feedback from the Product Hunt community ❤️
YouMind
Congrats on the launch!
This is such a smart way to solve the production safety issue with coding agents. Giving them an isolated backend to test changes is a huge game changer. I have a quick question: how does the system handle massive databases? If our production database is extremely large, does spinning up a new branch clone all that data, or does it use seed data instead?
InsForge
@jaredl We support both `full` and `schema-only` modes. Full copies schema + data at T0 for realistic testing; schema-only copies the schema and backend config but leaves user-data tables empty, so it’s much lighter for huge prod DBs. Then you can add seed/test data for the agent.