For firms whose models can't go to anyone else's cloud: what running the AI yourself actually secures, today and over decades.
Plenty of engineering firms have watched the AI wave from the shore. Their models hold things that cannot go to anyone else's cloud — a turbine's internal geometry, a utility's live network, a client's unreleased product under NDA. For them, "upload your file and try it" was never on the table, whatever the tool promised.
ODA MCP Servers change that, because you run them yourself. An AI agent works against your models inside your own network, and nothing leaves it. For a firm under real confidentiality obligations, that is the line between adopting AI and being shut out of it.
There is a mode built for exactly this. Run the server locally and it has no network path out at all — the model never crosses a wire it shouldn't. File access is whitelisted, every tool call is logged, and each tool declares whether it only reads or can also write. That is the kind of trail an ITAR, TISAX or MDR audit expects to find.
The answers come from the same compiled engine that ships inside commercial CAD products, so the same model returns the same number every time. When a figure has to survive an audit or a design review, that repeatability stops being a technicality.
Control has a second horizon. Engineering data outlives the software that drew it, and often the vendors too; a model may have to stay readable for fifty years. Access served by a consortium that by charter cannot be bought is something you can plan a decades-long archive around, not a product that might be acquired and quietly sunset. And it runs against whatever language model you trust, on-premises or hosted.
Martyn Day reached the same read from outside. In AEC Magazine:
"A member-governed body that cannot be bought, offering self-hosted, model-agnostic access to the formats, is about as close to a firm-level data sovereignty play as this industry has produced."
Running it yourself is not free of effort — self-hosting takes hands and hardware. The capability is also uneven: reading and analysis work across all three formats, while writing back goes furthest in DWG and stays lighter in STEP and IFC. The control, though, is real, and for this kind of firm it is the entire point.
New to the product? Start with the announcement and the FAQ. When you want to work through running it inside your own environment, talk to us.
