InsForge

Give agents everything they need to ship fullstack apps

Open Source

Developer Tools

GitHub

Database

YC Application

The InsForge Skills concept (from the CLI blog post) is interesting. Giving agents pre-built skill modules for common backend tasks means less prompt engineering and more consistent results. Looking forward to seeing the skill library grow.

The multi-region deployment support is important for teams with global users. Having your backend close to your users reduces latency for realtime features and improves the overall user experience. Good to see it supported.

Congrats on the launch! Also checked the Github repo of InsForge and it looks promising too as the next potential viral repo hey :)

@aaron_epstein Check out our product hunt launch!

The idea of a semantic layer that agents can reason about is really compelling. As someone building developer tools, I know how frustrating it is when agents can't properly interact with your backend. Having databases, auth, and storage all designed with agent-first thinking could be a game changer. The 2.3K GitHub stars speak for themselves. Great launch!

Congrats on the #1 launch! For teams deploying private AI environments (on prem or private cloud), how does InsForge handle data residency requirements? Curious if there’s a self-hosted path beyond InsForge Cloud.

@hanghuang @tonychang430 Really interesting launch.

Reading through the architecture and the way InsForge exposes backend primitives through a semantic layer for agents, something stood out.

It seems to behave less like a traditional backend-as-a-service (like Supabase or Firebase) and more like infrastructure designed for agents to operate application backends directly.

Especially when agents can provision databases, deploy functions and manage resources without the human developer operating the stack.

Curious how the team thinks about this internally.

Is InsForge evolving primarily as a backend platform for developers using agents, or closer to infrastructure where agents themselves become the primary operators of the backend?

As someone who mostly dabbles in front-end and rarely backend, I'm always afraid I'll set up something wrong that causes a recursive loop and spikes my cloud or database cost somewhere. Are there ways that InsForge can also help with ensuring the code is cost-optimized as well?

Congrats on #1! The semantic layer approach is smart - agents that can reason about their own infrastructure instead of blind API calls is a big unlock. How are you handling auth scoping when multiple agents share the same backend? That's always been tricky in multi-agent setups.

I’m actually not a developer, but I was surprised by how simple InsForge is to use. The setup and interface make it much easier to experiment with AI tools and integrations without needing a deep technical background. It feels like the team really thought about usability, not just developer features. Excited to see where this goes! 🚀

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?

The model gateway feature is underrated. Being able to route to different LLM providers through a single OpenAI-compatible API, with usage tracked per project, is exactly what teams building AI-native apps need.