Build any product from reusable, typed building blocks, with full attribute control, zero rigid templates, and instant team adoption.
Specifications for complex parts (acoustic lenses, transducers, biocompatible housings) are scattered across Excel files, PDF specs, and legacy PLM silos. Implementing rigid tools fails because they force a methodology that doesn't fit. Engineers reject the tool, adoption collapses, and teams revert to fragmented spreadsheets.
Koddex acts as a blank canvas where teams define their own blueprints, called classes and instances. Each class carries typed attributes (numbers, dates, units like MHz, frequencies, materials) that engineers configure to match their exact workflow. Define a Transducer once, then instantiate it across every new design. No forced methodology. No migration pain.
Numbers, dates, enums, units (MHz, mm, pC/N). Define the exact schema your engineering domain requires.
Define a component blueprint once. Instantiate it across every new product variant without duplication.
Engineers create and evolve their metamodel visually. No developer required, no rigid migrations.
Child classes inherit parent attributes automatically. Override only what changes for each variant.
Every numeric field carries its unit. Conversions and validations happen natively. No broken formulas.
Flexible enough to match any team's culture. Engineers adopt it because it fits their workflow, not the other way around.