The Print Is Stamped ITAR, Do Not Transmit. Put the Shop's AI on a Box in the Tool Crib Instead.

Can you name every file your shop's AI touched last week, and say where each one went?

For most molders the honest answer is no, and for four folders on your server that answer is a problem with a legal shape to it. Not a philosophical one — a clause-in-the-contract one, with a customer's supplier quality manager on the other end of it.

The four folders that legally cannot leave the building

Controlled defense work. If you mold anything on the United States Munitions List — a housing for a night vision assembly, a connector body for an armored vehicle harness — you are registered with DDTC and the technical data is export-controlled. Uploading that print to a general consumer AI service is a transfer, and the fact that it felt like typing into a chat box does not change the regulation.

Customer-owned mold designs. Read your own tooling agreements. Most of them say the mold design, the part geometry, and the process settings developed on it are the customer's property and may not be disclosed to third parties. A CAD model of a competitor-sensitive consumer product is exactly what those clauses exist for.

Medical device records. If you run under ISO 13485 and your customer's device is regulated under 21 CFR Part 820, your device history records, the validation runs, and the deviation reports are part of a regulated record set your customer's auditor will ask about. "It went to a cloud service, we're not sure which region" is not an answer anyone wants to give in an audit.

Formulation detail. Masterbatch letdown ratios, regrind percentages you have agreed with a customer, additive packages a compounder gave you under NDA. That is the recipe. It walks out the door easily and quietly.

What changed in 2026: the box can live in the tool crib

Running capable AI locally stopped being a science project this year. Qualcomm's Dragonwing-class processors put real processing on hardware you can bolt to a wall in a plant, and on the enterprise side the shift is visible: Cisco has been rolling a personal AI agent out to roughly 90,000 employees with an explicit on-premises emphasis, precisely for control and data protection. If a company that size concluded that sensitive material should stay inside its own walls, a 90-person molder with ITAR registration is not being paranoid for reaching the same conclusion.

On-premises AI, for a molding shop, means the machine that reads your prints, mold history cards and process sheets physically sits in your building, on your network, and the documents it reads never travel outside the plant.

The cost picture also moved. High-volume, repetitive local work runs roughly 90% cheaper than sending the same work out to a cloud service — which matters when what you want is an agent that every process tech on every shift queries dozens of times a night.

flowchart TD
  A["Box in the tool crib, on the plant network"] --> B["Mold history cards for 640 tools"]
  A --> C["Setup and process sheets by press and by tool"]
  A --> D["Past corrective actions: splay, flash, short shots, black specks"]
  A --> E["Customer prints marked ITAR or NDA"]
  B --> F{"Does answering this need anything to leave the plant?"}
  C --> F
  D --> F
  E --> F
  F -->|No| G["Process tech gets the answer standing at the press"]
  F -->|Yes| H["Plant manager reviews and approves before anything is sent out"]

What a local agent is actually good at on a molding floor

Not design. Not simulation. What it is good at is the thing that eats your second and third shift: finding what your own shop already learned and forgot.

A shop with 640 tools has 640 mold history cards, most of them handwritten or scanned into a folder nobody indexes. When tool 4412 starts flashing on the parting line at 2 a.m., the useful fact is that it flashed the same way in October 2023, the cause was a nicked interlock, and the tool room shimmed it. That fact exists. It is in a maintenance record, in a corrective action, and in the head of a mold maker who works days.

The same goes for splay on a hygroscopic resin. Your own history says that this nylon needs four hours at 180 degrees F and that the batch that splayed last spring came from a gaylord that sat open over a humid weekend. A local agent that has read every deviation report, every setup sheet, and every corrective action your shop has ever written can put that in front of a process tech in ten seconds instead of thirty minutes of hunting and a phone call to someone at home.

Second shift, 6:10 p.m., a Tuesday

Press 14 starts short-shotting a PC/ABS instrument bezel. The process tech types the tool number and the symptom into the terminal by the tool crib. He gets back: the last three times this tool ran, the fill setting was 1.9 inches per second slower than what is on the current setup sheet; the November corrective action attributed short shots on this tool to a partially blocked sub-gate on cavity 3; and the material lot on the floor is a different letdown than the qualified one.

He checks cavity 3, finds it, calls the tool room lead at home for one two-minute question instead of forty minutes of guessing, and the press is running by 6:45. Nothing about that bezel — a product nobody has announced yet — left the building. The customer's design is still the customer's.

The arithmetic on downtime hunting

Assume 20 presses, two shifts, and roughly 14 troubleshooting events a week where somebody spends real time hunting for history: past corrective actions, setup sheets, the mold history card. Assume the average hunt is 25 minutes today, and the press is down for part of it.

That number will not fund a data center, and it is not supposed to. The real reason to run this locally is the first section of this article: the ITAR folder, the customer-owned tool designs, the medical records. The downtime savings are what makes the hardware pay for itself while it protects you.

Where the box in the tool crib is the wrong answer

A local setup is worse than a cloud service at anything that needs the outside world. It cannot look up a resin datasheet it has never been given, it cannot tell you what a supplier's website says today, and it does not know a thing about a resin grade released last month. If your main need is market research or general writing, run that separately and keep it off the protected side.

Somebody also has to own the box. That means backups, updates, and a plan for the day it fails during a launch build. In a shop with no IT person beyond the controller's nephew, that is a real commitment, not a checkbox. Be honest about who that is before you buy anything.

And local does not mean compliant by itself. If your ITAR obligations require access controls and records of who looked at what, the local machine needs those controls too. A box in the tool crib that anyone can walk up to is a different exposure, not a smaller one.

Frequently asked questions

My customer's contract says "no third-party cloud processing." Does a local setup satisfy that?

Usually yes, but get it in writing from their supplier quality contact and describe what you built: where the machine sits, who can reach it, and that the documents do not leave. Volunteering that description before an audit is far better than answering it during one.

Do I need a server room? I have a tool crib and a very dusty office.

You need a clean, cooled, locked space with a decent network run. Plenty of shops put it in the quality lab, which is already climate-controlled and already restricted because of the CMM. Do not put it near the grinders.

What do I feed it first?

Mold history cards, setup sheets, and every corrective action and deviation report you have written in the last five years. That set is entirely internal, has no export-control question attached, and it is where the answers your night shift needs actually live.

Can the same local setup answer the phone?

Keep those separate. Customer calls are not export-controlled and belong on a system built for phone traffic; the protected material belongs on the local box. Mixing them is how a print ends up somewhere it should not be.

A note on the calls this does not cover

Nothing about a local setup helps with the outside line — the buyer calling at 4:50 p.m. to ask whether the shipment left, the new prospect calling during a mold change when everyone is on the floor. CallSphere builds AI voice and chat agents that answer the shop's phone and website chat, take the caller's part number and purchase order, and book the callback. Keep your controlled prints on the box in the tool crib; let the phone be handled where phones are handled.