Your mill certificates do not belong in a hosted silo.

ForgeEPM stores the event log, mill test reports, drawings and turnover evidence on a Windows PC inside your facility. ForgeGo talks to that host. Unplug the internet and the crew still works.

On-site database Offline ForgeGo queue Owned backups

What stays in the building

The system of record is a machine you can point at.

Host

Windows PC or shop server

One local host on your network. No per-workstation tax. Floor devices pair to this business, not to a public cloud tenant.

Records

Event log + certificates

Heats, MTRs, inspections, release approvals and manifests stay on disk you control, with deterministic backup to a second drive or NAS.

On-device, optional

Forge AI runs on the shop PC against records already in the building. A prompt does not ship mill data to a third-party model host.

Mail

Company addresses only

Public web forms notify info@forgeepm.com. Staff mailboxes are @forgeepm.com on Microsoft 365. That is email — not the fabrication database.

Compared with cloud-only shop packages

When the access point dies, the bay does not stop.

Cloud systems fail in the exact moment a fabricator cannot afford delay: cut, weld, inspect, load. ForgeEPM treats connectivity as a sync path, not as permission to work.

Latency does not gate the saw.
The host is on the shop LAN. ForgeGo queues if that LAN blips.

You can take a backup off-site.
Copy the database. You are not waiting on an export ticket.

Turnover has a digest.
SHA-256 of the package is produced from the local record, not from a portal state.

Honest boundary

Local-first is not the same as air-gapped forever.

You still choose when the PC is on a network, how backups leave the building, and which staff mailboxes exist. ForgeEPM does not replace your IT policy. It gives the fabrication record a machine that belongs to the shop.

See the platform

FABRICATION DB
On-site Windows hostOWNED

FORGEGO
Paired devices, local queueOFFLINE

FORGEMAIL
Company email on Microsoft 365SEPARATE