Drawings and NC programs
Your customers’ know-how, often under NDA. Many framework agreements in the automotive, defense and plant-engineering sectors explicitly prohibit uploads to third-country clouds.
LOKI runs fully local on your hardware. It finds drawings, process plans, inspection records, material certificates and mailboxes with a single question. Every answer names its source.
The customer wants the 3.1 certificate for batch 84120. Where is it, and where did the rest of the bar go?
The EN 10204 inspection certificate is filed with the goods receipt from 12 May [1]. The batch went into three orders, the cutting list shows dimensions and remaining length [2]. The delivery note for the customer order lists position and quantity [3].
Complaint about part 4711. What measurements do we have, which tool was in, which program version?
The measurement report from the final check shows all dimensions in tolerance [1]. The machine data collection (BDE) journal records a tool change in the middle of the batch [2]. And the NC program version was changed two days earlier, the change note states the reason [3].
Have we made a part like this before? And what went wrong back then?
Yes, in 2024 with a similar geometry [1]. The post-costing shows the setup time ran twice as long as planned [2]. The meeting minutes state the reason: the fixture had to be modified twice [3].
From family-run businesses to DAX corporations. Machine building, chemicals, and the public sector.
NDAs, liability and your margin depend on it.
Your customers’ know-how, often under NDA. Many framework agreements in the automotive, defense and plant-engineering sectors explicitly prohibit uploads to third-country clouds.
Hourly rates, setup times, scrap rates: whoever reads them knows where your margin sits. None of it belongs in someone else’s data center.
EN 10204 material certificates, measurement reports, batch traceability: liability-relevant for years. And in a complaint case, your defense.
EU Machinery Regulation 2023/1230, binding from January 2027, requires technical documentation including risk analyses, drawings and software logic, for ten years. Add initial sample inspection reports and batch records that customers still ask about years later. All of it is filed. Just in five different places.
ISO 9001, IATF 16949 for suppliers, and customer audits in between: document control, measuring equipment monitoring, training records, 8D history. If you have to hunt for evidence first, you lose audit days and trust.
Machinists and setup technicians have been on the German Federal Employment Agency’s shortage list for years. Why a part runs at reduced feed and which fixture takes out the vibration lives in setup sheets, deviation approvals and in heads that are leaving.
Orders in the ERP, inspections in the CAQ, NC programs and setup sheets on the file server, machine times in the BDE, agreements in the mailbox. None of these systems can search the others.
The knowledge is in the building. It just sits in the ERP, the CAQ, the CAM folder, the BDE journal and the project manager’s mailbox all at once.
Your knowledge lives in four worlds that don’t know each other: orders and costing in the ERP, inspections in the CAQ, NC programs and setup sheets on the file server, agreements in the mailbox. LOKI lays one search across all four, fully on your hardware, with a source for every answer.
ERP order, CAQ inspection, NC folder, mail thread.
LOKI opens up all four, following your role-based access.
No system knowledge, no file names, no folder hunting.
Every statement carries the source it came from.
One question. Four systems. One answer that tells you where it knows it from.
Thursday, 7:40 a.m. The customer reports a dimensional deviation. The 8D report is due by Monday.
The customer wants the 3.1 certificate for batch 84120. Where is it, and where did the rest of the bar go?
The EN 10204 inspection certificate is filed with the goods receipt from 12 May [1]. The batch went into three orders, the cutting list shows dimensions and remaining length [2]. The delivery note for the customer order lists position and quantity [3].
The report cites evidence instead of memories: measurement report, tool change, program version.
Your team wants to work with the best models, and does so anyway, if need be around the official toolbox. LOKI turns that into an official path: you connect external models, and every request passes through a check first. Names, order numbers, part identifiers and amounts are detected and redacted before the prompt leaves the building.
Summarize the complaint from Brandt[CUSTOMER] about drawing 4711-B Rev. C[DRAWING] for me. Dimensional deviation on the Ø 12 H7[FEATURE].
Protokoll07:58 · M. Weber · Claude Opus 4.8 · 3 findings redacted · sent
Name recognition and configurable patterns find what must not go out.
The user sees in the chat what was found and chooses: send anonymized, send unchanged, or cancel.
Every call is in the log, with user, model, time and the result of the check. Including the cancelled ones.
And this is what the switch looks like in the product: choose a cloud model and it tells you right above the input field.
That’s the difference between a ban that gets bypassed and a path you’re allowed to take.
We don’t have to vouch for the architecture ourselves. The conference of Germany’s data-protection authorities (DSK) described it before we built it.
The DSK’s guidance on AI and data protection states that technically closed systems are preferable from a data-protection perspective: in open systems, the input data leaves the users’ protected environment. With LOKI it doesn’t.
Inside a language model itself there is no way to control who may see which information; the supervisory authorities state this explicitly. In the knowledge system in front of it, tenant separation and role-based access do work. That’s why LOKI is built this way. And that’s why individual entries can be deleted deliberately instead of disappearing into a model.
EU Machinery Regulation 2023/1230 requires documented software and AI aspects in the technical documentation from January 2027. Suppliers inherit their customers’ documentation duties, from document control under IATF 16949 to the NIS2 supply chain for anyone supplying critical-infrastructure industries. A stack that runs entirely on your premises is one line of answer in the supplier questionnaire instead of an essay of justification.
The regulators call this a mitigating measure, not a blanket solution, and name open questions around transparency and data-subject rights. We put it exactly the same way.
Without you changing your system landscape.
LOKI replaces none of these systems; they stay in charge. LOKI makes findable what lies between them, and turns it into finished documents: the 8D draft, the certificate bundle for the batch, the audit template.
LOKI finds the measurement reports, the tool change in the BDE journal, the NC program version with its change note and the sorting inspection of the remaining batch, every point with a source for D2 through D5.
The report cites evidence instead of memories.
Measuring equipment monitoring, training records, control of specification documents, 8D history: LOKI delivers the status and source of every record. You find the gaps before the audit, instead of during it.
The audit checks the chain of evidence, not the machine.
Why the part runs at reduced feed, which fixture takes out the vibration, where the deviation approval sits: LOKI finds the setup sheet, the change note and the mail in which it was decided.
The successor inherits the machine, and its memory along with it.
Also: pull material certificates for a batch in seconds · compile initial sample inspection reports · keep the maintenance history of each machine in view · search quotes for similar parts · compile technical documentation for the EU Machinery Regulation
With our locally installed AI assistant from IGNAITE, our employees can access company knowledge much faster. For example, information from past projects. This enables higher productivity and, above all, more comprehensive knowledge sharing.
In our collaboration with IGNAITE, we built a practical, high-performance computer-vision solution that has sustainably improved our incoming-materials processes. What particularly convinced us was the structured approach, the deep process understanding, and the ability to translate complex requirements into pragmatic solutions.
LOKI opens up what has been written down. But a lot happens at your machines that never makes it into a document: spindle currents, vibrations, temperatures, cycle times, downtimes. MINERVA captures them at the machine, with its own boards in its own network, and turns them into sources LOKI can cite. The vibration curve of the milling machine becomes a record with a source.
Extendable with MINERVABoth products follow the same principles: sovereign, source-based, local. You start with one and add the other when you need it.
From order to productive operation in under four weeks — with no intervention in machines or controls.
We look at where your records live (ERP, CAQ, CAM folders, mailboxes) and tell you honestly what LOKI can open up from them.
The hardware goes in behind your firewall. File shares, ERP, CAQ and mail server are connected, with no intervention in running machines or controls.
We hand over only once it runs production-ready. The EU AI Act has required you since February 2025 to train your staff in the competent use of AI; we deliver that training.
We open up the relevant content: drawing PDFs including title block and revision status, bills of materials, NC programs as text, setup sheets and the metadata of the CAD archive. The aim is to answer the question "Where is the valid revision?" in seconds, with no ambition to replace your CAD. What is specifically possible in your landscape is something we clarify before the installation.
Only your own. LOKI runs on your hardware behind your firewall: no upload, no API call to OpenAI, Anthropic or Google, no training by third parties. And role-based access governs who in the building may see what: sales sees no NC programs, the shop floor no costing.
LOKI answers based on sources and names the document behind every statement, verifiable before anything goes into production or a report. And we draw one line deliberately: LOKI issues no production releases. It finds; deciding stays with QA and the foreman.
No. Your QM system remains the leading source for controlled documents, your CAQ for inspections. LOKI changes nothing about that. It makes findable what sits alongside: the mail about the deviation approval, the scanned legacy report, the 8D report from 2022.
No. Scanned documents are processed with text recognition. With handwritten entries the hit rate drops. We tell you that up front instead of promising otherwise.
Yes, through tenant separation and role-based access: whoever isn’t allowed to see a project doesn’t see it, including through search. We set up that separation together with you before the rollout.
A fixed monthly price plus a one-time setup fee that includes the server hardware. The license covers unlimited users. There are three packages that differ in hardware sizing. Operation, maintenance, updates and support are included. We’ll give you the specific price in the intro call.
The industry pages show LOKI in the everyday work of individual industries. If yours is missing, that only means we haven’t written it up yet.
30 minutes, an honest assessment. No slides, no sales pressure. We’ll also tell you if LOKI isn’t the right step for your data situation yet.