Question 1

How long does it take to deploy Koddex?

Accepted Answer

The first use case is typically live in production within 48 hours, and full onboarding takes about three weeks, not three months. Deployment follows a repeatable six-phase method (setup, learning, core concepts, data governance, use case implementation, wrap-up) with validation milestones, led by a dedicated Customer Success Manager. There is no multi-quarter integration project.

Question 2

What does the onboarding program include?

Accepted Answer

A structured program in which we model your actual business processes in Koddex with your team: kickoff and training sessions, access governance workshops, and hands-on implementation of two to three priority use cases using your own data. After onboarding, you keep weekly 30-minute office hours with your CSM, direct chat support, and change management assistance (internal champions, demo sessions for managers, onboarding of additional users).

Question 3

Do we need to migrate everything at once?

Accepted Answer

No, and we advise against it. Koddex is designed for incremental adoption: start with one or two high-value processes (for example requirements traceability or BOM roll-ups), connect the tools you keep, and extend the graph program by program. Most teams import their existing spreadsheets (CSV, Excel) as the starting point.

Question 4

Who needs to be involved on our side?

Accepted Answer

A project lead, an IT administrator and a handful of key users for the onboarding sessions. Process owners prepare a sample dataset per use case. That is the whole footprint; no dedicated Koddex administrator role is required afterwards.

Question 5

How is deployment validated internally, for example by our quality department?

Accepted Answer

The data governance phase of onboarding produces exactly what quality teams need to sign off: documented access rules, role and permission mapping, and an audit trail active from day one. Many customers use the first modeled use case as the internal demonstration to quality and leadership.

Question 6

How does data modeling work? Do we have to fit a predefined structure?

Accepted Answer

No. Koddex is built on visual metamodeling: your team defines its own object types (systems, assemblies, components, requirements, tests, risks, documents), their attributes, their relations and their computation rules. The model reflects your engineering, not a vendor's template. You stay agile while building the model, and the platform enforces rigor once it is set: strict typing, mandatory attributes, controlled vocabularies.

Question 7

Can models use inheritance and computed fields?

Accepted Answer

Yes. Models support inheritance (a cylindrical and a hexagonal component can share a parent model while carrying geometry-specific formulas) and computed fields at graph level: mass roll-ups, requirements coverage rates, compliance statuses, cost aggregations. Computations run in real time and flag errors immediately when a formula input is missing or invalid, so data integrity problems surface at entry, not at review.

Question 8

How does impact analysis work?

Accepted Answer

Because everything is linked in one graph, Koddex shows the full blast radius of a change before you commit it: which requirements, tests, risks, documents and parent systems are affected by a component modification. If a change breaks a norm or an engineering requirement defined in your model, it is flagged instantly.

Question 9

How do revisions, locking and baselines work?

Accepted Answer

Items and models can be locked once validated, making them immutable. To evolve locked data, users create revisions (branches) that are worked on and submitted for approval without touching the reference version, then merged with full lineage between old and new revisions. Immutable baselines let you prove the exact configuration of the entire product at any point in time, which is the core of audit-proof configuration management.

Question 10

Is Koddex a PLM, a QMS, or a requirements management tool?

Accepted Answer

None of the three, and parts of all of them. Koddex is an Engineering Operating System: the structured backbone that holds your product definition (requirements, BOM, tests, decisions, documents) as one computable graph. It replaces the scattered spreadsheets between your tools rather than replacing your CAD, your ERP or your quality processes, and it connects to PLM, QMS, ERP and MES platforms via API.

Question 11

Can we manage risk matrices and compliance statuses in Koddex?

Accepted Answer

Yes. Risk registers with severity and probability scoring can be modeled and linked to requirements and tests. If a test result invalidates a requirement, the linked risk is automatically flagged, giving quality teams immediate visibility without manual cross-checking.

Question 12

Does Koddex have an API?

Accepted Answer

Yes, and it is not an afterthought: Koddex is API-first and headless. Everything you can do in the interface is available through the API, which makes deep integrations and custom workflows possible without waiting for a connector. Unlimited API access is included in every license, with no metering surcharge.

Question 13

Which tools does Koddex integrate with?

Accepted Answer

