InsForge is the backend built for agentic development. We offer everything AI agents need to build fullstack apps that scale. Our open source backend (2.3K stars on GitHub) provides databases, auth, storage, model gateway and edge functions accessible through a semantic layer that agents can understand, reason about, and operate end to end. Say the word, and you can deploy to InsForge Cloud or your own domain.
If you’re exploring agentic development—or migrating off legacy backends—InsForge is the platform that gives your agents the infra they need to tackle the heavy lifting.
Hey Product Hunt 👋 I’m @hanghuang, co-founder of InsForge.
Before starting InsForge, I was a Product Manager at Amazon and have always enjoyed building products and launching side projects to test new ideas.
InsForge is the backend built for agentic development — giving agents everything they need to ship fullstack apps, fast.
Most backend platforms are designed for human developers. But InsForge starts with agent experience.
Our platform (2.1K+ stars on GitHub) exposes backend primitives like databases, auth, storage, and functions through a semantic layer that agents understand, can reason about, and operate end to end:
With InsForge, your agent can:
Set up everything needed to ship fullstack apps
Launch and deploy your applications on a hosted or custom URL
Build applications that are secure and scale
Building on InsForge is faster and more reliable — up to 14% more accurate, 1.4x faster, and 2.4x more token efficient than SupaBase — as demonstrated in our MCPMark v2 benchmark.
We’re excited to share this with the Product Hunt community and can't wait to see what you build. Thanks for checking us out, and huge thanks to our hunter @chrismessina for hunting us🙏
@hanghuang@insforge@chrismessina Been running into exactly this with multi-instance setups. Agents don't really "get" the backend, they just guess at API shapes and hope for the best. How do your edge functions handle concurrency when multiple agents hit the same resources?
@insforge@chrismessina@hanghuang Oh nice, Deno's edge runtime is solid for that. Curious how it handles state between requests though, like if two agents hit the same function and need to coordinate. Is that all stateless or do you have some persistence layer?
@insforge@chrismessina@alan_silverstreams we’re working on persistent layer solution, will release something soon next quarter, and probably will launch again on product hunt haha
Report
@hanghuang@insforge@chrismessina Congrats on this, guys! For teams already deep in Supabase — existing tables, RLS policies, edge functions — is InsForge only a replacement or can it layer on top?
Report
@hanghuang Congrats on the launch! Quick question: how does InsForge handle data isolation?
Hey product hunt! @tonychang430 here, co-founder of InsForge.
Before starting InsForge, I was working at Databricks on the networking infrastructure team. One of the first projects I worked on was optimizing our cloud resources, and we ended up saving around $30K networking cost per month. It ended up just turning on private link to aws resources, which is a private link endpoint setup and a cloud configuration.
That experience taught me something important: just because something works doesn’t mean it’s scalable or designed the right way.
Over the past year, AI coding tools have gotten incredibly good at generating code. You can go from idea to prototype faster than ever. But shipping a real product still means dealing with databases, auth, storage, deployments, infrastructure, and a lot of configuration.
Most of these systems were designed for humans who understand every layer of the stack.
But agents don’t work that way.
We started asking a simple question:
What would a backend look like if it was designed for agents from day one?
That is why we built InsForge. It is a backend platform where agents can set up infrastructure, manage data, deploy applications, and operate everything end to end.
Humans are slower, make more mistakes, and usually need deep knowledge of every layer of the stack. Agents should be able to understand the system and get things done directly.
Our goal is simple.
Make agents the primary operators of software infrastructure.
Really excited to share this with the Product Hunt community. Happy to answer any questions and would love to hear what you think 🙏
The MCP integration is what sets InsForge apart. Instead of agents hallucinating API calls or guessing schema, they can actually fetch live backend context. That's a fundamentally smarter approach than just giving agents a README and hoping for the best.
@josie_oy Thanks! Great question. We built InsForge so tools like Cursor or Claude Code can actually operate the backend directly. The agent can understand the system through MCP and do things like create databases, set up auth, or deploy functions!
Benchmarks like MCPMark suggest big gains vs Supabase—what specific parts of your semantic layer or tool design drive those gains (fewer tool calls, smaller payloads, better introspection), and where do you still see agents struggle today?
@curiouskitty I think is how we expose the backend as structured data type for agents to self-introspect and use. And with this capability, agents can use the InsForge platform like human developers. Reasoning and fetching information (when needed), so their performance will be much higher!
As for struggles, I think definitely context, that's why we build this semantic layer.
The semantic layer approach is really smart — having agents reason about backend primitives rather than just calling APIs changes the whole development model. The fact that it works inside existing IDEs like Cursor and Claude with no new UI to learn is a big plus. Congrats on the launch!
@handuo Well said. As agents become part of the workflow, development itself needs to evolve. Agent-first thinking is the natural next step.
Report
The pgvector support (mentioned in the docs) is a great addition for teams building RAG applications. Having vector search built into the same Postgres instance as your relational data simplifies a lot of architecture decisions.
Replies
Raycast
Thrilled to back @hanghuang and the InsForge team on their Product Hunt launch.
InsForge is an AI‑native backend built for agents.
This isn't “AI bolted on,” this is starting with agent experience, and building on that foundation.
The unlock is a semantic layer that agents can actually read and act on.
Agents introspect policies and provision resources, so you can ship full‑stack apps end‑to‑end.
This adds up to:
Faster setup with npx. One install. Go build.
Agents working inside your IDEs (Cursor, Claude, etc.). No new UI to learn.
Benchmarked performance demonstrates higher accuracy, greater token efficiency, and lower latency.
If you’re exploring agentic development—or migrating off legacy backends—InsForge is the platform that gives your agents the infra they need to tackle the heavy lifting.
Get started now:
InsForge
@insforge @chrismessina thanks Chris for hunting us 🙏
InsForge
@hanghuang @insforge @chrismessina Thanks for hunting InsForge 🫡
InsForge
@hanghuang @insforge @chrismessina Honored to have you hunting us, Chris! Thanks for capturing the essence of InsForge so perfectly.
InsForge
Hey Product Hunt 👋 I’m @hanghuang, co-founder of InsForge.
Before starting InsForge, I was a Product Manager at Amazon and have always enjoyed building products and launching side projects to test new ideas.
InsForge is the backend built for agentic development — giving agents everything they need to ship fullstack apps, fast.
Most backend platforms are designed for human developers. But InsForge starts with agent experience.
Our platform (2.1K+ stars on GitHub) exposes backend primitives like databases, auth, storage, and functions through a semantic layer that agents understand, can reason about, and operate end to end:
With InsForge, your agent can:
Set up everything needed to ship fullstack apps
Launch and deploy your applications on a hosted or custom URL
Build applications that are secure and scale
Building on InsForge is faster and more reliable — up to 14% more accurate, 1.4x faster, and 2.4x more token efficient than SupaBase — as demonstrated in our MCPMark v2 benchmark.
To get started, head to your terminal and enter:
And use code INSFORGELW1 to get a month of InsForge Pro for $0.00!
👉 Got questions? Drop them below, or join our Discord.
We’re excited to share this with the Product Hunt community and can't wait to see what you build. Thanks for checking us out, and huge thanks to our hunter @chrismessina for hunting us🙏
InsForge
@hanghuang @insforge @chrismessina Join our discord and we respond under 1 min 👀
@hanghuang @insforge @chrismessina Been running into exactly this with multi-instance setups. Agents don't really "get" the backend, they just guess at API shapes and hope for the best. How do your edge functions handle concurrency when multiple agents hit the same resources?
InsForge
@insforge @chrismessina @alan_silverstreams we use the best service Deno! It is auto scaling capability and deployed on edge, so performance is shockingly good!
@insforge @chrismessina @hanghuang Oh nice, Deno's edge runtime is solid for that. Curious how it handles state between requests though, like if two agents hit the same function and need to coordinate. Is that all stateless or do you have some persistence layer?
InsForge
@insforge @chrismessina @alan_silverstreams we’re working on persistent layer solution, will release something soon next quarter, and probably will launch again on product hunt haha
@hanghuang @insforge @chrismessina Congrats on this, guys! For teams already deep in Supabase — existing tables, RLS policies, edge functions — is InsForge only a replacement or can it layer on top?
@hanghuang Congrats on the launch! Quick question: how does InsForge handle data isolation?
InsForge
@jerrybyday every project has its own isolated virtual machine! The strongest isolation haha
InsForge
Hey product hunt! @tonychang430 here, co-founder of InsForge.
Before starting InsForge, I was working at Databricks on the networking infrastructure team. One of the first projects I worked on was optimizing our cloud resources, and we ended up saving around $30K networking cost per month. It ended up just turning on private link to aws resources, which is a private link endpoint setup and a cloud configuration.
That experience taught me something important: just because something works doesn’t mean it’s scalable or designed the right way.
Over the past year, AI coding tools have gotten incredibly good at generating code. You can go from idea to prototype faster than ever. But shipping a real product still means dealing with databases, auth, storage, deployments, infrastructure, and a lot of configuration.
Most of these systems were designed for humans who understand every layer of the stack.
But agents don’t work that way.
We started asking a simple question:
What would a backend look like if it was designed for agents from day one?
That is why we built InsForge. It is a backend platform where agents can set up infrastructure, manage data, deploy applications, and operate everything end to end.
Humans are slower, make more mistakes, and usually need deep knowledge of every layer of the stack. Agents should be able to understand the system and get things done directly.
Our goal is simple.
Make agents the primary operators of software infrastructure.
Really excited to share this with the Product Hunt community. Happy to answer any questions and would love to hear what you think 🙏
InsForge
@tonychang430 let’s go man! Building the world-tier infrastructure for agentic development!
Gro
The MCP integration is what sets InsForge apart. Instead of agents hallucinating API calls or guessing schema, they can actually fetch live backend context. That's a fundamentally smarter approach than just giving agents a README and hoping for the best.
InsForge
@leo_aj Exactly! That’s why agents need agent-native infrastructure!
InsForge
@leo_aj Yes! We spend a LOT of time optimizing for the Agentic Experience! We believe Agentic experience is the new developer experience.
InsForge
@leo_aj Spot on, moving from static docs to live context is the jump from guessing to knowing for any serious agentic workflow!
InsForge
@leo_aj In the agent era, we need to rethink how we build — agentic development is key to adapting to the future!
Vozo AI — Video localization
Congrats on the launch! Would love to know how this integrates with tools like Cursor or Claude Code in real workflows
InsForge
@josie_oy Thanks! Great question. We built InsForge so tools like Cursor or Claude Code can actually operate the backend directly. The agent can understand the system through MCP and do things like create databases, set up auth, or deploy functions!
InsForge
@josie_oy please reach out if you need anything from InsForge team!
InsForge
@josie_oy We have InsForge MCP and Skills to help you connect smoothly. It works out of box for any agents!
Product Hunt
InsForge
@curiouskitty I think is how we expose the backend as structured data type for agents to self-introspect and use. And with this capability, agents can use the InsForge platform like human developers. Reasoning and fetching information (when needed), so their performance will be much higher!
As for struggles, I think definitely context, that's why we build this semantic layer.
Open source AND hosted? Best of both worlds.
InsForge
@shirley_mou open source is and will always be the core of InsForge
InsForge
@shirley_mou Open source is the key factor to build our community!
Naoma AI Demo Agent
InsForge
@dmitry_zakharov_aiThanks for the support! Really appreciate it.
InsForge
@dmitry_zakharov_ai thank you so much for the support!
InsForge
@dmitry_zakharov_ai Thank you so much!
Copus
The semantic layer approach is really smart — having agents reason about backend primitives rather than just calling APIs changes the whole development model. The fact that it works inside existing IDEs like Cursor and Claude with no new UI to learn is a big plus. Congrats on the launch!
InsForge
@handuo Thanks! We’re entering the era of agentic developments, so agent experience is the new developer experience
InsForge
@handuo Indeed! It's not just an api call. It's an entire backend ecosystem build for agents as primary operator!
InsForge
@handuo Well said. As agents become part of the workflow, development itself needs to evolve. Agent-first thinking is the natural next step.
The pgvector support (mentioned in the docs) is a great addition for teams building RAG applications. Having vector search built into the same Postgres instance as your relational data simplifies a lot of architecture decisions.
InsForge
@chelsea_yang Exactly! The reason we use postgres instance is because of it's extensions!
InsForge
@chelsea_yang yes, pgvector + our embedding pipeline make AI related workflow much easier to implement!