Forge

Forge is an opinionated, open-source Go + React framework and deploy platform that ships the production system — dev environments, tests, secrets, multiple environments, releases, observability and hosting — from the first commit, built for AI agents to work in.

The Go framework for AI-generated code, with an MCP server that deploys your app:

# Deploy a Vite or Next.js static app without an account (live URL + 72-hour claim link)
npx -y @reliantlabs/forge@latest env deploy prod --claimable

# Use from your agent: an MCP server to deploy your app (Claude Code; Cursor, Codex and Gemini below)
claude mcp add forge -- npx -y @reliantlabs/forge mcp

# Not sure where to start? forge start prints the one next command for this directory
forge start

Install forge, and the other ways to run it: Install.

Website · Live demo · Docs · Reliant · Slack

Most teams build that system in year two, under deadline, on top of a codebase that wasn't shaped for it. With Forge the first commit already has it, wired into files you own and can change.

Try it in the browser first: the live demo.

Quick start

# Install (macOS / Linux; Windows, Homebrew, npm and go install: see Install below)
curl -fsSL https://raw.githubusercontent.com/reliant-labs/forge/main/install.sh | sh

forge project new my-app && cd my-app
forge scaffold service billing
forge generate
forge env up dev

That last command brings up Postgres, runs your migrations, and starts your services and frontends, then prints a table of URLs and a log file for each process, including the HyperDX UI, already receiving the app's traces, metrics and logs. With a frontend (forge project new my-app --frontend web) it also starts a local identity provider, so the app's own sign-in page works on the first run. No signup, no external accounts, no cloud project, no cluster.

Add tables (a // forge:entity message and forge scaffold) and a fresh database is seeded with foreign-key-coherent rows that satisfy every constraint your schema declares, so the app boots alive instead of empty.

When you want it online, forge env deploy staging builds a release once and deploys it. A new project's staging and prod are bound to Reliant hosting; the same environments deploy to a Kubernetes cluster you run, or as host processes, by changing where each workload is bound. Before you call a change done: forge generate && forge lint && go build ./... && task test.

Everything included

What a new app would otherwise stitch together from separate tools:

... View full README on GitHub