Koddex links requirements, system design, components and certification documentation. Every change stays traceable, every file stays ready for the certification audit.
The systems behind today's complex hardware products still rely on disconnected files, spreadsheets and siloed tools. For a regulated, safety-critical product, that isn't a tooling problem. It's an infrastructure problem.
When you read a value in Koddex, you know it's right, structurally guaranteed. Every baseline verifiable, every design decision explainable to an auditor or a regulator.
Typed objects, explicit relationships, deterministic workflows. But the business logic is yours. You model your own reality, from the 20-person startup to the global industrial group.
We remove the administrative noise of chasing versions and rebuilding context, so teams can focus entirely on their mission. Software should extend the craft, not get in its way.
« Rigor shouldn't be a brake on innovation. It should be the infrastructure that makes innovation possible. »
« Complex hardware demands a rigorous, regulated methodology. We instill a mindset of flexibility within that rigor, so engineers adapt fast without compromising structure. »
Configuration management for a reactor programme lives in a single spreadsheet. It holds, because the people who wrote it are still there. Nobody has asked what happens when they are not.
for the configuration of a whole reactor programme
« We need to get professional about this. »
How do you answer that today?
Configuration is a locked structure, not a file someone maintains.No PLM. Each project manager tracks the standards their own way, in their own Google Docs and spreadsheets. Which means nothing is tracked. Finding out what was decided means finding the person who decided it.
one per project manager, so none
« To put it kindly, requirements were followed artistically. Everyone had their own method, so nothing was tracked. »
Standards get revised a handful of times in a career, so people stay confident in the version they learned. Then two thousand units have to be built to it, by technicians nobody trained on the current text.
to a standard that ages in people's heads
« He was completely sure of himself — on a version of the standard that was true fifteen years ago. »
One spreadsheet, one author, one convention nobody else was taught.
The file stays. The reasoning behind half its columns does not.
Technicians are trained on the baseline someone remembers, not the one in force.
Build your single source of truth. Define your own component blueprints.
Automate critical roll-ups. Changes propagate deterministically.
Secure your baselines. A locked baseline is a structural guarantee.
Make your lifecycle audit-proof. Requirements linked to physical results.
Define your engineering objects once. Lock the structure for audit. Revise with full traceability without breaking certification.
A living tree, every discipline edits the same model. No exports, no version confusion.
Freeze a baseline, keep V1 in production, revise V2 on its own branch with zero collisions.
RCC-M, IEC 61513, IEC 60880, ISO 19443. Calibrated by sector from day one.
A single changed component can affect more than 200 dependencies. Catch every deviation before the commit, not three weeks later.
Attributes nested at every level, mirroring a real assembly.
Mass, size and coefficients linked by formulas. A value never lives alone.
An out-of-spec requirement is flagged instantly, the moment a value moves.
Audit prep isn't a project. It's a click. The activity history is queryable from program level down to a single attribute.
Every action logged with author, timestamp and justification.
Exactly the scope they need. No oversharing, no confidential leak.
Nuclear, energy, defense. Structured for every safety authority.
Koddex exposes a Model Context Protocol (MCP) so AI agents read, write and automate inside your system models.
Agents authenticate and receive typed scopes. Every read and write is fully logged.
Targeted rights on precise entities. The same approval workflow as your engineers.
Actor, timestamp, diff, impact, all logged. No agent bypasses a locked baseline.
Every role plugs into the same backbone as your PLM, ERP, CRM and tools. One traceable source of truth. No migration, no disruption.
Koddex is API-first: any tool that exposes an API can read from and write to Koddex. Read this as what the architecture reaches, not as connectors already shipped.
+ 80 integrations · API-first · OAuth or token · bidirectional sync · EU hosting · SOC 2
« We need to get professional about this. »
« To put it kindly, requirements were followed artistically. Everyone had their own method, so nothing was tracked. »
« He was completely sure of himself — on a version of the standard that was true fifteen years ago. »
« Nobody knows the standard to the letter. You end up on some tiny detail that was never settled. »
Deployment and saving figures are ranges observed on deployments Koddex runs alongside the team, not an audited average. Scope, team size and regulatory load move each one.
A custom metamodel framed to your product. Objects, attributes, relationships mapped.
BOM, requirements and data migrated. Permissions and roles configured.
Role-based sessions for engineering, quality, PM. Autonomous in under a week.
Change control, design freeze, audit trail, live on Koddex. First locked baseline.
AI integrations, external sharing, impact analysis.
« Onboarding is human and hands-on. We sit alongside your team to build a rigorous, custom infrastructure with limitless flexibility, so you ship the most demanding products. »
A demo on nuclear use cases, ideally with several members of your team. We gather your requirements live.
Book the demo →Verbatims: what hardware teams say about Koddex.