Workers moving a fabricated steel part with an overhead crane in a machining workshop
    Connected factory · Automation · IIoT
    THE ENGINEERING OPERATING SYSTEM FOR REGULATED HARDWARE INDUSTRIES

    Design, certify and industrialize your production lines.

    Koddex links requirements, system design, components and certification documentation. Every change stays traceable, every file stays ready for the certification audit.

    koddex.app · IND-SYS-001
    Forge X-9 · Production line
    IND-SYS-001
    Locked
    ContentAccessFilesActivity
    StatusBaseline locked · Rev 3.1
    Nominal throughput1,200 u/hƒ computed
    Requirement coverage94%
    StandardsIEC 62443 · ISA-95
    Components2
    ItemCell controller (PLC)Locked
    ItemRobotic cellIn review
    OUR VISION

    We build the digital infrastructure for those who design complex physical systems.

    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.

    Absolute trust by design.

    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.

    Structured, yet malleable.

    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.

    Execution is a craft.

    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. »

    Stéphane Dicostanzo, Founder & CEO · Koddex
    Stéphane Dicostanzo
    Founder & CEO · Koddex

    « Complex hardware demands a rigorous, regulated methodology. We instill a mindset of flexibility within that rigor, so engineers adapt fast without compromising structure. »

    Thomas Le Blanc, VP of Engineering · Koddex
    Thomas Le Blanc
    VP of Engineering · Koddex
    INDUSTRY & SUBCONTRACTING · WHAT WE HEARD, NOT WHAT WE ASSUMED

    One list doing three jobs, and a drawing office absorbing the difference.

    Three bills of materials pretending to be one

    Engineering, process and production each need a different view of the same product. There is one BOM, so aligning them means rewriting drawings that did not need to change — and the engineering office absorbs it.

    3views, one BOM

    so every change means redrawing

    CAD model
    Engineering BOM
    « the same list, three jobs »
    Process BOM
    Production BOM
    « Aligning the engineering and production BOMs forces pointless drawing updates that overload the engineering office. »
    Hardware Manager · Medical gas equipment
    When it gets paid forEvery engineering change

    How do you answer that today?

    One structure, three views. Each discipline reads what it needs.

    Between the PLM and the ERP, there is Excel

    Design data sits in the PLM, production data in the ERP. Neither speaks to the other, so the gap is filled by Word and Excel files, maintained by hand, trusted by nobody, and referenced by the drawings.

    2systems

    and a hand-maintained gap between them

    Paper ECR
    « retyped by hand »
    ECO in the ERP
    « There is a gap between our PLM and our ERP, filled with Excel and Word files. Traceability becomes a nightmare. »
    Hardware Manager · Medical gas equipment
    When it gets paid forHandover to production
    One graph under both. The gap has nowhere left to be.

    Three sites, three continents, one machine

    The same machine is configured and built on three continents. Each site rebuilds the bill of materials line by line from the others' exports, because there is no structure all three can write into.

    3sites

    no shared source, BOMs retyped line by line

    « If it is complicated, people simply do not do it. »
    Engineering Manager · Ground support equipment
    When it gets paid forEvery site synchronisation
    One workspace the three sites write into, not three that export.

    Requirements live on an intranet from the 2000s

    Requirements are held in an in-house intranet nobody maintains any more. Whether a mechanical part is traced back to the requirement it satisfies is left to each engineer's judgement, so coverage is whatever the last engineer felt was enough.

    1legacy intranet

    mechanical traceability left to the engineer's discretion

    « The tool has to be simple enough for non-technical profiles, or it will not be used. »
    Engineering Manager · Ground support equipment
    When it gets paid forDesign gate review
    Coverage is computed, so it stops depending on who was careful.

    The reliability tests do not match how customers use it

    The bench tests pass. Then the machine meets an apron in July, a night shift and an operator in a hurry, and fails in a way no test described. The gap only shows up as field returns, a year after sign-off.

    0tests in real conditions

    reliability proven on the bench only

    Bench test
    « never described anywhere »
    Real conditions
    Field return
    « Our reliability testing is not representative of the conditions the customer actually runs in. »
    Engineering Manager · Ground support equipment
    When it gets paid forField returns
    A test condition is an attribute, so a gap in it is visible before shipping.
    REGULATORY LANDSCAPE
    IEC 62443ISA-95OPC-UARAMI 4.0IEC 61508Directive MachinesCEISO 9001ISO 27001

    The drawing is redone now. The field return arrives a year later.

    1. J+0
      One BOM line changes

      Engineering updates its view. Process and production find out by export.

    2. J+30
      Drawings are reworked

      Aligning the three views forces changes to drawings that were correct.

    3. J+365
      Field returns

      The machine fails in conditions no bench test ever described.

    PLATFORM OVERVIEW

    One backbone for a structured, traceable and computable product.

    Visual metamodeling

    Build your single source of truth. Define your own component blueprints.

    Graph-level computation

    Automate critical roll-ups. Changes propagate deterministically.

    Lock & revision control

    Secure your baselines. A locked baseline is a structural guarantee.

    End-to-end traceability

    Make your lifecycle audit-proof. Requirements linked to physical results.

    koddex · visual metamodeling
    SHIP ON TIME. EVERY TIME.

    Write the BOM you actually ship, then lock it.

    Define your engineering objects once. Lock the structure for audit. Revise with full traceability without breaking certification.

    Define once, reuse across the whole BOM

    A living tree, every discipline edits the same model. No exports, no version confusion.

    Lock, branch and revise safely

    Freeze a baseline, keep V1 in production, revise V2 on its own branch with zero collisions.

    Certification-ready templates

    IEC 62443, ISA-95, IEC 61508, CE. Calibrated by sector from day one.

    1 living BOM0 V1/V2 conflicts÷3 release lead time, observed
    koddex · lock & revisions
    SEE EVERY IMPACT, BEFORE IT HITS.

    Visualize the full impact of every change.

    A single changed component can affect more than 200 dependencies. Catch every deviation before the commit, not three weeks later.

    Items within items

    Attributes nested at every level, mirroring a real assembly.

    Computation links every attribute

    Mass, size and coefficients linked by formulas. A value never lives alone.

    Catch the deviation before the commit

    An out-of-spec requirement is flagged instantly, the moment a value moves.

    koddex · graph-level computation
    PASS YOUR AUDIT, WITHOUT THE 3-WEEK SPRINT.

    Every change already traced. You just click Export.

    Audit prep isn't a project. It's a click. The activity history is queryable from program level down to a single attribute.

    COMPLIANCE LEVEL · LIVE
    Directive Machines · Sécurité94%
    IEC 62443 · Cybersécurité81%
    ISO 9001 · Qualité76%
    koddex · traceability

    Activity history at every level

    Every action logged with author, timestamp and justification.

    Targeted export to auditors & suppliers

    Exactly the scope they need. No oversharing, no confidential leak.

    Certification-ready evidence

    Industry, automation, manufacturing. Structured for every quality audit.

    YOUR TOOLS. YOUR AGENTS. ONE PRODUCT RECORD.

    Let AI agents work inside your design record.

    Koddex exposes a Model Context Protocol (MCP) so AI agents read, write and automate inside your system models.

    Native MCP access

    Agents authenticate and receive typed scopes. Every read and write is fully logged.

    The same rules as humans

    Targeted rights on precise entities. The same approval workflow as your engineers.

    Full audit trail

    Actor, timestamp, diff, impact, all logged. No agent bypasses a locked baseline.

    Claude / GPTKoddex MCPProduct graphTargeted permissionsFull audit trail
    Model in daysminutes.
    ENTERPRISE BACKBONE

    Koddex becomes the backbone of your organization.

    Every role plugs into the same backbone as your PLM, ERP, CRM and tools. One traceable source of truth. No migration, no disruption.

    A few of the tools Koddex could plug into
    Siemens logo
    SiemensPLM · MES
    Dassault Systèmes logo
    Dassault SystèmesCAD · PLM
    Autodesk logo
    AutodeskCAD
    SAP logo
    SAPERP
    Rockwell Automation logo
    Rockwell AutomationMES
    Jira logo
    JiraALM
    Confluence logo
    ConfluenceDocs
    GitHub logo
    GitHubCode
    Microsoft Excel logo
    Microsoft ExcelSpreadsheet
    Google Sheets logo
    Google SheetsSpreadsheet
    Anthropic logo
    AnthropicAI agents
    n8n logo
    n8nAutomation
    Siemens logo
    SiemensPLM · MES
    Dassault Systèmes logo
    Dassault SystèmesCAD · PLM
    Autodesk logo
    AutodeskCAD
    SAP logo
    SAPERP
    Rockwell Automation logo
    Rockwell AutomationMES
    Jira logo
    JiraALM
    Confluence logo
    ConfluenceDocs
    GitHub logo
    GitHubCode
    Microsoft Excel logo
    Microsoft ExcelSpreadsheet
    Google Sheets logo
    Google SheetsSpreadsheet
    Anthropic logo
    AnthropicAI agents
    n8n logo
    n8nAutomation

    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

    IN THEIR WORDS

    Sentence you have already said yourself.

    « Aligning the engineering and production BOMs forces pointless drawing updates that overload the engineering office. »
    Hardware Manager · Medical gas equipment
    Industry & subcontracting
    « There is a gap between our PLM and our ERP, filled with Excel and Word files. Traceability becomes a nightmare. »
    Hardware Manager · Medical gas equipment
    Industry & subcontracting
    « If it is complicated, people simply do not do it. »
    Engineering Manager · Ground support equipment
    Industry & subcontracting
    « The tool has to be simple enough for non-technical profiles, or it will not be used. »
    Engineering Manager · Ground support equipment
    Industry & subcontracting
    « Our reliability testing is not representative of the conditions the customer actually runs in. »
    Engineering Manager · Ground support equipment
    Industry & subcontracting
    « We have no technical data management tool at all. Searching and proving compliance are both hard. »
    Technical Director · Medical components
    MedTechIndustry & subcontracting
    « If it is complicated, people do not do it. »
    Design Lead · Medical imaging
    MedTechRoboticsIndustry & subcontracting
    PROOF BY THE NUMBERS

    Finally, an Engineering Operating System for the talents shaping our future.

    +1 000
    licenses deployed, cumulative since 2024
    80
    industrial tools reachable through the open API
    30%
    saved on tools & software licenses, observed on guided deployments
    ÷3
    admin tasks & data collection, observed on guided deployments

    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.

    IMPLEMENTATION

    Operational in days. Audit-ready in months.

    1

    Architecture workshop

    A custom metamodel framed to your product. Objects, attributes, relationships mapped.

    2

    Import & configuration

    BOM, requirements and data migrated. Permissions and roles configured.

    3

    Training & handover

    Role-based sessions for engineering, quality, PM. Autonomous in under a week.

    4

    First workflows in production

    Change control, design freeze, audit trail, live on Koddex. First locked baseline.

    5

    Scale & autonomy

    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. »

    Valentin Houssin, Product & Customer Success Lead · Koddex
    Valentin Houssin
    Product & Customer Success Lead · Koddex
    Day 5
    Models created, data structured and collected on Koddex
    Day 14
    Models consolidated and operational. Full autonomy
    Day 90
    Your teams onboarded and trained on Koddex
    Deep support · first 90 daysSupport & CSM guaranteed for 2 years · maintenance within 48h
    FAQ

    Frequently asked questions

    The questions below are the ones engineering, quality and IT teams actually ask us in demos and security reviews. If yours is not here, ask it in a 30-minute call.

    Did we miss your question?

    IN THEIR WORDS

    Verbatims: what hardware teams say about Koddex.