Forge documentation
The forge is your software and the crew that builds it, in one place: a self-hosted forge in one Bun process and one SQLite file that hosts code and runs apps, with AI agents that build. Forges connect to one another.
The forge is part of Open Platform, with the platform for organizations.
Start here
The guide, in order, one or two screens a page: What a forge is, Your first app in five minutes, Tell the crew, Ship and undo, Your apps, Hosting forges, Bring your own AI, Agents, Backups and moving, Settings, When something is wrong.
Use it
- The studio: the web interface and the words it uses.
- Tour: every other page and screen, and each way to reach it.
- Apps: apps, previews, runs and the rules the forge enforces.
- The crew: how agents build, review and land work.
- Asks: what waits on a person and how to answer it.
- Cloning over git: smart HTTP, SSH and large repositories.
- MCP: the forge as a Model Context Protocol server.
- The
forgecommand: every command, with an example.
Run it
- Run it: start a forge and create the first admin.
- On your machine: the local copy, offline work and the binary.
- Send a change without a forge: fork, source archive, patch, pull.
Connect forges
- Origins: connect accounts on other forges, mirror and write through.
- A forge is an origin: connect one forge to another.
- The forge toolbar: the pill in every app and preview.
Operate it
- Operating: configuration, health, releases, switches and limits.
- Metrics: the Prometheus endpoint.
- Failure domains: the ways the forge stops and what it reports.
- An app's own domain: cut-over, certificate, and the way back.
- Snapshots: nightly copies and what they hold.
- Recovery: a printable guide for a forge in trouble.
- Restore: bring a forge back on a fresh machine.
Secure it
- Security runbook: what to do, with no AI, under load or after a leak.
- Threats: each protection and its test. Protections with no test are listed as gaps.
Develop it
- Developing the forge: tests, checks, the gate, lint and types.
- Architecture: the principles and the shape of the system.
- Writing: how to write documentation for the forge.
- Dependencies: every package and why it is there; the gate refuses one without its line.
- Reference: the long reference and the list of every document.