InsForge: the open-source backend platform built for coding agents

Coding agents have made the front half of building an app fast. What still blocks launch is the backend chores: provision a server, create a database, wire up auth, configure storage, and work out deployment. A WhatsApp recommendation on 16 October placed InsForge exactly there: it packages those backend primitives into an open-source platform (TypeScript, Apache-2.0, about 13.1k stars and 1.2k forks as of 2026-10-16) that agents drive through MCP or a CLI — reading state and changing configuration the way a backend engineer would.

Core features

• Two interfaces, one capability set: an MCP Server (self-hosted or cloud) exposes InsForge’s operations as tools any MCP-compatible agent can call; the CLI + Skills (cloud only) let agents invoke them from the terminal.
• Six backend primitives: authentication (user management and sessions), a Postgres database, S3-compatible storage, a model gateway (an OpenAI-compatible API across multiple LLM providers), edge functions, and site deployment; Compute for long-running containers is marked private preview.
• Context for the agent, not just endpoints: agents pull documentation, schemas, metadata (deployed functions, bucket contents, auth configuration) and runtime logs — what writing code, verifying a build and debugging actually require.
• Self-hosting in one command: the official setup script writes the Compose files and secrets (JWT_SECRET, ENCRYPTION_KEY, POSTGRES_PASSWORD and the rest) into ~/insforge/.env (mode 600); re-running only adds COMPOSE_FILE and never touches values you have already set.
• Configure before starting: setup generates configuration without starting anything; after docker compose up -d, connect the MCP Server at http://localhost:7130.

Typical use cases

• A solo developer shipping full-stack with an agent: no more registering one service per primitive and stitching docs together.
• Teams already on Claude Code, Codex or Cursor: the agent creates buckets, runs migrations and configures auth providers over MCP while humans review.
• Studios standardizing their backend: the Compose file plus the .env template is a copyable internal platform.

Quick start

curl -fsSL https://raw.githubusercontent.com/InsForge/InsForge/main/deploy/setup.sh | sh -s ~/insforge
cd ~/insforge
$EDITOR .env          # set API_BASE_URL and VITE_API_BASE_URL to browser-reachable addresses
docker compose up -d

Open http://localhost:7130 and follow the guide to connect the MCP Server. If you would rather not self-host, the official cloud runs at insforge.dev.

Summary

For developers who want agent-driven full-stack delivery without assembling backend services by hand. It is not the tool for teams that already run a mature internal platform and need one primitive — InsForge ships the whole set, and adopting it means adopting its deployment and upgrade path. TypeScript, Apache-2.0, 13,128 stars and 1,224 forks as of 2026-10-16, last pushed 2026-10-13 — development is active. One note: the WhatsApp recommendation mentioned YC backing, which does not appear in the repository README, so this entry does not repeat that claim.

For other takes on packaging the engineering around agents, OpenResearch handles experiment orchestration where InsForge handles application backends; and for collapsing video, image and voice into one workspace, OpenCreator answers the other end.