Wide-body aircraft under maintenance inside a hangar, engines and scaffolding visible

Aerospace · Defense · Space

THE ENGINEERING OPERATING SYSTEM FOR REGULATED HARDWARE INDUSTRIES

Design, certify and fly your aerospace systems.

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

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

« 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

AEROSPACE & DEFENSE · WHAT WE HEARD, NOT WHAT WE ASSUMED

On a defence programme, the standard is never the hard part. Agreeing on what it says is.

The answer to “where is it hosted” ends the conversation

For defence programmes the cloud is not a preference to be argued with. The tool installs on the customer's server, physically inside the customer's building, or it does not get evaluated at all.

0cloud allowed

on-premise in the building, or no evaluation

« For defence, forget the cloud entirely. It installs on the customer's server, physically in the building. »

When it gets paid forFirst security review

How do you answer that today?

Sovereign by architecture: your infrastructure, your keys, no exception.

Two product lines, two standards, nothing shared

The civil line answers to European CE standards, the military line to its own. Each business unit interprets its own text its own way, so a design that could have been inherited is specified twice from scratch.

2product lines

no traced reuse between civil and military

« The unit that works only for defence has military standards. It has nothing like the same things to comply with. »

When it gets paid forProduct line launch

One model, two baselines. Inheritance is traced, not retyped.

The question about one line of the standard, still open

Everybody is comfortable with the standard in outline and nobody knows it to the letter. So how one clause should be read gets asked, gets escalated, and three months later has still never been settled — while design carries on around it.

3months

one clause, escalated, never settled

« Nobody knows the standard to the letter. You end up on some tiny detail that was never settled. »

When it gets paid forAuthority filing

The reading you chose is recorded on the requirement, with its date and its author.

REGULATORY LANDSCAPE

EASA Part 21CS-23CS-25DO-178CDO-254ARP4754AARP4761DO-160AS9100

Between the design change and the production ramp, the trail goes cold.

J+0
The clause is interpreted
Somebody decides how one line of the standard should be read. In a meeting.
J+180
Qualification review
A second team reads the same line the other way. Both are already built.
J+730
Production ramp
The authority asks which reading was applied, to which serial numbers.

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

CS-23, CS-25, DO-178C, ARP4754A. 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

CS-23 · Airframe compliance94%

DO-178C · Embedded software (DAL B)81%

ARP4761 · Safety assessment76%

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

Aerospace, defense, space, rail. Structured for every auditor.

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

SiemensPLM · MES

Dassault SystèmesCAD · PLM

AutodeskCAD

SAPERP

Rockwell AutomationMES

JiraALM

ConfluenceDocs

GitHubCode

Microsoft ExcelSpreadsheet

Google SheetsSpreadsheet

AnthropicAI agents

n8nAutomation

SiemensPLM · MES

Dassault SystèmesCAD · PLM

AutodeskCAD

SAPERP

Rockwell AutomationMES

JiraALM

ConfluenceDocs

GitHubCode

Microsoft ExcelSpreadsheet

Google SheetsSpreadsheet

AnthropicAI agents

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.

« We need requirements traceability to replace the manual spreadsheets before the launch. »

Engineering Lead · Medical device

MedTechAerospace & defense

« For defence, forget the cloud entirely. It installs on the customer's server, physically in the building. »

Business Unit Director · Defence programmes

Aerospace & defense

« The unit that works only for defence has military standards. It has nothing like the same things to comply with. »

Business Unit Director · Defence programmes

Aerospace & defense

« Nobody knows the standard to the letter. You end up on some tiny detail that was never settled. »

Business Unit Director · Defence programmes

Aerospace & defenseNuclear & energy

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

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?

NEXT STEP

Let's take the next step.

Book the demo (30 min)

A demo on aerospace use cases, ideally with several members of your team. We gather your requirements live.

Book the demo →

IN THEIR WORDS

Verbatims: what hardware teams say about Koddex.

Design, certify and fly your aerospace systems.

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

Absolute trust by design.

Structured, yet malleable.

Execution is a craft.

On a defence programme, the standard is never the hard part. Agreeing on what it says is.

The answer to “where is it hosted” ends the conversation

Two product lines, two standards, nothing shared

The question about one line of the standard, still open

Between the design change and the production ramp, the trail goes cold.

One backbone for a structured, traceable and computable product.

Visual metamodeling

Graph-level computation

Lock & revision control

End-to-end traceability

Write the BOM you actually ship, then lock it.

Define once, reuse across the whole BOM

Lock, branch and revise safely

Certification-ready templates

Visualize the full impact of every change.

Items within items

Computation links every attribute

Catch the deviation before the commit

Every change already traced. You just click Export.

Activity history at every level

Targeted export to auditors & suppliers

Certification-ready evidence

Let AI agents work inside your design record.

Native MCP access

The same rules as humans

Full audit trail

Koddex becomes the backbone of your organization.

Sentence you have already said yourself.

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

Operational in days. Audit-ready in months.

Architecture workshop

Import & configuration

Training & handover

First workflows in production

Scale & autonomy

Frequently asked questions

Getting started and onboarding5

Data modeling and the platform6

Integrations, API and interoperability5

AI and MCP3

Security and data sovereignty6

Compliance and regulations4

Support, maintenance and reliability4

Commercial4

Let's take the next step.

Book the demo (30 min)