Identity and access
SSO via SAML and OIDC, role-based access control, and least-privilege scoping down to the individual line and workflow.
SOC 2 Type I in progress · Type II on the roadmap Aspirational
Write accesshas to beearned.
Duromex asks for permission to change what happens to your product. That is a serious ask, and it is why isolation, auditability, IP protection and fail-safe behaviour were in the first release rather than a later one.
The security baseline
Nothing exotic — just the controls an industrial buyer should refuse to proceed without.
Encryption
Encryption in transit and at rest across the edge runtime, the control plane and every data store.
Multi-tenant isolation
Per-tenant data and model scoping with permission-aware retrieval; no shared vector store, no shared memory.
Immutable audit log
Every agent action, its evidence, its citations and its write, recorded in an assurance-grade quality and safety trail.
Deployment choice
Cloud, factory edge or fully on premises — with regional residency controls for multi-region groups.
Observability
Full tracing, twin and evaluation gating in CI, and runtime guardrails on every agent action.
Your recipes are the asset. We treat them that way.
Scoped by construction
Recipes, BOMs, product specs and quality data live inside your tenant boundary and are retrieved with permission-aware filtering.
- Per-tenant vector stores
- No cross-tenant retrieval path
- Versioned, scoped memory
Federated, not pooled
Cross-factory learning improves shared defect, leak, foam-void and performance models without moving your recipes or quality data.
- Tenant IP boundaries preserved
- Privacy and IP-preserving transfer of fault patterns
- Opt-in participation
Auditable use
You can see what was retrieved, what was cited and what was written — for every action, retrospectively.
- Citation chain per output
- Retrieval provenance retained
- Exportable evidence for auditors
Exit is possible
Your data, and in enterprise agreements the model artefacts trained on it, remain yours and are exportable.
- No data hostage-taking
- Documented export path
- Retention driven by results, not lock-in
Fail-safe is a design property, not a feature
Duromex can write to a press, a foaming machine, an assembly station, a tester and a robot cell. Every one of those write paths is idempotent, scoped, reversible and subordinate to the plant's existing safety systems.
Agents request; the safety layer decides. Graceful degradation and fail-safe stop for press, foamer, robot and product handling are part of the non-functional requirements, not an add-on.
Safety controls
- Idempotent agent steps with graceful degradation
- Fail-safe press, foamer, robot and line stop
- Human checkpoints on safety and warranty decisions
- Authority envelopes scoped per line and revocable
- Edge autonomy that survives a WAN outage
- Twin validation before any process change
The standards this work sits under
Appliance manufacturing is regulated on safety, energy and refrigerants. Duromex captures the evidence as a by-product of running the line.
| Area | What applies | How Duromex helps |
|---|---|---|
| Product safety | IEC 60335 appliance safety | Test acceptance evidence and traceability captured per unit |
| Energy | Energy-efficiency regulations and ratings | Thermal-performance forecasting and rating conformance tracking |
| Refrigerants | F-gas and refrigerant regulations | Leak detection, charge accuracy and loss tracking with evidence |
| Quality systems | Non-conformance, disposition and traceability | Immutable action log integrated with MES and quality systems |
| Information security | SOC 2 Aspirational | Type I in progress, Type II on the roadmap |
| Data protection | Regional residency requirements | Regional deployment and on-prem options |
Nothing reaches a line without passing two gates
This is how a validated process stays validated.
Evaluation gate
Golden datasets and judge models evaluate every model and prompt change in CI. A regression blocks the release.
Twin gate
Recipe, layout and changeover changes are simulated in the line-and-product twin and must hit the predicted quality, yield and takt targets.
Canary rollout
Signed OTA updates roll out to a canary line first, with automatic rollback on regression.
Human checkpoint
Anything touching safety, warranty or a validated process requires explicit human approval, recorded in the audit trail.
For IT, OT, quality and security
The four groups who can stop a deployment, and what each one gets.
IT
SSO, RBAC, encryption, tenancy isolation, documented data flows and an on-prem option.
OT
Scoped write authority, fail-safe stop, offline-capable edge and no dependency on a WAN link for control.
Quality
IEC 60335 evidence, non-conformance integration, immutable traceability and twin-gated change control.
Security
Audit logging, IP protection, least privilege, canary and rollback, and the SOC 2 roadmap.
Assurance is produced by running, not by reporting
Every stage the unit passes through leaves signed evidence: what was seen, what was decided, what was written and who approved it. The audit trail is a by-product of the loop, not a separate exercise.
Form & stampWeld & seamEnamel & paintFoam & insulateWire & assembleLeak & function testRate & pack
Where we are today
Duromex is pre-launch. This is stated plainly rather than implied otherwise.
Type 1
SOC 2 in progress Aspirational
0
customer data used for cross-tenant training
100%
actions with retained evidence
24 h
target initial response on security enquiries
What got us through review
“Our end-of-line functional testers told us what failed. They never told us which press stroke or foam shot caused it. That link is the whole product.”
“Foam voids are invisible until the energy rating comes back wrong. Predicting density distribution before the cabinet cures is the part I could not buy anywhere else.”
“If it writes to the press, it needs an audit trail a quality auditor accepts. Duromex started there instead of bolting it on.”
Detailed answers
Do you train shared models on our data?
Not in a way that moves your data. Cross-factory learning is federated and preserves tenant IP, product recipes and quality data boundaries. Participation is opt-in.
Where is the audit log stored and can we export it?
It is written at the edge and replicated to your tenant in the control plane, or kept entirely on premises in an on-prem deployment. It is exportable in full.
What is your vulnerability disclosure process?
Report to security@duromex.com. We acknowledge within one business day and will agree a remediation timeline with you. Aspirational A formal programme launches with general availability.
Can Duromex operate with no outbound internet access?
Yes, in the on-prem configuration. Model updates are then delivered through a controlled, signed offline channel.
Send us your security questionnaire.
We would rather answer 200 questions now than lose your trust after we have write access to a press.
Duromex is pre-launch. Figures shown are design-partner targets and modelled economics, not audited results. Ask us for the methodology.