ADAM OS
The manufacturing execution system built to run the Omnifactory, and a growing standardisation and productisation effort that is now partly in your hands.
What ADAM OS is
ADAM OS is Arridex's internal Manufacturing Execution System for the Omnifactory, managing the operational stages covered on the Additive Manufacturing Domain page: unit traceability, per-unit Certificate of Conformity generation, quality workflows, and the operational data a modern AM factory needs to run reliably and produce certifiable output. Development has progressed through multiple phases, with recent work covering unit traceability, per-unit CoC generation, an email notification system, and platform-level improvements such as a global error handling page.
The hub-and-spoke model
ADAM OS is architected around Arridex's 'Africa's Distributed Additive Manufacturing' (ADAM) Network, a distributed manufacturing network that is designed around a hub-and-spoke model: a central hub node coordinates activity, while spoke nodes of different types handle specific parts of the manufacturing process. This allows ADAM OS to scale beyond a single factory floor, coordinating multiple manufacturing locations or functions under one system, rather than each site running in isolation. Understanding the specific node types and how they communicate is one of the first things to establish through direct discovery sessions with the development team, since this architecture is central to any future standardisation or external licensing work.
Why external licensing is plausible
ADAM OS was built to solve Arridex's own operational problem of running the Omnifactory. But the underlying problem, coordinating traceable, certifiable, on-demand manufacturing, is not unique to Arridex. Other AM operators face the same operational complexity described on the previous page, and there has been emerging external interest in ADAM OS as a product in its own right, not just an internal tool. Turning that interest into something sellable requires deliberate work: understanding what would need to change for multi-tenant, multi-customer use, and packaging the platform in a way a prospective customer can actually evaluate.
Where things stand
The right first step towards getting started with ADAM OS is establishing a current, verified picture directly with the development team through structured discovery, covered further on the ADAM OS 90-day priorities page.
The development of Arridex's software platforms increasingly relies on AI coding agents rather than every line being written manually by a developer. Because AI agents can drift from a specification over a long session, or produce code that passes visible tests while missing edge cases, it is important to establish a set of development rules and disciplines to govern how these agents are briefed, constrained, and checked for effectiveness, and how code is checked for quality. This is part of the standardisation work in front of you.