80+ native integrations across the engineering stack: PLM (Teamcenter, Windchill, Arena), ERP (SAP, NetSuite, Zoho), QMS (Greenlight Guru, MasterControl), MES (Opcenter, Rockwell), CAD (SolidWorks, CATIA, Autodesk), project management (Jira, Monday, Linear, Asana), collaboration (Slack, Notion, Confluence, Excel, Google Sheets) and AI tooling (n8n, LangChain, Anthropic, Hugging Face).

Question 14

How does integration with our ERP or PLM actually work?

Accepted Answer

Typically through your IT team's standard middleware layer, consuming the Koddex API. Data exchanges are fully traced: every integration action is logged with a per-integration audit trail, and access can be scoped precisely so an integration only reads or writes the data it needs. Your IT team keeps control of the exchange architecture.

Question 15

Can we import and export our data freely?

Accepted Answer

Yes. Imports from CSV and Excel are standard during onboarding and afterwards. Exports are available in machine-readable formats (CSV, JSON), including scoped exports for audits. Contractually, you can retrieve a complete export of all your data at any time, and full reversibility is guaranteed at the end of the contract. Your data is never locked in.

Question 16

What about CAD files and other engineering file formats?

Accepted Answer

Koddex links to and attaches files (PDF, Office documents, and engineering formats) on items in the graph, and connects to CAD tools through the API rather than replacing your CAD vault. Support for specific exchange formats is handled case by case during onboarding.

Question 17

What is the MCP integration and what does it enable?

Accepted Answer

Koddex ships a native MCP (Model Context Protocol) server, which lets AI agents and assistants (Claude, LangChain or n8n pipelines, or your own agents) read and write on your engineering graph through governed, structured operations: querying items, running impact analyses, creating revisions, updating attributes, generating documentation.

Question 18

Is it safe to let AI agents work on engineering data?

Accepted Answer

That is precisely what the architecture is for. Agents operate under the same governance as humans: permissions, locks, revision workflows and a per-action audit trail. An agent cannot modify a locked baseline, and every agent action is attributable and reversible. Because the data is structured and typed, agents work on verified relationships instead of guessing from documents, which is what makes AI on engineering data reliable rather than hallucination-prone.

Question 19

Does AI usage require sending our data to third parties?

Accepted Answer

AI capabilities operate through governed interfaces under your control. You choose which agents connect, with which permissions, on which scopes. Anonymized, aggregated usage data may be used to improve the Service; your engineering data is never used for marketing or shared without your written agreement.

Question 20

Where is our data hosted?

Accepted Answer

Exclusively in the European Union, in the AWS Europe (Ireland) region. No customer data is stored, processed or transferred outside the European Economic Area without your prior express written agreement, in compliance with GDPR Chapter V. If a non-EU authority requests access to your data, we commit contractually to notify you without delay, challenge legally baseless requests, and limit any disclosure to the strict minimum.

Question 21

How is our data protected?

Accepted Answer

Encryption at rest (AES-256) and in transit (TLS 1.2+), with keys managed under Koddex control. SSO integration with your identity provider, MFA enforced for privileged access, least-privilege access management, monthly vulnerability scans, annual independent penetration tests, and anti-malware analysis of uploaded files. Production data access is restricted to authorized EU-based personnel under individual confidentiality undertakings. The hosting infrastructure is certified against ISO/IEC 27001 and SOC 2.

Question 22

Who owns the data we put in Koddex?

Accepted Answer

You do, entirely and exclusively. You retain ownership of all data, configurations and models created in the Service. Koddex claims no rights over your data and does not access, use or disclose it for any purpose other than delivering the Service.

Question 23

What audit trails are available?

Accepted Answer

Application-level audit logs record authentication, authorization, configuration changes and data access events, retained for a minimum of 36 months. On the engineering side, every modification to every item is traced (who, what, when), and activity history supports restoring deleted elements. Auditors and external stakeholders can be granted free, scoped, read-only access.

Question 24

What happens to our data if we leave, or if Koddex disappears?

Accepted Answer

Two contractual guarantees. Reversibility: at the end of the contract you receive a complete export in machine-readable formats within days, a transition access period, and certified deletion of your data from our systems and backups afterwards. Continuity: the source code, documentation and deployment scripts are deposited with a third-party escrow agent (such as the Agence pour la Protection des Programmes) and updated quarterly; in the event of a lasting failure or cessation of activity, you receive a license to use the escrowed elements to maintain service continuity internally.

