Show HN: InsForge – Open-source Heroku for coding agents

Published: (May 18, 2026 at 11:40 AM EDT)
2 min read

Source: Hacker News

Introduction

Hi HN, I’m Hang, co‑founder of InsForge (YC P26). InsForge is an open‑source “Heroku for AI coding agents”: a backend platform designed for coding agents to deploy, operate, and debug end‑to‑end. It is released under the Apache 2.0 license (GitHub repository). Quick demo: .

Motivation

We built InsForge because we wanted our Claude Code agent to handle all backend/infra tasks without us having to jump between dashboards, manually configure settings, or copy‑paste logs and documentation back to the agents.

Our initial attempt involved creating a folder of .md files and installing MCPs (Supabase, Vercel, GitHub, Context7). We quickly ran into issues:

  1. Tools were pre‑loaded into context before the agents could act.
  2. Poor design caused payloads to exceed 10 k tokens.
  3. Many tasks (e.g., telemetry, configuration) could not be performed via MCPs.

Since coding agents excel at CLI interactions, we decided to put everything in a CLI and create Skills to teach them how to use it.

What InsForge Provides

Installation

A single command installs the CLI and the required Skills, enabling coding agents to run the entire backend platform:

  • Documentation:

Core Primitives

We started with authentication and a database, then added more primitives:

  • Frontend hosting
  • Backend servers (microVM‑based) – see
  • Database
  • Authentication
  • Storage
  • LLM model router
  • Cron jobs
  • Realtime features
  • Edge functions
  • Vector storage

Reliability Features (inspired by real backend engineers)

  • Backend branching – Agents often make mistakes (e.g., deleting a database). Inspired by Neon, we branch the entire backend (DB, auth, storage, functions, schedules). Agents work on a branch; you review diffs and decide to merge or discard. Details:
  • Server telemetry – Agents can read logs, CPU, memory, and disk usage to detect spikes and root causes themselves.
  • Debug agent – Each project gets a dedicated debug agent. Your coding agent can ask “why did deployment fail?”; the debug agent runs diagnostics, finds root causes, proposes fixes, and returns the answer. More info:
  • Backend advisor – Scans your backend daily for security and performance issues, proposes remediations, and forwards them to your coding agent. See

Try It Out

  • InsForge Cloud:
  • Source code:

We’re a small team and read every comment. Let us know what’s good, what sucks, and what’s missing—we love feedback!

0 views
Back to Blog

Related posts

Read more »

Click

Article URL: https://clickclickclick.click/ Comments URL: https://news.ycombinator.com/item?id=48187054 Points: 158 Comments: 28...