ForgeMigrating to Forge

Under 15 minutes.
No new hardware.
Nothing left behind.

Forge runs on macOS and Linux natively, and on Windows through the browser — so a Windows-first engineering team doesn't need to buy new hardware to start. A guided setup wizard connects your machines, imports your existing CAD library, and bridges your current systems in under 15 minutes.

No new hardware

Your Windows engineers use Forge today.

Forge is macOS and Linux native, but the full feature set is available through the React web UI in any browser — including Edge and Chrome on Windows. Windows engineers don't need a new machine to access ForgeCAD, ForgeOps, or ForgeMaint. They open a browser tab.

ForgeCertify standalone ships native binaries for macOS, Linux, and Windows — the only Forge component with a native Windows binary.

No extra seats

The same licence works at the desk and on the floor.

An engineer working at their fully-enabled desktop can pull up the same Forge environment on an iPad standing next to a machine. No additional seat purchase. No separate floor licence. Changes made on the floor are live everywhere immediately — because it's the same system.

ForgeMaint's iPad interface is optimised for shop-floor use: large touch targets, offline-capable, sunlight-readable.

Platform support

Native means a local process on your machine. Web UI means the full feature set in a browser — no local install required.

ProductmacOSLinuxWindows
Forge (full suite)NativeNativeWeb UI (browser)

Windows engineers use the React UI in any browser — full functionality, no macOS required.

ForgeCADNativeNativeWeb UI (browser)
ForgeCertify (standalone)NativeNativeNative

The only Forge component with a native Windows binary — runs directly on the machine you're certifying against.

ForgeOps / ForgeMaint / ForgeMachineNative + WebNative + WebWeb UI (browser)

The setup wizard

Five steps. Under 15 minutes. Forge walks you through each one.

01

Connect your machines

~3 min

Provide your PLC endpoints or OPC-UA addresses. Forge autodiscovers connected devices and maps them to the ForgeMachine I/O catalog. Unrecognised devices are flagged for manual assignment.

02

Point at your existing CAD library

~5 min setup, ingestion runs in background

Give Forge a directory path (or share path) to your existing CAD files. The ingestion engine scans, parses, and imports. Files that parse cleanly are imported automatically. Anything below the confidence threshold is queued for engineer review.

03

Attach your existing systems

~4 min

Enter credentials for any systems you want to bridge: SAP, Oracle, Maximo, Hexagon, Dynamics, Salesforce, or a generic REST/ODBC endpoint. Eight enterprise adapters built in. You choose what to connect.

04

Set output paths

~2 min

Configure where Forge writes exports: NC programs, drawings, reports, BOMs. If you have a specific directory structure for your CNC machines or DMS, Forge follows it.

05

Forge is live

Under 15 min total

Every connected machine is monitored. Every imported CAD file is in the graph. Every configured system is bridged. ForgeOps begins producing data from the first machine event.

Your existing CAD library — imported, not re-entered

Forge's ingestion engine parses your existing CAD files deterministically. Files that import cleanly do so automatically. Anything ambiguous is held for engineer review — with a full explanation of what Forge found and why it wasn't certain.

Above threshold: imported automatically

Files that parse deterministically — geometry intact, metadata complete, revision traceable — are imported without engineer involvement. The majority of a mature CAD library falls here.

⚠️

Below threshold: queued for engineer review

Files with ambiguous geometry, missing metadata, or conflicting revision history are held in a review queue. The engineer sees exactly what Forge found and exactly what it wasn't sure about — and approves or corrects each entry.

📊

Full ingestion report

After the initial import, Forge produces a complete report: files imported automatically, files pending review, files that couldn't be parsed and why. Nothing is silently dropped.

🔄

Incremental ingestion on a schedule

After the initial import, Forge monitors the source directory for new and modified files. Changes are ingested on a configurable schedule — keeping the Forge graph current without manual re-imports.

Run Forge next to your current setup.

Forge doesn't require you to decommission anything to get started. Import your existing data. Compare directly. Run both in parallel for as long as you need. When you're ready to cut over, it's one configuration change — not a six-month migration project.

Already have Oracle, Maximo, or Teamcenter?

Read how Forge runs alongside your existing enterprise stack — without a rip-and-replace.

Adoption strategy →