InsForge (YC P26) is an open-source Apache 2.0 backend platform acting as a Heroku-like deployment and operations layer
We started InsForge because we just wanted our Claude Code to handle all the backend / infra stuff for us, instead of us jumping between dashboards doing manual config, or copy paste logs and docs back to agents.
We first tried creating a folder with bunch of .MD files, and installing MCPs like Supabase, Vercel, GitHub, Context7. But soon we found MCPs have their own problems: (a) Tools get pre-loaded into context, before agents even do anything (b) bad design, payloads are returning 10k+ tokens, and (c) a lot of stuff still canβt be done by MCP: e.g. telemetry and configs.
So we think, because coding agents are so good at CLI, why not just put everything in CLI and create Skills to teach them how to use it?
Thatβs InsForge: 1 command to install our CLI + Skills, coding agents can run the entire backend platform [1].
We started with authentication and database, but we kept adding more primitives we wanted, so now we have: - frontend hosting - backend servers (mi