WO-2291
Enclosure / Type C · 24 each
- 01 Laser cut & form Complete
- 02 Weld frame Complete
- 03 Powder coat Held
- 04 Fit out & pack Queued
Manufacturing ERP
Manufacturing ERP, built this decade.
Customers, stock, purchasing and the floor in one system — with an open API, an assistant that can actually work the data, and everything your shop doesn't do simply switched off.
You work directly with the people who built Forge — the same team through setup, go-live and afterwards. Open API throughout, so it fits alongside the systems you already run.
What you switch on
Turn off the parts you don't use.
Forge is one system, not a suite you assemble. A short spine is always there because everything references it. Everything else is a surface your workspace can simply not have — so you are not paying for, or looking at, a module your shop will never open.
Always there
Customers & organizations
Every company and contact you deal with, in one place the whole system points at. Always present, because purchasing, inventory and work orders all reference it.
Inventory & purchasing
What you hold, where it is, what you have on order, and what it cost. Stock levels, receiving, transfers, purchase orders and an append-only movement history.
Items & quantities
Your product types modeled as real structures, with every quantity carrying its unit — so what you buy, hold, issue and cost all agree with each other.
Switchable
Optional
Work orders & time clock
Schedule work against a defined workflow, gate steps behind preconditions, and track who ran what for how long.
Switch it off if you don't track the floor. Inventory and purchasing carry on working without it.
Optional
Sales pipeline
Quotes, opportunities and the activity history behind them, kept against the same customer records.
Switch it off if you run Salesforce or HubSpot. Forge still knows who your customers are.
Optional
Dashboards & reporting
Live views over whatever you have switched on — no warehouse to load and no overnight refresh.
Switch it off and take the data out over the API instead.
How it works
Opinionated where it counts.
A system that permits every possible way of working cannot help you with any of them. These are the four positions Forge takes, and the ones your team will feel the difference from on the floor.
Your product gets its own model.
A panel is not an enclosure is not a frame. Every product type you build gets its own real structure and its own workflow — so the fields, the rules and the steps match the thing itself.
Instead of: one generic products table, thirty optional columns, and a spreadsheet to remember which ones apply to what.
Work waits for the gate, not for someone to notice.
Any task can be held behind a precondition — a subassembly cleared inspection, a material received, a measurement recorded. Until it clears, the next step does not open, and the floor can see exactly what is blocking and why.
Instead of: a status column somebody updates when they remember, and a supervisor walking the floor to find out what is really happening.
Every quantity carries its unit.
Buy steel by the kilogram, issue it by the sheet, cost it by the square meter. Forge holds what connects them, so one purchase converts cleanly into stock, into issue and into cost. Weights convert to weights and lengths to lengths — ask for anything else and it refuses rather than guessing.
Instead of: a bare decimal, a separate unit-of-measure column, and a conversion somebody did in their head at 6am.
The shop floor works without a signal.
Scan, count and move stock in a dead zone. The device queues the work and replays it when the connection returns. Nothing reads as done until the server confirms it, and anything the server rejects lands in a supervisor's queue instead of vanishing.
Instead of: optimistic ticks that lie about what was saved, or a tablet that simply stops working past the loading bay.
The assistant
Ask it. It works the same data you do.
Forge exposes its whole domain over the Model Context Protocol, so an assistant reads and writes through exactly the paths a person uses — the same services, the same permission checks, the same audit trail. It is wired into the system rather than bolted alongside it.
- It knows what you make
- Because your product types are modeled as real structures rather than rows in a generic item table, it can answer a question about an enclosure instead of guessing what column seventeen means.
- It can't do what you can't
- It acts as the person using it. Same login, same role, same entitlements — an assistant cannot reach a record its user could not open themselves.
- Every change is on the record
- Writes it makes carry who, when and what they touched, exactly like any other write. There is no separate AI back door and nothing that skips the audit.
Part designer
Design the part, not the paperwork.
Most ERPs make you describe what you build by filling in forms — a routing table here, a bill of materials there, an operations list somewhere else, and nothing that shows you the shape of it. Forge's part designer is a node editor: materials, operations and gates as nodes on a canvas, wired into the thing you actually make.
See the whole workflow at once
Where work branches, where it merges, and what is holding it up — in one view instead of four tables.
Change it without raising a ticket
Rewire a workflow when the process changes on the floor, rather than queuing behind a customization request.
It is the model, not a diagram
What you draw is what production runs. There is no second source of truth to keep in step with the first.
Setup
You set the pace, not us.
ERP projects don't run for a year because of the software. They run for a year because of discovery, the customization backlog and the integration work. Forge already knows what a work order is, so setup means modeling your products and configuring your process — and it moves as fast as your shop can move.
- 01
We stand up your workspace
Your own deployment, with the parts you need switched on and your people invited. Nothing to install, and an open API from the first day if you want to wire it to what you already run.
- 02
You model what you make
Product types, workflows and gates, laid out on a canvas with us alongside you. This is the part a traditional ERP rollout spends half a year on — and the part that decides whether the system fits how you build.
- 03
Your team starts working
Guided walkthroughs run inside the real system on your real data, so people learn the job itself rather than sitting through a training course about it.
The platform
One deployment per customer. Not one row per customer.
Most ERP software puts every customer in the same database and keeps them apart with a column. Forge gives each customer its own application, its own database and its own storage — so isolation is a boundary, not a filter someone has to remember to apply.
- Deployment
- Dedicated Your own application, database and object storage, per environment.
- Audit
- Every write Who, when, and the request it arrived on — joined by one correlation ID.
- Configuration
- Yours Product types, workflows and gates are yours to change in the app. Deeper work we build with you, versioned so upgrades never break it.
- Integration
- Open API Every record reachable over a documented API, so Forge fits the systems you already run.
See it running against your kind of work.
Bring a product you actually make. We will model it during the demo rather than walking you through a generic tour, so you can judge the fit on something real.