Works with

Yes — it works
with your stuff.

Any CAM software. Any ERP. Any machine. CutIQ sits between the systems you already run — nothing to rip out, nothing to migrate, no vendor approval required.

Send us a fileHow it works →

CutIQ doesn't replace anything in your stack. It reads what your CAM software already outputs, and hands off structured data to whatever ERP or system you choose. That's the whole architecture.

CAM systems

Any CAM software.
Brand doesn't matter.

Production-ready today. Including but not limited to — if your CAM software outputs structured CAM data, CutIQ can read it.

SigmaNEST
SigmaNEST
SigmaTube
● Production ready
TruTops
TruTops Boost
TruTops Fabrication
● Production ready
BySoft
BySoft 7
BySoft CAM
● Production ready
ProNest
ProNest
ProNest LT
● Production ready
Lantek
Lantek Expert
Lantek Flex3d
● Production ready
AMADA
AMNC 3i
VPSS 3i
● Production ready
!
The five brands above are the shops we built against — they are not the limit of what CutIQ can read. If your CAM software produces structured CAM data, it can be onboarded. Ask us.
Fields extracted across all brands
part_numbermaterial_codethickness_mmquantityprocess_timescrap_pctutilization_pctsheet_countmachine_nameprogram_nameissued_dateremainder_flag
How brand detection works
  • CutIQ identifies the CAM brand automatically from the CAM data layout — no configuration per customer, no manual flag
  • Each brand has a dedicated extraction path with brand-specific field rules and server-side guards
  • If your CAM software isn't on the list, send us a sample — most brands can be onboarded quickly
  • Switching CAM software later doesn't break anything — detection is automatic
ERP systems

Any ERP.
It just receives the data.

CutIQ outputs structured data. Your ERP ingests it. How is your business. We don't write to your ERP directly. We hand off clean, typed JSON — your integration layer, your webhook, your import process.

JobBOSS
Common in job shops and fabricators. CutIQ hands off structured data ready to ingest.
Epicor
Widely deployed in metal fabrication. REST and BPM-based integration paths.
Global Shop
Popular with custom manufacturers. Job and work order data flows in cleanly.
Shoptech E2
Common in small-to-mid fabricators. Straightforward field mapping.
Infor CloudSuite
Larger manufacturing operations. ION API and webhook support.
NetSuite
Cloud ERP used across job shops and contract manufacturers.
SAP S/4HANA
Enterprise-scale operations. Output maps cleanly to production orders.
Fishbowl
Lightweight option for smaller shops. CSV import and plugin API.
Your ERP
If it has an API, a webhook, or accepts a CSV — CutIQ can hand off to it.
→
CutIQ doesn't care what your ERP is. It produces clean, typed output. Every field is labeled, normalized, and ready to map. Your team configures the destination — we supply the data.
Machines

Any machine.
Brand is irrelevant.

CutIQ reads the CAM data — not the machine. The machine brand is irrelevant to CutIQ extraction. For ConfirmIQ live monitoring, machines need OPC UA or MTConnect connectivity.

TRUMPF
Lasers and punch combos. Live monitoring via OPC UA on supported controllers.
OPC UA
Bystronic
Fiber lasers and press brakes. Standards-based connectivity for planned vs. actual.
OPC UA
AMADA
Lasers, punches, and press brakes. CAM data extraction plus controller monitoring.
OPC UA · MTConnect
Mazak
Optiplex fiber lasers and machining centers. MTConnect-native, drop-in connectivity.
MTConnect
Prima Power
Lasers, punches, and bending. OPC UA connectivity for live machine state.
OPC UA
Your machine
If it speaks OPC UA or MTConnect, CutIQ can see it. Brand doesn't matter.
Standards-based
Infrastructure

On-prem, cloud,
or hybrid.

Deploy CutIQ wherever fits your IT footprint. The architecture is the same. Only the hosting changes.

On-premise
Deploy CutIQ inside your network. Data never leaves your infrastructure. Common for shops with strict data residency or enterprise IT requirements.
Cloud
Fastest deployment. CutIQ runs in our managed environment. You access it like any SaaS product. Most shops start here.
Hybrid
ConnectIQ on the shop floor. CutIQ extraction in the cloud. Data routed back to your on-prem ERP. Best of both — and the most common configuration in practice.
Integration architecture

How CutIQ fits into
your existing stack.

No changes to your CAM software
CutIQ reads the CAM data your software already outputs. Nothing changes in the programmer's workflow. They save it exactly as they do today. ConnectIQ catches it automatically.
No changes to your network
ConnectIQ uses dual-network architecture: Ethernet stays on the closed laser network, WiFi connects to the shop network and then to the cloud. Nothing touches the laser network. No IT approval required.
No changes to your ERP
CutIQ hands off structured JSON. Your ERP receives data. You configure the destination — API, webhook, CSV drop, or manual review queue. We supply the clean output. The integration is yours to own.
No vendor dependency
CutIQ doesn't require approval from your CAM vendor, your ERP vendor, or your machine manufacturer. It operates at the data layer. Standards-based where machine connectivity is needed. Proprietary protocols are not used.
Corporate-mandated ERP

Can't change your ERP?
You don't have to.

OEMs, subsidiaries, and contract manufacturers running corporate-mandated ERP systems — SAP, Oracle, Infor, Dynamics — face a different challenge. They can't add modules. They can't change the system. And getting IT to approve an integration takes months they don't have.

CutIQ connects to the ERP the same way your team does — as a named user, with existing transaction permissions, making familiar-looking updates. No IT approval required. No integration project. No corporate review. The shop manager makes the call. The data shows up in the system that day.

Bottom line
Local buying decision. Corporate ERP. No conflict.
FAQ

What shops ask
before they start.

We use a CAM software that isn't on your list. Can CutIQ still read our files?
Probably. The brands listed are the ones production-ready today — they are not the limit. If your CAM software outputs structured CAM data, we can onboard it. Send us a sample file and we'll evaluate it.
Our ERP is older and doesn't have a modern API. Does that break anything?
No. CutIQ outputs structured data to the cloud. From there, you can route it any way you need — including a CSV export, a scheduled batch push, or a manual review queue. The pipeline doesn't require a modern ERP API to function.
Do we need to install anything on the machine or the CAM workstation?
No software installs on the machine or the CAM workstation. ConnectIQ is a Raspberry Pi that plugs into the network. It watches the folder where your CAM software already saves output. Nothing changes for the programmer or the machine.
We're switching CAM software. Will we need to reconfigure CutIQ?
No. Brand detection is automatic. When you switch CAM software, the new CAM data layout is detected automatically — assuming the new brand is already in CutIQ's extraction engine. If it isn't, we add it. Existing brands are never affected.
We cut more than just sheet metal. Plasma, waterjet, press brake. Does CutIQ work for those?
CutIQ's architecture is brand-agnostic and process-agnostic. If your CAM produces structured CAM data, it's the same problem, same solution.
What does ConfirmIQ need from the machine to work?
OPC UA connectivity from the machine controller. The machine must be on a network that the Pi can reach via Ethernet. No proprietary protocols. No vendor SDK. Namespace indices are resolved dynamically — ConfirmIQ works on any OPC UA-enabled machine regardless of how the vendor implemented the namespace.
Not sure if it works with your stack

Send us a file.
We'll show you.

Drop CAM data from your CAM software. We'll run it through CutIQ live and show you exactly what comes out — no slides, no demo environment, your actual data.

Request a demo← Back to platform