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
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!
LobeHub
Can this work with existing apps, or does the app need to be built on InsForge from the start?
InsForge
@rika_lee1 It doesn’t have to be a brand-new app, but the backend you want to branch needs to be on InsForge.
An existing frontend can point to an InsForge backend / branch. The branching layer is for backend state, not for replacing the whole app.
How do you represent auth-provider changes in the diff?
InsForge
@jackiesong We represent auth-provider changes as config diffs in the merge preview.
Mergeable auth config can be reviewed before merge, while environment-specific values like OAuth secrets / API keys stay separate and are not blindly pushed to prod.
APIPark
I have seen too many AI coding demos stop at the frontend. This tackles the scarier backend part.
InsForge
@frey_loong exactly. Frontend demos are the easy part. Backend state is where mistakes get expensive, so we wanted agents to have a real backend to work on without touching production.
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 ❤️
neon figured out database branching for postgres specifically and it's genuinely useful. doing it for the full backend stack, database plus storage plus auth plus edge functions, is a meaningfully harder problem. curious whether all those components branch atomically or whether there's a coordination layer that can get out of sync