Do I have to migrate out of my CAD or PLM?

No. Koddex sits alongside them and references their items. Your CAD files stay in CAD and your parts stay in PLM; the graph holds the relationships between them.

What does a native connector do that the API does not?

Nothing you could not build yourself. Native connectors are prebuilt mappings over the same headless API, so you save the integration work rather than gain hidden capability.

Is the sync one-way or two-way?

Two-way, with conflict resolution and idempotency built in. Whatever tool the data was entered in, it lands in the graph and stays in sync.

How long does it take to connect a tool?

OAuth or token auth with scoped permissions, set up in about thirty seconds for the prebuilt connectors. Custom ones are a normal API integration.

What rights does a connector get?

The ones you give it. A connector is a principal with scoped read and write rights on specific entities in specific projects, exactly like a human or an AI agent.

Are integration calls audited?

Yes. Every call is captured in the same audit trail as human edits, with the principal, the timestamp and the permissions it acted under.

What if my tool is not on the list?

Use the API, or ask for a connector. Every integration runs on the same REST and GraphQL surface, so nothing depends on us shipping a specific adapter first.

Where is the data hosted?

EU hosting, with SOC 2 alignment and ISO 27001 in progress.

Product · Integrations

Connect to the engineering stack you already trust.

Koddex sits at the center of your engineering graph and talks to the tools your team uses every day. Headless API, plug & play, the same data synced everywhere.

koddex · CAD & geometry

SolidWorksNative

OnshapeREST API

Fusion 360REST API

CATIA / 3DEXPERIENCENative

NX SiemensNative

CreoREST API

AutoCADNative

InventorNative

Solid EdgeNative

Already talks to the tools on your bench

SiemensPLM · MES

Rockwell AutomationMES

SAPERP

ZohoERP / CRM

HubSpotCRM

Dassault SystèmesCAD

AutodeskCAD

LookerBI

JiraPM

MondayPM

LinearPM

TrelloPM

AsanaPM

ClickUpPM

AtlassianInternal

ConfluenceInternal

NotionInternal

SlackComms

Microsoft ExcelSpreadsheet

Google SheetsSpreadsheet

MiroInternal

FigmaDesign

n8nAI Agents

LangChainAI Agents

AnthropicAI Agents

Hugging FaceAI Agents

GitHubCode

GitLabCode

SiemensPLM · MES

Rockwell AutomationMES

SAPERP

ZohoERP / CRM

HubSpotCRM

Dassault SystèmesCAD

AutodeskCAD

LookerBI

JiraPM

MondayPM

LinearPM

TrelloPM

AsanaPM

ClickUpPM

AtlassianInternal

ConfluenceInternal

NotionInternal

SlackComms

Microsoft ExcelSpreadsheet

Google SheetsSpreadsheet

MiroInternal

FigmaDesign

n8nAI Agents

LangChainAI Agents

AnthropicAI Agents

Hugging FaceAI Agents

GitHubCode

GitLabCode

One API, zero friction.

Koddex is built API-first. Every integration uses the same headless REST + GraphQL surface, with webhooks and SDKs. No proprietary middleware, no custom adapters, no vendor lock.

Coverage

Browse by category.

Click a category on the left to see the tools Koddex connects to.

Connector categories

CAD & geometry14 tools

PLM10 tools

ALM & issue tracking12 tools

Git & code8 tools

Simulation & analysis12 tools

MES & production11 tools

Quality & regulatory9 tools

Comms & docs11 tools

API-first

Headless · API-first

Koddex is built API-first. Every integration uses the same headless REST + GraphQL surface, with webhooks and SDKs. No proprietary middleware, no custom adapters, no vendor lock.

Plug & play: OAuth or token-based auth, scoped permissions in 30 seconds. No support ticket required.
Two-way sync: Read and write across all tools. Conflict resolution and idempotency baked in.
One source of truth: Whatever the entry tool, the data lands in your Koddex graph, and stays in sync everywhere.
Everywhere your team is: Browser, IDE, mobile, CLI. Same API, same data, same audit trail.

Build on the Koddex API

koddex · Headless API

Plug & playOAuth or token-based auth, scoped permissions in 30 seconds. No support ticket required.

Two-way syncRead and write across all tools. Conflict resolution and idempotency baked in.

One source of truthWhatever the entry tool, the data lands in your Koddex graph, and stays in sync everywhere.

Everywhere your team isBrowser, IDE, mobile, CLI. Same API, same data, same audit trail.

Governance

Integrations under the same access model.

Every external connector is a principal with scoped rights. Audit trail captures every call. EU hosting, SOC2 alignment, ISO 27001 in progress.

MCP Koddex

koddex · PLM

TeamcenterNative

WindchillNative

Aras InnovatorREST API

EnoviaREST API

Oracle Agile PLMREST API

SAP PLMREST API

IBM Engineering ELMREST API

Arena PLMREST API

Propel PLMREST API

Every tool you already run. One set of rules.

Most integrations run on a service account with full access and no trail. An agent or a script updates a component attribute directly, no review, no trace, and the approved baseline no longer reflects reality. Koddex treats a connector the way it treats an engineer: scoped rights, the same validation pipeline, the same audit trail, and locked baselines that stay locked whatever calls them.

Scoped access per integration: read-only, write-to-draft or full lifecycle, granted explicitly rather than inherited from whoever built it
The same validation pipeline as humans: schema constraints, required fields, lifecycle status. Invalid data is rejected, never silently absorbed
Baseline immutability enforced structurally: a blocked write is logged and the quality manager is notified. No override, no back door

Browse by category.

Click a category on the left to see the tools Koddex connects to.

CAD & geometry

Sync part numbers, BOMs and revisions with your CAD authoring tools.

SolidWorksNative

OnshapeREST API

Fusion 360REST API

CATIA / 3DEXPERIENCENative

NX SiemensNative

CreoREST API

AutoCADNative

InventorNative

Solid EdgeNative

Autodesk VaultNative

SketchUpREST API

FreeCADOpen source

BlenderOpen source

Bentley MicroStationNative

What changes when the connector plays by your rules.

Most integrations are a service account with full access and no trail. Koddex treats a connector the way it treats an engineer.

One surface, every integration

REST and GraphQL with webhooks and SDKs, so there is no proprietary middleware and no custom adapter to maintain.

1 API

Behind every connector

Connectors are scoped principals

An external tool gets rights on specific entities in specific projects, and every call it makes lands in the audit trail.

Scoped

Rights per connector

Sync goes both ways

Read and write across tools, with conflict resolution and idempotency built in, so the graph stays the reference wherever data was entered.

2-way

Sync with your stack

Frequently asked questions

Plug Koddex into your existing stack.

Tell us what tools you use today. We'll show you the connectors and the integration path.