InsForge
github.com/insforge/insforge- Category
- Developer Tools
- Rank
- No. 765Tools index
Previous survey · No. 754 ·
- Type
- APP
- Builder
- insforge
- GitHub
- 13.0k stars
- Latest release
- v2.3.2
- Date
About
An all-in-one, open-source backend platform built for agentic coding.
What it does
InsForge gives coding agents direct control over a full application backend. Through MCP, or a cloud-only command line with Skills, agents can inspect schemas and logs, run migrations, configure authentication, manage storage, deploy edge functions, and work with Postgres, model APIs, compute, and site hosting.
Why it's ranked here
The appeal is unusually broad operational coverage through agent-friendly interfaces. An agent can read live backend state, change resources, verify deployments, and inspect failures without handing each task back to a human. The case is tempered by cloud-only command-line access and compute remaining in private preview.
What's good
Self-hosting uses Docker Compose and includes Postgres, an automatically generated REST API, the main backend, and a Deno function runtime. Storage supports local files or S3-compatible services. The model gateway follows the OpenAI API shape, while shared schemas cover database, authentication, storage, realtime, payments, deployments, schedules, and compute.
Tradeoffs
The command-line and Skills interface is cloud-only, although MCP works in both deployment modes. Long-running compute is still a private preview. Self-hosters must manage secrets, ports, TLS, backups, upgrades, and container infrastructure. Local storage is the default, while production object storage needs separate S3-compatible configuration and careful credential handling.
How to use it well
Use InsForge when a coding agent should build and operate the backend as part of one continuous workflow. MCP is the natural choice for self-hosted projects; cloud users can also use the command-line interface and Skills. It does not replace the coding agent itself, and self-hosting does not remove routine infrastructure and security work.
Technical notes+
The root package.json defines an npm 11 workspace monorepo spanning backend, frontend, and packages/*, orchestrated with Turbo and TypeScript tooling. packages/shared-schemas/src/index.ts exposes schemas for database, auth, storage, AI, logs, functions, realtime, deployments, schedules, payments, compute, telemetry, and more. packages/dashboard/src/index.ts exports the dashboard and its public types, while packages/dashboard/src/types/index.ts models separate self-hosted and cloud-hosted modes with a discriminated InsForgeDashboardProps union. packages/ui/src/index.ts and packages/ui/src/components/index.ts expose a reusable component surface. docs/deployment/README.md describes a four-service architecture: PostgreSQL, PostgREST, a Node.js backend serving the dashboard, and a Deno runtime. docs/deployment/deploy-to-coolify.md explains that Postgres is built from repository configuration because required files cannot safely use Coolify bind mounts.
Observed
- License
- Apache-2.0
- Primary language
- TypeScript
- Package management
- npm 11 workspace monorepo with backend, frontend, and packages workspaces
- Interfaces
- MCP server for cloud and self-hosting; CLI with Skills for cloud; OpenAI-compatible model API
- Self-hosting
- Docker Compose with PostgreSQL, PostgREST, Node.js backend, and Deno runtime
- Storage support
- Local filesystem by default, with S3-compatible backends and gateway support
- Deployment surface
- Cloud-hosted service, Docker Compose, and one-click Railway, Zeabur, and Sealos options
Read from README.md, package.json, packages/ui/src/index.ts, packages/dashboard/src/index.ts, packages/shared-schemas/src/index.ts, packages/ui/src/lib/index.ts, packages/ui/src/components/index.ts, packages/dashboard/src/types/index.ts, packages/dashboard/src/router/index.ts, packages/dashboard/src/components/index.ts, docs/README.md, docs/asset-guidelines.md, docs/deployment/README.md, docs/deployment/deploy-to-aws-ec2.md, docs/deployment/deploy-to-coolify.md.
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.