EN
Back to the archive

The archive · Developer & Business Tools · Product decision · 2025-2026

InsForge bets coding agents, not humans, are the backend's real users

InsForge rebuilds BaaS around AI agents as primary operators: MCP/CLI-first, Apache 2.0, YC P26, PH #1 and GitHub #1 trending in March 2026.

InsForge

The betThat backend infrastructure must be agent-native - MCP/CLI-first, structured, reversible - because coding agents will run entire applications, not just write code.Live

What the business is

InsForge is an open-source (Apache 2.0) backend platform that lets AI coding agents deploy and operate the full backend - Postgres, auth, storage, edge functions, model gateway, hosting - via one CLI and MCP tools.

How it started

Hang Huang (ex-Amazon PM, former pro League of Legends player) and Tony Chang (ex-Databricks network engineer) watched their coding agents stall on backend work: MCP servers for Supabase, Vercel, GitHub and Context7 bloated context windows with 10K+ token payloads and still hid core state like configs, logs, and runtime behavior. Their conclusion was that clouds were built for humans who know infrastructure, not for agents - so they rebuilt the stack with the agent as the primary operator.

What happened

InsForge ran an alpha in March 2026, joined YC's P26 batch, and launched 2.0 during Launch Week 1, taking #1 Product of the Day on Product Hunt and #1 trending on GitHub while stars climbed from 1,500 to 6,600+. It shipped Apache 2.0 with a self-hostable Docker Compose path, a built-in OpenAI-compatible model gateway, pgvector, and edge functions on Deno, then kept a CI-like release cadence - three releases in under three weeks in July-August 2026 - reaching roughly 12.7k stars by mid-August, per DEV.to.

How it ended up

Live and YC-backed: cloud at insforge.dev plus self-hosted Docker Compose with deployment parity; long-running Compute tier still in private preview.

Background

InsForge is an open-source backend platform designed for AI coding agents rather than humans. It bundles Postgres, auth, S3-compatible storage, edge functions, an OpenAI-compatible model gateway, and hosting behind one CLI and MCP toolset, so a coding agent can deploy, operate, debug, and scale a full-stack app end to end without a human touching a dashboard.

The founding bet came from experience: co-founders Hang Huang (ex-Amazon PM) and Tony Chang (ex-Databricks) found that MCP servers for Supabase, Vercel, and GitHub bloated their agents' context windows with 10K+ token payloads while still hiding the state agents need - telemetry, configs, logs, runtime behavior. They concluded that infrastructure built for humans was the bottleneck and rebuilt the stack around agents as primary operators, with structured outputs, scoped permissions, and reversible writes.

In March 2026 InsForge joined YC's P26 batch and launched version 2.0: the company reports #1 Product of the Day on Product Hunt, GitHub's #1 trending repository, and GitHub stars growing from 1,500 to 6,600+ in one month. The project is Apache 2.0 and self-hostable via Docker Compose with parity to the cloud tier, a deliberate hedge against lock-in for teams that want an exit route if the company disappears.

By August 2026 the repo sat at roughly 12.7k GitHub stars, with a release cadence of three feature releases in under three weeks. Independent coverage praised the MCP-first architecture but flagged the open questions: security guidance drifting from a fast-moving codebase, RLS policies written by agents, and whether the Compute tier for long-running containers will graduate from private preview.

What has to be true

  • The founders identified a real shift - coding agents becoming primary builders - and rebuilt infrastructure from that assumption rather than adding an AI adapter to a human-first product.
  • MCP-first design with structured outputs directly addresses the context-window and state-access problems that make agent backend work fail today.
  • Scoped permissions, reversible writes, and server-side secrets are concrete mitigations for handing agents infrastructure power, giving the bet a plausible security story.
  • Open source under Apache 2.0 with self-hosting parity creates a lock-in escape hatch, lowering the adoption barrier for teams wary of young infra companies.
  • Verifiable traction - PH #1 Product of the Day, GitHub #1 trending, and stars growing 4x in a month - shows developers recognized the problem.

What can be applied

When a genuinely new user class appears, bolting an adapter onto the old interface is not enough: rebuild the primary operating surface around the new user, and the old interface becomes the fallback.

Aftermath

As of September 2, 2026, InsForge is live: a hosted cloud at insforge.dev, a self-hostable Docker Compose distribution with deployment parity, and roughly 12.7k GitHub stars per an August 2026 review. It is in YC's P26 batch, shipped 2.x releases through August, and its Compute tier for long-running containers remains in private preview. Independent reviewers flag documentation drift relative to a fast-moving codebase - a real risk when docs double as the agent's operating manual - and the unresolved question of whether agents can be trusted to write correct row-level-security policies.

Sources

spotted an error? The archive wants to know.

Your turn

You just read one. Describe what you are building, and see who is betting on the same thing.

Free account · 3 free questions · no card

Related cases