A self-hosted workspace that turns a STEP assembly into manufacturing: drawings, flat patterns, weld setups, release control and shop-floor tracking.
Upload a neutral CAD file, classify every part (machined, sheet metal, purchased), record how each one is made, and Forge produces the drawing set, sheet-metal developments and manufacturing pack. It then follows the parts through release, job orders and quality inspection. One revision-controlled record from design review to the shop floor, running on your own server.
Forge is built and used in production at GOAT Robotics for its autonomous mobile robots.
Launch film, 58 s — play with sound.
- What it does
- Quick start
- Configuration
- How a project flows through Forge
- Drawings
- Architecture
- Security model
- Operations
- Development
- Scope and limits
- Contributing
- License
CAD workspace
- Imports STEP, IGES and BREP assemblies. Keeps the assembly tree, component placements, occurrence quantities and multi-body parts.
- Imports Forge packages (
.forge): STEP plus the CAD feature data STEP cannot carry — tapped holes and cosmetic threads, sheet-metal K-factors, material and properties, press-in inserts and fasteners — written by the SolidWorks exporter intools/solidworks/(uses the seat's own API, no add-on licence). Applied as from CAD, editable, never inferred. Format:docs/FORGE_PACKAGE.md. - Imports native SolidWorks parts (
.sldprt) with Forge's own reader (backend/app/swread): the exact B-rep SolidWorks stores for the active configuration (Parasolid data, rebuilt surface for surface), plus Hole Wizard holes, cosmetic thread sizes, material, colour, sheet-metal values and custom properties. Every solid is checked (valid, closed) before use; a part that cannot be read exactly is refused with the reason. SolidWorks assemblies come in as a ZIP of the assembly folder (Pack and Go, or the zipped folder; a Pack and Go name prefix such asISO-is fine): the component tree gives structure and placements, every part is read as above in the configuration the assembly uses, and virtual components are read from inside the assembly file. A part missing from the ZIP becomes a flagged placeholder box. - Fast 3D viewer: part navigator with assembly hierarchy, category filters, isolate a part (or one instance of a multi-quantity part), ghosting, section, explode, measure and view cube.
- Realistic view: each part shows its finish and material — powder coat gloss level and colour, plating, anodising, bare stainless, aluminium or steel with its machined roughness — with studio reflections and an optional studio backdrop.
- Classifies parts as machining, sheet metal or purchased from geometry and naming rules. Every suggestion is reviewed by an engineer, and sub-assemblies can be re-classified in one step.
Manufacturing definition
- Material, stock, process sequence, finish, coating (RAL picker), tolerances, datums, heat treatment, roughness, masking, marking and K-factor per part, or applied from reusable process templates.
- A step-by-step Make production ready walkthrough that asks the questions an engineer must answer before a part can be released.
- Rule checks (bend radius, flange length, hole-to-edge, holes inside a bend's distortion zone of 2t + r, a hanging hole for powder coating, …) with recorded waivers — accepting a distortion risk is a waiver on that hole — and manual verification items.
- Hole hardware shown as real parts in 3D: self-clinching nuts with knurled collars and yellow-zinc threads, flush nuts, studs, standoffs, rivnuts, DIN 929 weld nuts, tapped threads and countersinks.
Drawings and documents
- GOAT-style A4/A3/A2 sheets: third- or first-angle views, ordinate dimensions, hole callouts or hole tables, chamfer and fillet notes, angled holes and sloped faces, pictorial views, a title block filled from your project settings.
- Sheet-metal flat patterns with bend lines, UP/DOWN bend table, outside heights and blank thickness. Flat DXF ready for laser cutting.
- A vector drawing editor: move views and callouts, add notes and detail views, switch hidden lines per view, set threads and fits, review and export PDF. Geometry stays linked to the STEP.
- Editable DXF with true-scale ordinate dimensions, per-part STEP, and a ZIP manufacturing pack.
Welding and assembly
- Weld studio: pick two faces on any parts (touching or with a gap), or let Forge find every seam between selected components. Filter by inside/outside side, see the bead in 3D, and get ISO 2553 symbols on the assembly drawing.
- Bolted, press-fit and other joints with torque, fit limits and assembly instructions.
Release and production
- Release gate: every custom part needs a complete specification, design review and drawing review before the revision can be released.
- Job orders with a per-part process checklist, deadlines with days remaining and schedule pace, hold and cancel reasons, and count corrections.
- Vendors and rate cards: material per kg, laser per metre of cut and per pierce, bending per stroke, rolling, machining per hour, drilling, tapping, countersinks, hardware and its insertion, welding per metre and per tack (by process and material), finishes and colours, quantity breaks, margin and GST. A Coimbatore base sheet is included; copy it for each vendor and enter their rates.
- Every job order is priced from the parts' own geometry (flat-pattern cut length and pierces, bends, rolls, holes and their hardware, surface area, mass, welds) with the chosen vendor's rates. Compare vendors before creating it, change the vendor later, and see the cost per part and per process.
- Every make part has a Cost tab: the approximate cost to make one piece, split by process, with setups spread over the quantity, the cost at 1–500 pieces and at each vendor.
- Sheet nesting with true shapes; parts can be kept square to the sheet (only 0 / 90 / 180 / 270° turns) so the laser cuts along X and Y.
- Quality inspection against released limits, CSV export, a review thread and a full audit trail.
- Expiring, revocable, read-only vendor links scoped to one revision.
You need Docker with Compose v2 and about 8 GB of free RAM for the CAD worker.
git clone https://github.com/goat-robotics/forge.git
cd forge
cp .env.example .env
# Edit .env: set ALLOWED_EMAIL_DOMAINS and ADMIN_EMAILS for your organisation
docker compose up -d --buildOpen http://localhost:8100.
- Without Microsoft Entra ID, the first visitor creates the administrator account with a password. Do this before the server is reachable from a network.
- With Microsoft Entra ID, run
scripts/entra-register.sh(see platform guide). People then sign in with their organisation account, and the first one (or anyone inADMIN_EMAILS) becomes administrator.
Two services start: the web/API service and a separate CAD worker. Data lives in the forge-manufacturing_forge-data Docker volume. Stop with docker compose stop and resume with docker compose up -d. Never run docker compose down -v unless you mean to delete every project.
The port is bound to 127.0.0.1 by default. For remote use, put Forge behind an HTTPS reverse proxy and set COOKIE_SECURE=true and PUBLIC_URL.
All settings are environment variables, read from .env by Docker Compose. See .env.example.
| Variable | Default | Purpose |
|---|---|---|
PORT |
8100 |
Local port (bound to loopback). |
PUBLIC_URL |
http://localhost:8100 |
External URL, used for sign-in redirects and links. |
COOKIE_SECURE |
false |
Set true whenever Forge is served over HTTPS. |
FORGE_SECRET |
generated | Signs short-lived model links and sign-in state. If unset, a random secret is created in the data volume; set it explicitly (openssl rand -hex 32) when running more than one container. |
ALLOWED_EMAIL_DOMAINS |
— | Comma-separated e-mail domains allowed to sign in. Set this to your own domain. |
ADMIN_EMAILS |
— | Accounts that become administrators on first sign-in. |
DEFAULT_ROLE |
viewer |
Role for other new accounts. |
AUTH_MICROSOFT_ENTRA_ID_ID / _SECRET / _ISSUER |
— | Microsoft Entra ID single-tenant sign-in. Filled by scripts/entra-register.sh. |
FORGE_ALLOW_LOCAL_LOGIN |
false |
Keep password sign-in available as break-glass access once Entra is configured. |
MAX_UPLOAD_MB |
1024 |
Largest CAD upload. |
UPLOAD_CHUNK_MB |
16 |
Uploads are sent in chunks of this size, so reverse proxies and tunnels with request-size limits (Cloudflare: 100 MB) accept files of any size. Keep it well below your proxy's limit. |
FORGE_DRAWING_WORKERS |
3 |
Parallel drawing-generation processes in the worker. |
S3_BUCKET, S3_ENDPOINT, S3_REGION, S3_ACCESS_KEY, S3_SECRET_KEY |
— | Optional S3-compatible mirror for uploads and generated files. |
CAD_EXECUTION_MODE |
local |
ephemeral runs each CAD job on a short-lived DigitalOcean Droplet (see below). |
Company details on drawings (company name, drawn/checked/approved by, tolerance table, fits, general note) are set in the app under Settings → Drawing, not in the environment. Part-number prefixes, make/buy rules and workshop rules are per project.
- Upload a
.step/.stp/.iges/.igs/.brep, a native SolidWorks part (.sldprt) or assembly folder (.zip), or a.forgepackage from the SolidWorks exporter (tools/solidworks/README.md) to bring threads, sheet-metal parameters and inserts along. Export other native CAD (Creo, Inventor, …) to STEP first. Assemblies keep their structure; multi-body parts become one record per body. - Classify. Review the suggested category of every part. Mark purchased items, hide small bought-in parts, and mark anything Not for production with a reason.
- Specify. Fill in how each part is made, directly or with the Make production ready walkthrough. Apply process templates to many parts at once.
- Check. Work through the rule findings and manual checks, and approve fits and joints. Configure welds in the weld studio.
- Generate documents. Drawings, flat patterns, DXF, STEP and the manufacturing pack are produced by the worker in the background. Refine any drawing in the editor and mark it reviewed.
- Release. When every part is production ready, Release revision locks engineering edits and produces the final pack.
- Produce. Open job orders against the released revision, record progress per process step, and track the deadline.
- Inspect. Record measurements against released limits. Forge computes pass/fail and keeps the record.
- Revise. Upload the next revision. Specifications carry over by part name and shape; every part returns to review.
Details, roles and permissions are in the platform guide. Vendors, rate cards and job-order estimates are described in docs/PRICING.md.
Forge generates a starting drawing for every machined and sheet-metal part:
- View selection: the main view is the face with the largest area; long parts are laid along the sheet. Top, side and extra views are added where holes enter.
- Dimensions: ordinate dimensions from each view's bottom-left corner, hole positions, step edges, angled holes (entry point and drilling angle) and sloped faces.
- Holes: grouped callouts (Ø, depth, THRU, counterbore, countersink). Crowded views switch to a tagged hole table in CNC tool order.
- Placement: every label is placed with a collision map of views, dimensions, holes and other text. Sheet size and scale are chosen so nothing overlaps.
- Sheet metal: a formed views sheet plus a flat pattern sheet with the blank edge view and thickness, bend lines, a bend table and balloon tags tied to each bend line.
- Never inferred: thread size, thread class and fits are never guessed from geometry. They come only from what an engineer specifies.
The drawing editor is documented in docs/DRAWING_EDITOR.md. What is and is not covered automatically is in docs/COVERAGE.md.
frontend/ React + TypeScript + Three.js (Vite) workspace, viewer, weld studio, drawing editor
backend/ FastAPI + SQLite (WAL) API, auth, permissions, jobs
app/cad.py, hole_features.py, unfold.py, seams.py OpenCascade geometry: analysis, holes, flat patterns, weld seams
app/sheet.py, drawing_scene.py, pictorials.py drawing layout, editable vector scene, PDF/DXF output
app/worker.py CAD import and document generation worker
- Geometry: OpenCascade (OCP), trimesh and shapely. Documents: ReportLab (PDF) and ezdxf (DXF).
- Services: no Redis, PostgreSQL or cloud CAD service. One API process and one worker on a single host with a persistent volume. Jobs are persisted and resume after a restart.
- Ephemeral CAD workers (optional): with
CAD_EXECUTION_MODE=ephemeraland DigitalOcean/Spaces credentials, each CAD job runs on a one-off Droplet that gets only expiring upload and download URLs, then is deleted.
The module map and extension points are in docs/ARCHITECTURE.md.
- Sign-in with Microsoft Entra ID (single tenant, no guests) or local passwords. Sessions are HttpOnly; access can be restricted to listed e-mail domains.
- Roles and per-project membership decide who can edit, review, release, download CAD or manage job orders.
- 3D models are streamed encrypted through short-lived, session-bound URLs and are not downloadable. STEP/DXF downloads need an explicit permission.
- Vendor links are read-only, scoped to one revision, expiring and revocable, and stored as hashes.
- Containers run read-only, with no Linux capabilities and
no-new-privileges.
Report security issues privately to the maintainers (see Contributing), not in public issues.
Backup. Stop both services briefly and archive the volume:
mkdir -p backups
docker compose stop
docker run --rm --user 0 --entrypoint sh \
-v forge-manufacturing_forge-data:/data:ro \
-v "$PWD/backups:/backup" forge-manufacturing:local \
-c 'tar -czf /backup/forge-$(date -u +%Y%m%dT%H%M%SZ).tar.gz -C /data .'
docker compose up -dThe archive contains accounts, CAD, vendor links and quality records, so store it privately. Restore into a separate empty volume and validate it before replacing a live installation.
Resources. The API is limited to 768 MB. The worker is limited to 6 GB and 3 CPUs; large assemblies need that much RAM and disk.
Do not scale workers. Job recovery assumes exactly one worker.
Requirements: Python 3.13 and Node 22.
python3.13 -m venv .venv
.venv/bin/pip install -r backend/requirements.txt
(cd frontend && npm ci && npm run build)
# API
PYTHONPATH=backend .venv/bin/uvicorn app.main:app --host 127.0.0.1 --port 8100
# Worker (second terminal)
PYTHONPATH=backend .venv/bin/python -m app.worker
# Tests (isolated temporary database and generated geometry fixtures)
PYTHONPATH=backend .venv/bin/python -m pytest backend/tests -q
# Type check the frontend
(cd frontend && npx tsc --noEmit -p .)For frontend work, run npm run dev in frontend/ alongside the API. Interactive API documentation is served at /docs.
Forge produces an engineering starting point, not finished production detailing. An engineer remains responsible for every released drawing.
- GD&T, datum feature symbols, functional dimensioning, machining setups and full assembly sequences still need drafting by an engineer.
- Flat patterns use the configured K-factor and are marked provisional until the allowance is approved for your tooling.
- DXF curves are sampled at 0.025 mm deflection; they are not validated CAM toolpaths.
- Classification, weld seams and fits are suggestions until reviewed.
- Release records your organisation's approval; it is not an independent certification of the design.
See docs/COVERAGE.md and docs/VALIDATION.md.
Forge is developed by GOAT Robotics. You may send improvements to GOAT Robotics; anything you send becomes the property of GOAT Robotics under section 5 of the LICENSE.
Forge is source-available, not open source. Copyright (c) 2026 GOAT Robotics Private Limited. See LICENSE.
| Private, non-commercial use | Allowed |
| Modification (for your private, non-commercial use) | Allowed |
| Commercial use (including any use by or for a business) | Not allowed |
| Distribution (of Forge or your modified versions) | Not allowed |
| Patent use | Not granted |
For a commercial license or any other permission, contact naveen@goat-robotics.com.
"Forge" and the GOAT Robotics name and logo are trademarks of GOAT Robotics Private Limited.
