InsForge

InsForge/InsForge

The all-in-one, open-source backend platform for agentic coding. InsForge gives your coding agent database, auth, storage, compute, hosting, and AI gateway to ship full-stack apps end-to-end.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 13, 2026
1 day ago
Ship score
85/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 13,018 → 13,103 (Sep 22 – Oct 13, 2026)
History starts 2026-09-22, the first weekly sample after this repo joined the directory.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
13.1K
Forks
1.2K
Open issues
215
Watchers
36
Primary language
TypeScript
Created
Jul 29, 2025
Owner
InsForge · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 213 startups in the directory ship primarily in TypeScript.

Topics

#ai#ai-agents#coding#deno#embeddings#insforge#nextjs#oauth2#pgvector#postgresql#realtime#vectors#websockets

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 99%, self-hostable 60%, hosted offering 54%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 2026-09-22, found by the weekly discovery job at confidence 0.99. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-13This is the badge for InsForge/InsForge, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/InsForge/InsForge.svg)](https://ossean.com/InsForge/InsForge)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.