Home

Free, open-source ERP and MES for job shops: job cards on the floor, books in the office, one database.

Forge is a self-hosted operations platform covering the full quote-to-cash lifecycle — leads, quotes, sales orders, jobs, a kanban shop floor, time tracking, inventory, purchasing, shipping, invoicing, payments and returns — plus parts/BOM management, quality control, an employee training LMS, document signing and an optional AI assistant. It runs as a Docker Compose stack on one box, or split across several, with no Kubernetes commitment.

Job shops are the primary audience, but the same binary also carries a professional-services shape and a retail/marketplace commerce layer, chosen by preset at setup — see Business Shapes.

🌐 forge.armoryworks.com · 🏭 built by Armory Works · ⚖️ Apache 2.0

Status: public beta (1.0.0-beta.*). Usable, in use, and still moving — APIs and schema can change between betas.

---

Start here

I want to…	Go to
Install Forge on a box	Installation
Understand how it's built	Architecture
Know which features I'll actually get	Capability Gating
Work out the QuickBooks / built-in-books question	Accounting Modes
Look up what a specific screen or field does	Feature Reference
See a screen's flows and layout	UI Flows
Find a document in the repo	Documentation Map
Try it without installing anything	Try Forge First
Integrate another system with Forge	API Access
Run it in production	Hardening a Production Install · Backup and Restore · Upgrades and Rollback
Get it onto phones and the floor	Mobile and Offline · Shop Floor Kiosk
Load real data and go live	First Week
Know what it doesn't do	Limits and Non-Goals
Set up a development environment	Developer Setup
Contribute code or docs	Contributing
Decode the jargon	Glossary
Ask the obvious question	FAQ

The repos

Forge is a multi-repo project. This wiki lives on the umbrella repo; the code is in siblings.

Repo	What it owns	Wiki
forge	Umbrella: product docs, specs, delivery plans, governance, release manifest	you are here
forge-deploy	docker-compose, setup.sh, the forge-deploy CLI — start here to install	wiki
forge-ui	Angular frontend (SPA)	wiki
forge-api	.NET API — MediatR/CQRS, EF Core as the query-mapping layer	wiki
forge-db	The database project: desired-state SQL + the reconcile harness that owns the schema	wiki
forge-test	Acceptance-case library and the public test/demo SPA	wiki
forge-voice	Asterisk-based outbound calling	wiki

This wiki is the hub. It carries the product-level answers — what Forge is, what it can be configured into, how to run it. Each sibling repo's wiki is a spoke carrying the depth that belongs to that component: how it is laid out, how to work on it, its own conventions and traps. Concepts live here once; the spokes link to them rather than restating them.

Open issues and PRs in the repo that owns the affected code. Cross-cutting design discussion belongs on the umbrella repo.

How this wiki relates to the docs in the repo

The wiki is a map and an on-ramp. The authoritative detail — every field, endpoint, status lifecycle and validation rule — lives in docs/ in the umbrella repo, versioned with the code that implements it. Wiki pages summarise and link; they do not fork the truth. If a wiki page and a repo doc disagree, the repo doc wins — and the wiki page needs fixing.