InsForge
An agent-operable backend for taking full-stack apps from code to deployment.
- Source repo
- InsForge/InsForge
- Stars
- ★ 13k
- Last updated
- 3d ago
- License
- Apache-2.0
- Primary language
- TypeScript
- FA score
- 46/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformOpenAI API
- Cost
- Free tier plus a paid hosted plan
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- A developer using an MCP-compatible coding agent to build a full-stack app and needing that agent to inspect schemas and logs before changing backend resources.
- Not a fit if
- Teams that don't want to manage Docker and port config
- Production teams needing Compute long-running containers (private preview)
- Users wanting the S3-compatible gateway with default local storage
- Source review
- 46/100 · Major gaps 2 safety controls not found
What does this agent do, and when should you use it?
InsForge is an open-source backend platform for agentic coding, combining authentication, Postgres, storage, edge functions, a model gateway, compute, and site deployment. Coding agents can use it through an MCP Server in self-hosted or cloud environments; the cloud offering also includes CLI + Skills. Its MCP operations let agents inspect documentation, schemas, deployed-function metadata, bucket contents, auth configuration, and runtime logs before changing backend resources. Self-hosting uses Docker Compose, with local filesystem storage by default and optional S3-compatible backends. It fits teams that want coding agents to operate application infrastructure as well as write application code.
A coding agent interacts with InsForge through the InsForge MCP Server, or through cloud-only CLI + Skills from a terminal. It can read backend context, database schemas, resource metadata, and runtime logs, then deploy edge functions, run database migrations, create storage buckets, and configure auth providers. The platform provides a Postgres relational database, S3-compatible file storage, an OpenAI-compatible Model Gateway across multiple LLM providers, Edge Functions, private-preview Compute, and site build/deployment. A self-hosted instance starts with docker compose -f docker-compose.prod.yml up; when backed by S3-compatible storage, /storage/v1/s3 exposes an S3-compatible gateway.
- A developer using an MCP-compatible coding agent to build a full-stack app and needing that agent to inspect schemas and logs before changing backend resources.
- A team that wants to run its backend platform locally or on its own host using Docker Compose.
- A developer running several isolated local projects by assigning separate environment files, ports, and Compose project names.
- A team that needs an S3-compatible storage interface and can connect bundled or external S3-compatible storage.
- An application developer who needs an OpenAI-compatible gateway intended to work across multiple LLM providers.
How do you install or deploy this agent?
Self-hosting requires Docker and Node.js. Run:
git clone https://github.com/InsForge/InsForge.git
cd InsForge
cp .env.example .env
docker compose -f docker-compose.prod.yml upThen open http://localhost:7130 and follow the UI steps to connect the InsForge MCP Server. The supplied material does not specify the exact MCP credentials or configuration fields. To use bundled MinIO or RustFS, add docker-compose.minio.yml or docker-compose.rustfs.yml respectively; set the corresponding access keys in .env before production use.
How do you use this agent?
After connecting the MCP Server, send your coding agent: I'm using InsForge as my backend platform, call InsForge MCP's fetch-docs tool to learn about InsForge instructions. The agent can then use MCP operations to inspect platform documentation and backend state, and to deploy functions, run migrations, create buckets, or configure authentication. CLI + Skills are also documented for the cloud offering, but the supplied material does not provide installation, authentication, or command details for that path.
What are this agent's strengths and limitations?
- Its MCP Server exposes both backend inspection and configuration operations to MCP-compatible coding agents.
- The documented product scope combines authentication, Postgres, storage, edge functions, a model gateway, compute, and site deployment.
- It offers self-hosting plus local filesystem storage and several S3-compatible storage paths, including an S3-compatible gateway when configured.
- The Model Gateway is described as OpenAI-compatible and usable across multiple LLM providers.
- Self-hosting requires Docker and Node.js, and the operator is responsible for environment configuration and port management.
- CLI + Skills are cloud only, so the documented self-hosted agent interface is the MCP Server.
- Compute is marked private preview, so it should not be assumed to be generally available.
- The S3-compatible gateway is enabled only with an S3-compatible backing store; the default local filesystem storage does not provide it automatically.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| InsForge This agent | 46 · Major gaps | Self-hosted serviceFreemium | ★ 13k | 3d ago | TypeScript | OpenAI API |
| fx Coding Agent | 63 · Some gaps | CLIFree + model costs | ★ 3.8k | today | Zig | ChatGPT · Codex · OpenAI API |
| Chorus Agent Harness | 55 · Major gaps | CLIFree + model costs | ★ 1.2k | today | TypeScript | Codex · Claude Code |
| CloudBase AI Toolkit | 59 · Major gaps | Agent plugin / skillFreemium | ★ 1.2k | 1d ago | TypeScript | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows: README describes MCP server and CLI interfaces, but does not specify permission model or least privilege; setup script generates secrets and sets file permissions 600, but no user confirmation mechanism; data flow transparency is limited; sensitive data handling is not detailed; dependency security is addressed via overrides pinning versions, but no audit evidence; external effects are not fully documented; no rollback mechanism; source attribution is present but publisher unverified. Deductions: lack of user confirmation, insufficient data flow transparency, missing sensitive data handling details, no rollback, unverified publisher.
Evidence shows: README and package.json are consistent; dependencies are listed with overrides, but no lockfile or integrity checks; failure messages are present in test scripts but not documented for users. Deductions: dependency integrity not verified, failure message documentation missing.
Evidence shows: README identifies target audience and scenarios, provides multiple deployment options, but lacks explicit capability boundaries and trigger precision; environment fit is good with multiple storage backends and platforms. Deductions: capability boundaries and trigger precision not detailed.
Evidence shows: README is well-structured with quickstart, docs, community; install notes are detailed; naming is consistent; examples provided but no FAQ; known limitations not listed; license is Apache-2.0 with full LICENSE; versioning exists but no CHANGELOG; maintenance responsibility is clear with contributing guide and support channels. Deductions: missing FAQ, known limitations, CHANGELOG.
Evidence shows: Output usability is good with clear deployment instructions, but no actual output examples; marginal value is high as an all-in-one platform, but no comparison; cost-benefit is open-source free, but no performance data. Deductions: missing output examples, comparison, performance data.
Evidence shows: Claims in README lack implementation details or test evidence; cross-source corroboration is not provided; facts and inferences are mixed. Deductions: claims not traceable, no independent verification, facts and inferences not separated.
- Not found in source: confirmation before actingTurn on (or add) a confirmation step before it acts, and try it in a sandbox or test environment before real data.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- Publisher identity is unverified; assess supply chain risks carefully.
- Setup script generates sensitive secrets; ensure trusted environment and secure .env file.
- Dependencies are pinned via overrides but no lockfile; use npm ci or similar to ensure integrity.
- Feature claims lack test evidence; perform independent verification before deployment.
Recent releases
Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.
-
Release notes excerpt
What's Changed * fix(deps): resolve critical/high Dependabot alerts (proxy-addr, shell-quote, source-map-js) by @tonychang04 in https://github.com/InsForge/InsForge/pull/2136 * chore(yun-tianming): drop dead types, trim narration, fix doc drift by @Fermionic-Lyu in https://github.com/InsForge/InsForge/pull/2146 * fix(deps): patch Dependabot alerts by @tonychang04 in https://github.com/InsForge/InsForge/pull/2147 * fix(storage): default owner policies on storage.objects for projects created before their first bucket by @v01dstar in https://github.com/InsForge/InsForge/pull/2151 …View on GitHub ↗ -
Release notes excerpt
What's Changed * ci: let the OpenAPI validate step handle more than one changed spec by @Fermionic-Lyu in https://github.com/InsForge/InsForge/pull/2112 * chore(yun-tianming): drop dead modules/exports, fix OpenAPI and doc drift by @Fermionic-Lyu in https://github.com/InsForge/InsForge/pull/2111 * fix(database): stop forwarding the client Connection header to PostgREST by @Fermionic-Lyu in https://github.com/InsForge/InsForge/pull/2119 * fix(logs): return the newest CloudWatch logs for busy projects by @Fermionic-Lyu in https://github.com/InsForge/InsForge/pull/2123 …View on GitHub ↗ -
Release notes excerpt
What's Changed * chore(deps): clear 3 of 4 Dependabot alerts (browserslist, @humanfs/node, fflate) by @tonychang04 in https://github.com/InsForge/InsForge/pull/2048 * chore(deps): vitest 4.1.11, nodemailer 9.1.1, js-yaml 4.3.2 by @tonychang04 in https://github.com/InsForge/InsForge/pull/2057 * chore(deps): bump qs and body-parser by @dependabot[bot] in https://github.com/InsForge/InsForge/pull/2061 * docs(readme): add ZopDay to the One-click Deployment table by @muskanbandta23 in https://github.com/InsForge/InsForge/pull/2078 …View on GitHub ↗
FAQ
Can InsForge be self-hosted?
What kind of coding agent can connect to it?
Is the default storage S3-compatible?
/storage/v1/s3 gateway is enabled when InsForge is backed by an S3-compatible store.Does the model gateway lock me to OpenAI?
What does self-hosting cost and what credentials are required?
.env; other credential details are not specified.