GraphCanon updated 1d · GitHub synced 1d · 26 views this month
Decision brief
InsForge is a comprehensive open-source backend platform built for developers wanting to deploy full-stack applications that include AI agents using agentic coding techniques.
Good fit when
- Use InsForge when your application requires an integrated stack, including database management, authentication services, storage solutions, and compute resources optimized for both traditional and AI-
- agent-based workflows. Especially beneficial if you're working in TypeScript.
Avoid when
- Avoid using InsForge if your development framework heavily relies on languages other than TypeScript as it's primarily built around the TypeScript ecosystem.
- Do not choose InsForge if your project needs a lightweight solution without the overhead of an all-in-one backend platform. It may introduce unnecessary complexity and resource consumption.
- Pricing:
- freemium - As an open-source platform under the Apache-2.0 license, InsForge is available freely for anyone to use, modify, and distribute without direct costs.
- Requirements:
- Min 4 GB RAM; Requires Docker; Requires Docker for self-hosted deployment.; Node.js needed for running locally from source.
Observed Jul 11, 2026 · Source: enrich:decision_facts
Verify the decision
Maintenance and security
Full trust report- Maintenance
- Very active (0d since push)
- As of 1d
- Provenance
- Not a fork · Organization account
- As of 1d
- Security (OSV)
- No lockfile
- As of 1mo
Public GitHub metadata and optional OSV scans. Signals, not a guarantee. Trust methodology.
Install
npm install InsForgeHow it fits your stack(6)
Typed graph edges - alternatives, integrations, successors, and dependencies. Ranked by relationship type, not raw GitHub stars.
Alternative
Integrates
Relationship graph
Optional deeper exploration of typed edges and category neighbours.
Similar tools
Same-category neighbours not already linked as typed edges.
Evidence and technical details
Sourced facts, taxonomy, compatibility claims, README excerpt, and machine-readable endpoints.
Overview
InsForge provides a comprehensive backend infrastructure, including database, authentication, storage, compute resources, hosting, and an AI gateway to facilitate the full-stack development of applications using AI agents.
Capability facts
- Deploy
- Self-host
Source: dockerfile:Dockerfile · Aug 20, 2026
- Docker
- Dockerfile present
Source: dockerfile:Dockerfile · Aug 20, 2026
- CLI
- CLI entrypoint
Source: package.json:bin|scripts · Aug 20, 2026
- MCP server
- No MCP server detected
Source: repo_scan · Aug 20, 2026
- Languages
- typescript, javascript
Source: github.language+package.json · Aug 20, 2026
Categories
Tags
README
Self-hosted: Docker Compose
Prerequisites: Docker with Compose v2.
1. Setup
curl -fsSL https://raw.githubusercontent.com/InsForge/InsForge/main/deploy/setup.sh | sh -s ~/insforge
Fetches the files the stack reads and generates JWT_SECRET, ENCRYPTION_KEY,
POSTGRES_PASSWORD, ROOT_ADMIN_PASSWORD, and the two access keys into
~/insforge/.env (mode 600). Nothing is started. Re-running refreshes the files
and keeps every value you have set — it only ever adds COMPOSE_FILE, or points
it at this checkout's compose file if it still names the development one.
cd ~/insforge
$EDITOR .env # API_BASE_URL, VITE_API_BASE_URL — the URL browsers will use
docker compose up -d
.env sets COMPOSE_FILE, so plain docker compose commands work from that
directory — no -f flags to remember.
[![Deploy on Docker][docker-btn]][docker-deploy]
Building from source instead
For working on InsForge itself. docker-compose.prod.yml reads the same
variables but generates nothing, so set the secrets in .env yourself before
starting anything you expose.
git clone https://github.com/InsForge/InsForge.git
cd InsForge
cp .env.example .env
$EDITOR .env
docker compose -f docker-compose.prod.yml up
Set JWT_SECRET, ENCRYPTION_KEY, POSTGRES_PASSWORD, and
ROOT_ADMIN_PASSWORD — .env.example ships placeholders for them, and the
compose file falls back to published defaults for any you leave unset. Set
ACCESS_API_KEY and ACCESS_ANON_KEY too if you want to know your own keys;
left empty, the backend generates a pair only it knows.
This path passes -f explicitly, which overrides COMPOSE_FILE. Add overlays as
further -f flags rather than editing that variable.
2. Connect InsForge MCP
Follow the steps to connect InsForge MCP Server
3. Verify installation
To verify the connection, send the following prompt to your agent:
I'm using InsForge as my backend platform, call InsForge MCP's fetch-docs tool to learn about InsForge instructions.
4. Running Multiple Projects
Give each project its own directory:
curl -fsSL https://raw.githubusercontent.com/InsForge/InsForge/main/deploy/setup.sh | sh -s ~/project1
curl -fsSL https://raw.githubusercontent.com/InsForge/InsForge/main/deploy/setup.sh | sh -s ~/project2
Then give each a project name and its own ports. Both .env files start with
COMPOSE_PROJECT_NAME=insforge, and two directories sharing that name share
containers — the second up -d adopts the first's, rebuilt with the second's
config. Set it before starting anything.
~/project1/.env keeps the default ports — which collide with the ~/insforge
instance from the quickstart above if it is still running. Stop that one, or give
project1 its own ports the way project2 has:
COMPOSE_PROJECT_NAME=project1
~/project2/.env:
COMPOSE_PROJECT_NAME=project2
POSTGRES_PORT=5442
POSTGREST_PORT=5440
APP_PORT=7230
AUTH_PORT=7231
DENO_PORT=7233
Now each directory is a separate instance with its own containers, volumes, database, and secrets:
cd ~/project1 && docker compose up -d
cd ~/project2 && docker compose up -d
docker compose ps, logs -f, and down operate on whichever directory you
run them from.
5. Storage Backends (Optional)
InsForge stores files on the local filesystem by default. Backing storage with an S3-compatible store also enables the S3-compatible gateway at /storage/v1/s3 (use aws CLI, rclone, or any AWS SDK against your InsForge Storage).
Append one overlay to COMPOSE_FILE in .env. Bundled MinIO, whose store stays
internal to the Docker network:
COMPOSE_FILE=deploy/docker-compose/docker-compose.yml:docker-compose.minio.yml
Or Rus
For agents
This page has a .md twin and JSON over the API.