InsForge

What InsForge does

InsForge is a Postgres-based backend designed to be driven by AI coding agents. It covers the usual set of services: a database where every table becomes a typed REST endpoint through PostgREST, authentication, S3-compatible file storage, realtime channels and TypeScript edge functions on Deno. On top of that it adds a model gateway for calling language models through one OpenAI-compatible endpoint, frontend deployment, payment helpers for Stripe and Razorpay, and long-running containers (Compute, in private preview).

What sets it apart is the interface. Agents such as Cursor or Claude Code connect through an MCP server, which works on both self-hosted and cloud instances, or through a CLI with “Skills”, which is cloud-only. Agents can read schemas, logs and configuration, run migrations, deploy functions and set up auth providers. The documentation openly positions this against Supabase, which it describes as built for human developers.

Security and access control

Access control relies on Postgres row-level security. Policies read the user’s JWT, and the same rules apply to REST queries, SDK calls, realtime subscriptions and storage requests. With the cloud CLI, a diagnostics command lists RLS warnings and other advisor findings, which helps when an agent writes the schema and you want to check its work.

Users can sign in with email and password (with verification, password reset and brute-force throttling), magic links, one-time codes, OAuth providers such as Google, GitHub and Apple, or any OIDC-compliant provider. There are also integration guides for external auth services such as Clerk, Auth0, WorkOS and Better Auth, and InsForge can itself act as an OAuth 2.0 server.

Self-hosting InsForge

A setup script downloads the Docker Compose files and generates secrets. After you set the public URL in .env, docker compose up -d starts the stack. Files are stored on the local disk by default; overlays add bundled MinIO or RustFS, or you can point it at any S3-compatible service. The VPS guide gives a minimum of 2 vCPU, 2 GB RAM and 20 GB SSD, and recommends 4 vCPU and 4 GB or more. Guides cover AWS, Azure, Google Cloud, Hetzner, Coolify and Dokploy, and a backup script dumps the database and configuration.

Self-hosted instances must configure their own SMTP server, or verification, password reset and passwordless sign-in emails will not be sent.

Hosted version

InsForge Cloud has a Free plan, whose projects are paused after a week of inactivity, plus Pro and Enterprise plans.

Limitations

InsForge is a young project, and its documentation is written with agents in mind as much as people. Several headline features depend on outside services: the model gateway routes through OpenRouter, and Sites builds on Vercel. If you want a backend fully under your control, check which parts you need. There is no importer for Firebase data.

Who it suits

InsForge suits developers who build mainly through AI coding agents and want those agents to manage a real Postgres backend with row-level security, rather than generating ad-hoc server code. Teams that do not work this way get a similar Postgres stack, with a longer track record, from Supabase.