LOKI runs completely locally on your hardware. It finds specifications, batch records, lab results and approvals in one go. Every answer comes with its source.
Batch 240817: what all has lot L-4211 in it, and where did that ship out to?
The lot is in three batches from line 2 [1]. Lab results for all three are on file and show no findings [2]. Deliveries went to two retail customers and one wholesaler; the delivery notes with dates and quantities are on file [3].
The supplier’s changing flavor A-118. Which products and labels are affected?
The flavor is in four recipes [1]. Two of them carry allergen labeling that has to be reassessed [2]. One customer specification requires the retail customer’s written approval for recipe changes; the clause is highlighted [3].
I need the complaints from the last 12 months for the audit report, split by consumer, retail and authority.
47 in total: 31 from consumers, 14 from retail, 2 from authorities [1]. The three most frequent causes are broken down, foreign bodies separated by type [2]. The report is ready as a Word draft in the audit template format [3].
From family-run businesses to DAX corporations. Machine building, chemicals, and the public sector.
Protection status, customer contracts and audits hang on it.
A recipe is legally protected only for as long as it is subject to appropriate confidentiality measures. Entering it into a third-party service risks more than the data flowing out: it risks the protection status itself.
With private labels, the retailer owns the brand, and the specification is their property. If you fill for several competing chains, you carry a contractual risk that goes beyond a pure data-privacy issue.
Traceability is a KO requirement in the IFS audit and must be demonstrable in both directions within four hours. That evidence must belong to you.
Under IFS Food, the customer agreement, raw-material specifications, traceability and the recall procedure are KO requirements. A D rating on any one of them costs 50 percent of the total score. Four of the ten make-or-break questions of an audit hang on whether documents can be found.
Every third IFS audit must be unannounced, within a window from 16 weeks before to 2 weeks after the due date. Refuse the auditor access and you lose the certificate within two working days and get invoiced for the audit costs.
Update the finished-product specification, bring raw materials, process and packaging in line, check labeling against the law of every destination country, validate nutrition values and claims across shelf life, release the label, update retail specifications and master data, recalculate the Nutri-Score. A raw-material change is never just a raw-material change.
That is how long a position in the food industry stays vacant on average, and the trend is rising. A person-to-person handover structurally fails at that duration: almost a full working year lies between departure and replacement.
The knowledge is in the building. It just sits in the ERP, the lab system, specification PDFs, label approvals and the inboxes of QA and sales all at the same time.
Your knowledge sits in four worlds that don’t know each other: batches in the ERP, results in the lab system, specifications as PDFs, approvals in the inbox. Only 39 percent of ERP users get end-to-end traceability out of their system. LOKI puts one search across all four: on your hardware, with a source for every answer.
Batch record, lab result, specification PDF, 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, 9:10 a.m. The audit arrives unannounced, the traceability test begins. The four hours are running.
Batch 240817: what all has lot L-4211 in it, and where did that ship out to?
The lot is in three batches from line 2 [1]. Lab results for all three are on file and show no findings [2]. Deliveries went to two retail customers and one wholesaler; the delivery notes with dates and quantities are on file [3].
Gathering everything is the part that takes longest today. That part gets short.
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.
Which allergens have to go on the label for recipe R-2043[RECIPE]? It contains 12.5 % fruit content[QUANTITY] and flavor A-118[RAW MATERIAL].
Protokoll14:38 · M. Vogt · 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.
Under IFS Food, the customer agreement, raw-material specifications, traceability and the recall procedure are KO requirements; a D rating costs half the total score. Add the HACCP documentation, traceability under Article 18 of Regulation (EC) 178/2002 and the allergen and declaration duties of the LMIV. For mineral and table water the German Mineral and Table Water Ordinance applies on top, for medicinal water the authorization under the German Medicinal Products Act. LOKI opens up these evidence chains without a single document leaving your building.
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: emails, scans, approvals, legacy archives.
LOKI finds every article containing this raw material, the affected allergen and nutrition declarations, the customer specifications that require written approval of the change, and the labels that need to be redone.
The cascade becomes visible before it starts running.
The IFS report asks for the complaints of the last twelve months: split by consumers, retail and authorities, with the three most frequent causes and the types of foreign bodies. LOKI aggregates that across your systems instead of three colleagues counting for a week.
Data aggregation across twelve months and distributed systems: the textbook case for a knowledge assistant.
Every chain sends its own requirements document, every version replaces the last. LOKI opens up the PDF archives including scans and answers with the exact source: which clause applies, in which version, for which article.
The answer names document and page, verifiable before every customer email.
Also: document the post-audit action plan with implementation evidence · keep supplier ratings and certificate deadlines in view · keep the allergen overview up to date across all recipes · incoming-goods inspection against specification · prepare the traceability and recall test on the twelve-month cycle
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 was written down. But a lot happens on the line that never makes it into a document: temperatures, pressures, cycle times, cleaning cycles. MINERVA captures them at the machine, with its own boards in your own network, and turns them into sources LOKI can cite.
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 running production systems.
We look at where your records live (ERP, lab system, specification folders, inboxes) and tell you honestly what LOKI can open up from them.
The hardware goes behind your firewall. The standard data connections are hooked up, with no intervention in running production systems.
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.
It shortens the part that takes longest today: gathering everything. Batch links, lab results, delivery notes and customer assignments sit in several systems at most plants; LOKI queries them in one request and names the source for every data point. Responsibility for the test and its documentation stays with you. LOKI delivers the evidence, never the sign-off.
The question is fair, and the answer is the reason LOKI exists. The language model runs on your hardware behind your firewall. There is no API call to OpenAI, Anthropic or Google and no training on your data by third parties. You define who may see which documents through roles: the recipe is never automatically visible to everyone in the plant.
No. Your QA system stays the leading source for processes and approvals, your specification software for recipes and declarations. LOKI puts the search across everything that sits next to them: email threads on deviations, lab findings, customer correspondence, old batch files, audit reports from previous years.
Yes, through tenant separation and role-based access. With private labels this is no mere convenience: the retailer owns the brand, and their specification is their property. We set up the separation together with you before the rollout.
That is the use case it was built for. LOKI opens up PDF archives including scans via text recognition and answers with the exact source. With handwritten entries the hit rate drops; we tell you that up front.
No. Around 70 percent of food businesses in Rhineland-Palatinate have between 20 and 49 employees. Your size is the rule, never the exception. And the documentation burden per head is higher for you than for a corporation with twenty people in QA.
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. We’re based in Hoppstädten-Weiersbach on the Nahe, and we come to your site. We’ll also tell you if LOKI isn’t the right step for your data situation yet.