Question 25

Can Koddex host classified or export-controlled data?

Accepted Answer

The standard Service is not accredited for classified information (IGI 1300), restricted-regime PPST data or export-controlled technical data (EU dual-use regulation 2021/821) without a prior specific analysis and written agreement. This is stated transparently because our customers in defense and nuclear need to know exactly where the boundary is; contact us to discuss specific hosting requirements.

Question 26

Which regulations and standards does Koddex support?

Accepted Answer

Koddex is designed for regulated hardware development: ISO 13485 and IEC 62304 (medical devices), MDR technical documentation, DO-178C workflows (aerospace), ISO 19443 contexts (nuclear supply chain), the EU Machinery Regulation 2023/1230 digital technical file, and upcoming regimes such as the Battery Regulation and Digital Product Passport. The platform provides the end-to-end traceability, immutable baselines and audit evidence these frameworks require; your processes and certifications remain yours.

Question 27

Does Koddex replace our QMS?

Accepted Answer

No. Koddex produces the engineering traceability your QMS and your notified body consume: requirements-to-test coverage, impact assessments, configuration baselines. Quality processes (CAPA, complaints, training) stay in your QMS, which Koddex connects to.

Question 28

How does Koddex help during an audit?

Accepted Answer

Audit evidence is generated as you work, not rebuilt afterwards. Scoped exports assemble the traceability for a given system or baseline in minutes, external auditors get free read-only access to exactly the scope you define, and the activity log answers "who changed what, when" instantly. Customers typically describe the difference as a ten-minute query instead of a three-week preparation sprint.

Question 29

Is Koddex GDPR compliant?

Accepted Answer

Yes. A data processing agreement under Article 28 GDPR is part of every contract, with Koddex acting as processor. Approved subprocessors are contractually listed (currently AWS EMEA, EU region), any change is notified 30 days in advance with a right of objection, and personal data breaches are notified within 24 hours of detection.

Question 30

What are the availability commitments?

Accepted Answer

A 99.9% monthly availability rate, excluding planned maintenance notified in advance. Business continuity is backed by a disaster recovery plan with a recovery time objective (RTO) of 4 hours and a recovery point objective (RPO) of 6 hours, tested at least annually, with backups stored in a physically separate location. SLA breaches trigger service credits.

Question 31

How does reactive support work when something breaks?

Accepted Answer

Support is tiered by severity with contractual response and resolution targets. Critical incidents (production interruption or major feature unavailable) get a 15 to 30 minute response over extended hours (6:00 to 23:00 CET) by phone and ticketing, with resolution targeted within 4 to 8 hours. High-severity issues are answered within 1 hour, minor anomalies within 4 business hours, and standard requests within 1 business day. Priority support is included in every license, not sold as a premium tier.

Question 32

How are product updates handled?

Accepted Answer

Koddex evolves continuously; updates and fixes are included in the subscription at no extra cost, with no version upgrades to manage on your side. Significant changes affecting architecture, hosting or security controls are notified at least 30 days in advance so your IT and security teams can assess them.

Question 33

How are security incidents communicated?

Accepted Answer

Any security incident affecting your data or service availability is notified within 24 hours of detection, with the nature of the incident, impacted data, mitigation measures and remediation plan, followed by full cooperation on investigation and resolution.

Question 34

How is Koddex priced?

Accepted Answer

Per named user, per month, on an annual subscription, with everything included: all platform features, unlimited API access, unlimited graph computations, MCP, priority support, a dedicated onboarding manager, and free access for auditors and external stakeholders. There are no feature tiers and no usage metering. Pricing is designed for European mid-size manufacturers; contact us for a quote on your team size.

Question 35

Do prices increase after we sign?

Accepted Answer

Not during your initial commitment: the per-user price is contractually firm for the initial term, including for additional licenses added along the way. Any later revision is capped by an indexation mechanism and requires 60 days written notice before renewal.

Question 36

Can we add or reduce licenses?

Accepted Answer

Additional licenses can be added at any time at the contractual unit price, billed pro rata. License counts are reviewed at each contract anniversary.

Question 37

Is there an early adopter program?

Accepted Answer

Yes. Early adopters benefit from a free onboarding program in which we model your business processes with you (a packaged deliverable normally invoiced separately), for commitments starting at ten licenses. Ask us about current conditions.

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