Freezes what your stack already produces
'%3e%3cpath%20d='M13.513%2035.76a2.433%202.433%200%200%201-2.059-3.723l4.377-6.99a2.432%202.432%200%201%201%204.123%202.582l-4.378%206.99a2.43%202.43%200%200%201-2.063%201.141z'%20fill='%23ff3d57'/%3e%3cpath%20d='M21.056%2035.76a2.433%202.433%200%200%201-2.063-3.723l4.38-6.99a2.432%202.432%200%201%201%204.117%202.582l-4.372%206.99a2.43%202.43%200%200%201-2.063%201.141z'%20fill='%23ffcb00'/%3e%3cellipse%20ry='2.375'%20rx='2.436'%20cy='33.384'%20cx='28.597'%20fill='%2300d647'/%3e%3c/g%3e%3c/svg%3e){kind=small}
A frozen PDF is a snapshot. A frozen graph is an answer.
Exporting a document at review time tells you what the system looked like. It does not tell you why a value was chosen, which requirement it satisfied, or what has moved since. Koddex freezes the structure itself, links included, so a past state is still queryable years later.
See the system before you freeze it.
Koddex renders your metamodel as a live canvas: entities, their attributes, and the typed links between them. You validate a structure you can actually read, instead of signing off a spreadsheet nobody can hold in their head.
- Entities, attributes and relationships on one canvas, zoomable down to a single field
- Model any business object your teams already work with, not a fixed schema
- The same view drives the data, so the diagram can never drift from reality
Validate a state, duplicate it, keep the history.
Freezing a revision writes a content hash over the whole scope. From there you branch: duplicate the frozen state for a new market, a new variant or a new standard, and the lineage back to the original stays explicit.
- Content-hashed baselines, so nothing is quietly edited after sign-off
- Duplicate a validated state instead of restarting the paperwork for each standard
- Replay any past revision and see exactly what the reviewer approved
- Rev A · design input frozenlockedhash 4b1e…07c
- Rev B · V&V completelockedhash 9ad2…f31
- Rev B.1 · duplicated for EU MDRduplicatedfrom Rev B
- Rev C · in work3 open changes
Follow any element across the whole system.
Traceability is not a report you assemble before an audit. Every element carries its links, so you walk from a certification clause down to the component that satisfies it, and back up to the test that proves it, in one continuous chain.
- Activity history at every level, from the whole programme down to one attribute
- Scoped export for auditors and suppliers, without handing over the full file
- Works across variants, so a shared component is traced in every configuration
What a frozen graph gives you that a frozen file cannot.
The value shows up two years after the freeze, on the day someone asks why a decision was made.
Every revision stays queryable
A past baseline is not an archived PDF. It is a structure you can still traverse, filter and export.
Duplicating beats restarting
A validated state becomes the starting point for the next market or standard, with its lineage attached.
Nothing moves after sign-off
Content hashes over the frozen scope mean an edit after the freeze is impossible rather than merely discouraged.